Groups > comp.os.linux.networking > #2035

Is my ISP blocking `nc`?

From	Unknown <dog@gmail.com>
Newsgroups	comp.os.linux.networking
Subject	Is my ISP blocking `nc`?
Date	2013-03-17 09:54 +0000
Organization	A noiseless patient Spider
Message-ID	<ki43rt$8ua$1@dont-email.me> (permalink)

Show all headers | View raw

I get:
#  nc -l -p 119 -vv -w 80 -n 78.46.70.11
listening on [any] 119 ...
quit
^C sent 0, rcvd 0

Or is my syntax STILL wrong?

IIRC I've used nc before on an older installation, so I tried:-
-> # chroot /mnt/LennyP35 /bin/nc  -l -p 119 -vv -w 80 -n 78.46.70.11
listening on [any] 119 ...
^C sent 0, rcvd 0
bash-3.1# chroot /mnt/LennyP35 /bin/nc -vvv 66.11.225.84 smtp
66.11.225.84: inverse host lookup failed: Host name lookup failure
^C sent 0, rcvd 0
bash-3.1# chroot /mnt/LennyP35 /bin/nc -vvv gmail.com smtp
gmail.com: forward host lookup failed: Host name lookup failure
   : Resource temporarily unavailable
bash-3.1# chroot /mnt/LennyP35 /bin/nc -vvv 78.46.70.11 119
78.46.70.11: inverse host lookup failed: Host name lookup failure
78.46.70.11^C sent 0, rcvd 0

What confuses me too is if/how a `chroot` can communicate with THIS
<root's pids>; especially since the chrooted-proccesses haven't got
any /proc/* and /dev/*

== TIA

Back to comp.os.linux.networking | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Is my ISP blocking `nc`? Unknown <dog@gmail.com> - 2013-03-17 09:54 +0000
  Re: Is my ISP blocking `nc`? Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-03-17 11:24 +0100
    Re: Is my ISP blocking `nc`? Unknown <dog@gmail.com> - 2013-03-21 05:16 +0000
      Re: Is my ISP blocking `nc`? Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-03-21 09:36 +0100

csiph-web