netcat | nc -v -z localhost 22 | nc -l 1111 - nc 192.168.184.130 1111 | echo -n "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80

By OK -
client
#nc 192.168.184.130 1111
fdf
fd
hello

server
#nc -l 1111
fdf
fd
hello
==================
client

doc1@ubuntu:~$ cat testfile 
Sat Nov  4 10:13:01 PDT 2017
doc1@ubuntu:~$ cat testfile | nc 192.168.184.130 1111

server
[root@localhost docker-compose-ex1]# nc -l 1111
Sat Nov  4 10:13:01 PDT 2017
==================
options on server
$ nc -l 2389 > test
client timeout
$ nc -w 10 localhost 2389
server up after client disconnect
$ nc -k -l 2389
PORT SCANNING
 nc -v -z localhost 22

Connection to localhost 22 port [tcp/ssh] succeeded!

doc1@ubuntu:~$ nc -zv 192.168.184.130 1100-1111
nc: connect to 192.168.184.130 port 1100 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1101 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1102 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1103 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1104 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1105 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1106 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1107 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1108 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1109 (tcp) failed: Connection refused
nc: connect to 192.168.184.130 port 1110 (tcp) failed: Connection refused
Connection to 192.168.184.130 1111 port [tcp/*] succeeded!

doc1@ubuntu:~$

============================

TALKING TO SERVERS
It is sometimes useful to talk to servers "by hand" rather than through a user interface. It can aid in troubleshooting, when it might be necessary to verify what data a server is sending in response to commands issued by the client. For example, to retrieve the home page of a web site:
$ echo -n "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80
Note that this also displays the headers sent by the web server. They can be filtered, using a tool such as sed(1), if necessary.
More complicated examples can be built up when the user knows the format of requests required by the server. As another example, an email may be submitted to an SMTP server using:
$ nc localhost 25 << EOF
HELO host.example.com
MAIL FROM: <user@host.example.com>
RCPT TO: <user2@host.example.com>
DATA
Body of email.
.
QUIT
EOF


===========
- p - source port

 -T ToS
-X proxy_version
Requests that nc should use the specified protocol when talking to the proxy server. Supported protocols are "4" (SOCKS v.4), "5" (SOCKS v.5) and "connect" (HTTPS proxy). If the protocol is not specified, SOCKS version 5 is used.
-x proxy_address[: port]
Requests that nc should connect to hostname using a proxy at proxy_address and port. If port is not specified, the well-known port for the proxy protocol is used (1080 for SOCKS, 3128 for HTTPS).

 server UDP port
$ nc -4 -u -l 2389

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
Read more

teamcity Automatic Agent Start under Linux

By OK -
Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent....
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availabi...
Read more