3 ms·

All that stuff doesn't work between systems behind firewalls or NATs.

• deleted 7y ago
  [deleted]
• johnisgood 7y ago
  > A basic file transfer is very simple: Start Ncat in listen mode on one end, start Ncat in connect mode on the other end, and pipe the file over the connection. There are two ways to do this that differ only in which end listens, the sender or the receiver. Sometimes you can't create a listening socket on one end of the transfer because of a lack or permissions, NAT, or filtering. As long as you can listen on at least one end, though, you can use this technique.[1] This works with most if not all netcat implementations. > The basic file transmission technique described at the beginning of this section fails if neither participating host is capable of listening, or the two hosts can't communicate directly. This situation has become common with the prevalence of network address translation. A way to work around it is to use a third host as an intermediary. The intermediate host listens in connection brokering mode and the other two hosts connect to it. Recall from the section called “Connection Brokering” that in connection brokering mode any input received on one socket is copied and sent out to all other sockets. With just two hosts connected this is especially simple: anything coming from one host gets forwarded to the other. This example shows host1 sending inputfile to outputfile on host2, using host3 as an intermediary.[1] This works nicely with Nmap's Ncat. [1] https://nmap.org/ncat/guide/ncat-file-transfer.html https://nmap.org/ncat/guide/ncat-file-transfer.html
  • api 7y ago
    The second is not direct.