On Sat, Feb 12, 2005 at 03:02:14PM +0100, Vincent Fourmond wrote:
>  traceroute fails:
> 
> traceroute to ftp.fr.debian.org (212.27.32.66), 30 hops max, 38 byte packets
[...]
> 10  vlq-6k-1-po1.intf.routers.proxad.net (212.27.50.2) 36 bytes to 
> 132.166.53.137  5.124 ms  4.963 ms  4.983 ms
> 11  * * *
> (and then it's only * * * until 30...)
> 
>  Whereas tcptraceroute does give the right stuff:
> 
> Tracing the path to ftp.fr.debian.org (212.27.32.66) on TCP port 80, 30 
[...]
> 10  vlq-6k-1-po1.intf.routers.proxad.net (212.27.50.2)  5.364 ms  4.818 
> ms  4.953 ms
> 11  debian.proxad.net (212.27.32.66) [open]  5.454 ms  4.935 ms  4.928 ms
> 
>  So it does really look like the firewall is stupid (that wouldn't 
> surprise me, the company which is dealing with computers where I work is 
> about as good as my daughter - and she's 6 month old...)

haha, but you see, ICMPs are going back and further from your firewall (if it
isn't so you can't even trace your first hop!) so it is a matter of some router
in-between. (I can ICMP traceroute debian.proxad.net, though)
The best thing would be to have a -t|--tcp switch in netselect to do tcp
traceroute instead of icmp (and workaround dumb firewalls)
patches are welcome :)

thanks for your report,
filippo
--
Filippo Giunchedi 
GNU/PG key: 6B79D401
Random signature follows:

I was once walking through the forest alone. A tree fell right
in front of me -- and I didn't hear it.
-- Steven Wright

Attachment: pgpq0fSXgoymz.pgp
Description: PGP signature

Reply via email to