Using a second machine, connect to the listening nc process, feeding it the file which is to be transferred:ДЄfter the file has been transferred, the connection will close automatically. Start by using nc to listen on a specific port, with output captured into a file: The example in the previous section can be expanded to build a basic data transfer model.ДЄny information input into one end of the connection will be output to the other end, and input and output can be easily captured in order to emulate file transfer. The connection is terminated with an EOF (`^D'). After the connection has been set up there is no concept of `server' or `client'. There is now a connection between the ports, anything typed at the second console will be concatenated to the first, and vice. On a second console (or a second machine), connect to the machine and port being listened on: On one console, start nc listening on a specific port (1234) for a connection. doesn't seem to be required but is used for destination file Produces T17:07:44.534168-05:00 testing from ncДapie doesn't seem to recognize the timestamp (he adds his own) and a null message creates entry with rtr as host!Д¬olon's are in the original message (i.e. Simple syslog example: > nc -u -v 514Д¬onnection to port 514 succeeded! Ranges are in the form nn-mm.Дestination port must be specified, except with -U when a socket must be specified. Host a numerical IP address or a symbolic hostname (except with -n ).ДЄ host must be specified, unless -l (listen) is used, in which case the local host is used). r randomly choose source and/or destination ports instead of sequentially within a range or in the order Port for the proxy protocol is used (1080 for SOCKS, 3128 for HTTPS). x proxy_address connect using a proxy at proxy_address and port. SOCKS v.4, connect(HTTPS proxy) SOCKS v.5(default). XВ 4 |5 |connect protocol when talking to the proxy server. t send RFC 854 DON'T and WON'T responses to RFC 854 DO and WILL requests. Also causes a delay time between connections to multiple ports. i interval delay time interval between lines of text sent and received.

w seconds If a connection and stdin are idle for more than timeout seconds, the connection is closed. used with -l -z scan for listening daemons, without sending any data to them. l listen for an incoming connection rather than initiate a connection to a remote host.Дo not use with -z, -s, -p or -w -k keep listening for another connection after its current connection is completed. a SOCKS or HTTP Proxењњommand for ssh(1).

shell-script based HTTP clients and servers.

Scripts nicely, and separates error messages to standard error Open TCP connections, send UDP packets, listen on arbitrary TCP and UDP ports, do port scanning, and deal with both IPv4 and IPv6. Nc netcat establish arbitrary TCP and UDP connections and listens nc - netcat establish arbitrary TCP and UDP connections and listens

Playonlinux nc netcat