Henrique de Moraes Holschuh <hmh@debian.org> writes: > On Wed, 01 Jun 2011, Gerald Turner wrote: >> Henrique de Moraes Holschuh <hmh@debian.org> writes: >> $ tracepath6 schein.debian.org >> 1?: [LOCALHOST] 0.031ms pmtu 1480 >> 1: shub-niggurath.unzane.com 0.162ms >> 1: shub-niggurath.unzane.com 0.360ms >> 2: gturner-1.tunnel.tserv14.sea1.ipv6.he.net 6.576ms >> 3: gige-g2-6.core1.sea1.he.net 5.654ms >> 4: 10gigabitethernet9-1.core1.sjc2.he.net 26.522ms >> 5: 10gigabitethernet3-2.core1.pao1.he.net 34.657ms >> 6: he.pao1.isc.org 29.855ms >> 7: int-0-0-0.r1.sjc3.isc.org 31.418ms asymm 5 >> 8: schein.debian.org 27.519ms reached >> Resume: pmtu 1480 hops 8 back 59 > > 8 hops to get to shein, and *59* hops to get back?! > > That path is hopelessly broken. In fact, this is so weird I'd guess > something is screwing up the TTL fields in the way. > Wow. I tried a tool at SiXXS to tracreoute between various PoPs of theirs to my hosts running on a Hurricane Electric tunnel. Hops look reasonable (average 9 hops and under 50ms latency). https://www.sixxs.net/tools/traceroute/ > Set the TTL to packets directed to shein to 250, and check what > happens. I think you can do that adding a explicit route (via your > default gateway) and forcing the TTL, using "ip route add". > I don't believe this can be done with 'ip route' - ttl parameter only exists for 'ip tunnel'. > At this point, we really should get someone that can login in shein to > do a reverse tracepath to your IP... > I contacted debian-admins@lists.debian.org, hope that was appropriate. -- Gerald Turner Email: gturner@unzane.com JID: gturner@unzane.com GPG: 0xFA8CD6D5 21D9 B2E8 7FE7 F19E 5F7D 4D0C 3FA0 810F FA8C D6D5
Attachment:
pgpQEeBc3Ehvp.pgp
Description: PGP signature