nanog mailing list archives
Re: Routing issues
From: "Rubens Kuhl Jr." <rubens () email com>
Date: Wed, 14 Apr 2004 10:59:49 -0300
I'm seeing the same thing: works from 80.*, doesn't work from 83.*. Note that www.mercer.com seems to suffer from a bad case of paranoia, they filter traceroute and ping, so probably a misconfigured firewall there. hk.yahoo.com traceroutes just fine from a 212.* address:
TCP port 80 can also be used to traceroute... hping is your friend. http://www.hping.org (or apt-get install hping2 on apt-friendly distributions) Rubens
Current thread:
- Re: Lazy network operators, (continued)
- Re: Lazy network operators Andrew - Supernews (Apr 13)
- Re: Lazy network operators Iljitsch van Beijnum (Apr 13)
- Re: Lazy network operators John Curran (Apr 13)
- Re: Lazy network operators Randy Bush (Apr 13)
- Re: Lazy network operators Christopher L. Morrow (Apr 13)
- Re: Lazy network operators Randy Bush (Apr 13)
- Re: Lazy network operators Christopher L. Morrow (Apr 13)
- Re: Lazy network operators Robert E. Seastrom (Apr 14)
- Routing issues Simon Brilus (Apr 14)
- Re: Routing issues Iljitsch van Beijnum (Apr 14)
- Re: Routing issues Rubens Kuhl Jr. (Apr 14)
- Re: Routing issues Nick Feamster (Apr 14)
- Re: Lazy network operators Steven M. Bellovin (Apr 13)
- Re: Lazy network operators John Curran (Apr 13)
- Re: Lazy network operators Steven M. Bellovin (Apr 13)
- Re: Lazy network operators Eric Brunner-Williams (Apr 13)
- Re: Lazy network operators Paul Vixie (Apr 13)
- Re: Lazy network operators Eric Brunner-Williams (Apr 14)
- Re: Lazy network operators John Curran (Apr 13)
- Re: Lazy network operators Rob Nelson (Apr 17)
- Re: Lazy network operators Michael . Dillon (Apr 14)