|
Ticket ID: SIXXS #709283 Ticket Status: User PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
IPv4 routing problem blocking static tunnel to uschi02
![[us]](/s/countries/us.gif) Carmen Sandiego on Monday, 14 April 2008 21:22:39
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
This concerns handle: GNI1-SIXXS
Tunnel: T14086 / 2001:4978:f:88::2
Despite uschi02 status being up and my knowledge that others are connecting through it with no issues, There's an IPv4 routing issue between pccwbtn.net and your.org that's blocking my tunnel traffic.
From my end of the tunnel at 209.144.225.87:
gneff@neuron-/home/gneff$ traceroute 216.14.98.22
traceroute to 216.14.98.22 (216.14.98.22), 64 hops max, 40 byte packets
1 host65.fxol.com (209.144.225.65) 0.681 ms 0.469 ms 0.737 ms
2 border1.fe5-9.appserve-2.ext1a.dal.pnap.net (216.52.189.81) 0.864 ms 1.445 ms 0.866 ms
3 core1.tge5-2-bbnet2.ext1.dal.pnap.net (216.52.191.103) 1.488 ms 2.723 ms 4.240 ms
4 ae0.411.ar1.DAL2.gblx.net (208.51.41.57) 2.731 ms 1.581 ms 1.736 ms
5 64.213.176.242 (64.213.176.242) 24.726 ms 24.721 ms 24.354 ms
6 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 24.847 ms 24.757 ms 24.853 ms
7 * * *
:: snip ::
64 * * *
I can ping and traceroute to 216.14.98.22 from other locations with no issues.
I've been getting automated tunnel down warning E-mails (and point deductions) for 4 days now, despite this being completely out of my control or that of my ISP's.
Thanks,
Glen Neff
gneff dot trioptimum dot com
gneff@neuron-/home/gneff$ uname -a
FreeBSD neuron.subneural.net 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #6: Thu Jan 31 10:43:40 EST 2008 gneff@neuron.subneural.net:/usr/obj/usr/src/sys/neuron i386
gneff@neuron-/home/gneff$ ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet6 fe80::2c0:9fff:fe46:39b3%em0 prefixlen 64 scopeid 0x1
inet 209.144.225.87 netmask 0xffffffe0 broadcast 209.144.225.95
inet 209.144.225.88 netmask 0xffffffff broadcast 209.144.225.88
inet 209.144.225.89 netmask 0xffffffff broadcast 209.144.225.89
inet6 2001:4978:14d::87 prefixlen 64
inet6 2001:4978:14d::88 prefixlen 64
inet6 2001:4978:14d::89 prefixlen 64
ether 00:c0:9f:46:39:b3
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
ether 00:c0:9f:46:39:b4
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 209.144.225.87 --> 216.14.98.22
inet6 fe80::2c0:9fff:fe46:39b3%gif0 prefixlen 64 scopeid 0x4
inet6 2001:4978:f:88::2 prefixlen 64
gneff@neuron-/home/gneff$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 209.144.225.65 UGS 0 406525 em0
127.0.0.1 127.0.0.1 UH 0 98201 lo0
209.144.225.64/27 link#1 UC 0 0 em0
209.144.225.65 00:01:63:8d:7c:54 UHLW 2 0 em0 1034
209.144.225.66 00:e0:81:24:16:37 UHLW 1 14 em0 68
209.144.225.87 00:c0:9f:46:39:b3 UHLW 1 18 lo0
209.144.225.88 00:c0:9f:46:39:b3 UHLW 1 9 lo0 =>
209.144.225.88/32 link#1 UC 0 0 em0
209.144.225.89 00:c0:9f:46:39:b3 UHLW 1 14 lo0 =>
209.144.225.89/32 link#1 UC 0 0 em0
209.144.225.94 00:e0:81:24:16:37 UHLW 1 0 em0 68
Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0 =>
default 2001:4978:f:88::1 UGS gif0
::1 ::1 UHL lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
2001:4978:f:88::/64 link#4 UC gif0
2001:4978:f:88::2 link#4 UHL lo0
2001:4978:14d::/64 link#1 UC em0
2001:4978:14d::87 00:c0:9f:46:39:b3 UHL lo0
2001:4978:14d::88 00:c0:9f:46:39:b3 UHL lo0
2001:4978:14d::89 00:c0:9f:46:39:b3 UHL lo0
fe80::/10 ::1 UGRS lo0
fe80::%em0/64 link#1 UC em0
fe80::2c0:9fff:fe46:39b3%em0 00:c0:9f:46:39:b3 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#3 UHL lo0
fe80::%gif0/64 link#4 UC gif0
fe80::2c0:9fff:fe46:39b3%gif0 link#4 UHL lo0
ff01:1::/32 link#1 UC em0
ff01:3::/32 ::1 UC lo0
ff01:4::/32 link#4 UC gif0
ff02::/16 ::1 UGRS lo0
ff02::%em0/32 link#1 UC em0
ff02::%lo0/32 ::1 UC lo0
ff02::%gif0/32 link#4 UC gif0
gneff@neuron-/home/gneff$ traceroute6 2001:4978:f:88::1
traceroute6 to 2001:4978:f:88::1 (2001:4978:f:88::1) from 2001:4978:f:88::2, 64 hops max, 12 byte packets
1 * * *
2 * * *
: snip :
64 * * *
gneff@neuron-/home/gneff$
IPv4 routing problem blocking static tunnel to uschi02
Seems there is something odd at your end of the path...
traceroute to 209.144.225.87 (209.144.225.87), 64 hops max, 40 byte packets
1 ge-0.0.0-30.core1.chi.bb.your.org (216.14.98.21) 1.686 ms 10.684 ms 1.200 ms
2 c3066.ge1-48.ar1.ord1.us.scnet.net (64.202.111.38) 1.173 ms
c3066.ge1-48.ar2.ord1.us.scnet.net (64.202.111.34) 1.360 ms 1.236 ms
3 xe-1-0-0.cr1.ord1.us.scnet.net (216.246.95.241) 1.172 ms 47.003 ms 1.223 ms
4 tge9-3-10G.ar1.ord1.us.scnet.net (216.246.50.154) 1.631 ms 1.290 ms 1.165 ms
5 144.232.8.97 (144.232.8.97) 1.285 ms 1.279 ms
sprint-ic-122344-chi-bb1.c.telia.net (213.248.84.226) 1.158 ms
6 sl-bb22-chi-2-0.sprintlink.net (144.232.20.20) 1.486 ms 1.425 ms 1.536 ms
7 sl-bb21-kc-3-0.sprintlink.net (144.232.20.129) 12.517 ms 12.297 ms 12.336 ms
8 sl-crs2-fw-0-15-5-0.sprintlink.net (144.232.8.63) 31.920 ms 31.904 ms 32.111 ms
9 sl-st20-dal-13-0.sprintlink.net (144.232.20.83) 31.901 ms 32.044 ms 32.138 ms
10 144.228.250.114 (144.228.250.114) 24.605 ms 24.659 ms 24.495 ms
11 * * *
12 * * *
Clearly this is some IPv4 routing issue, but where exactly is now the question.
I've been getting automated tunnel down warning E-mails (and point deductions) for 4 days now, despite this being completely out of my control or that of my ISP's.
You receive the robot's notification already for four days, and apparently are really sure that it is not you or your ISP causing it, and only file a ticket about this now? Odd.
IPv4 routing problem blocking static tunnel to uschi02
Carmen Sandiego on Tuesday, 15 April 2008 02:49:59
Is that traceroute you pasted from the uschi02 PoP?
I have, for good measure, filed a ticket with my ISP as well.
IPv4 routing problem blocking static tunnel to uschi02
Carmen Sandiego on Tuesday, 15 April 2008 13:56:12
gneff@neuron-/home/gneff$ traceroute 216.14.98.22
traceroute to 216.14.98.22 (216.14.98.22), 64 hops max, 40 byte packets
1 host65.fxol.com (209.144.225.65) 351.943 ms 390.827 ms 11.847 ms
2 border1.fe5-9.appserve-2.ext1a.dal.pnap.net (216.52.189.81) 0.986 ms 1.824 ms 1.612 ms
3 core1.tge5-1-bbnet1.ext1.dal.pnap.net (216.52.191.38) 12.233 ms 2.594 ms 1.614 ms
4 ae0.411.ar1.DAL2.gblx.net (208.51.41.57) 1.112 ms 1.207 ms 1.612 ms
5 64.213.176.242 (64.213.176.242) 138.916 ms 25.477 ms 233.491 ms
6 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 25.464 ms 25.154 ms 26.342 ms
7 sixxs.cx01.chi.bb.your.org (216.14.98.22) 25.971 ms 25.893 ms 25.223 ms
gneff@neuron-/home/gneff$
It's resolved. It appears it was at the PoP's end.
IPv4 routing problem blocking static tunnel to uschi02
How exactly was this a problem at the PoP end?
If you didn't notice above, it was perfectly able to almost reach your endpoint with at least a traceroute.
Don't point fingers unless you have conclusive material.
IPv4 routing problem blocking static tunnel to uschi02
Carmen Sandiego on Tuesday, 15 April 2008 15:46:16
My desire was for a solution, not to place blame.
The successful traceroute from my end looks identical the the previous unsuccessful one, with the exception of the last hop.
The traceroute you pasted looked very different. I would suspect that now it's working a traceroute from uschi02 to 209.144.225.87 would look very much like it does from my end.
IPv4 routing problem blocking static tunnel to uschi02
You have clearly never heard of dynamic routing or asymmetrical paths. The paths don't have to be the same, and can change from one moment to the other.
You can do your own traceroutes from almost every PoP using the traceroute tool on this site. Verify it yourself.
State change: user
The state of this ticket has been changed to user
|
![[ch]](/s/countries/ch.gif)
on Monday, 14 April 2008 21:25:41
Posting is only allowed when you are