[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Verizon FIOS IPv6?

Subject: Verizon FIOS IPv6?
From: bosch at adacore.com (Geert Bosch)
Date: Fri, 10 Jan 2014 00:17:53 -0500
In-reply-to: <[email protected]>
References: <CAL9jLaaKapZnNz6QdpbLmQiBSFWOYYi0Eiyz6Y2bb_UMPg18DQ@mail.gmail.com> <CAPZUUwUi3AxGiT6N8OYzHJm859YYgAZvtV5sJJPqNxPhLA_F5Q@mail.gmail.com> <CAL9jLaYeatS-YmfB3MdHB9HPOC2CY5DTAc3vWkNoMqXvEGz3vw@mail.gmail.com> <[email protected]> <[email protected]> <CAOtTuarZKqp7bNJ55RNo5gb3Pg+fKYZ86Lji8DTdZ91pwcoxUA@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On Jan 9, 2014, at 14:32, Stephen Frost <sfrost at snowman.net> wrote:

> Sure, entirely possible, but I'd be investigating into why because
> clearly there's a better ipv4 route than that being used, if ipv6
> tunneled over ipv4 is faster.  A bit of difference is fine, but it
> sounded like more than 'a bit'.

Of course it's a routing issue. At AdaCore (AS32019), we have very
good connectivity with level3 (<2ms), but the Verizon/Level3 path seems
variable and generally slow.

Here are the relevant bits.  Note that I've seen lots of different
routings for IPv4 traffic, routing over Cogent, Alter.net, Above.net,
but not so much when using the HE tunnel. Of course, I could
just ascribe this to NSA traffic redirection/inspection, or some
traffic engineering by a New Jersey governor, but I guess VZ
might have their own reasons for subpar routing. It always seems
as if VZ is avoiding L3.

The Hurricane Electric tunnel server I'm using is 209.51.161.14.

kwai:~%ping -i0.2 -c20  209.51.161.14
...
--- 209.51.161.14 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 3819ms
rtt min/avg/max/mdev = 1.604/1.763/2.497/0.205 ms


potomac:~%ping -i0.2 -c20 209.51.161.14
...
--- 209.51.161.14 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 6.832/8.040/9.152/0.720 ms

The sum of these times is just 10ms. 

Now, look at the resulting time for my IPv4 tunnel endpoint:
kwai:~%ping -i0.2 -c20 72.69.184.141
...
--- 72.69.184.141 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 3817ms
rtt min/avg/max/mdev = 22.843/25.422/27.725/1.538 ms

That's where the difference is.

With trace routes:
kwai:~%traceroute 209.51.161.14
traceroute to 209.51.161.14 (209.51.161.14), 30 hops max, 60 byte packets
 1  jordan.gnat.com (205.232.38.200)  5.402 ms  5.483 ms  5.535 ms
 2  towerstream-gw.gnat.com (69.38.252.177)  2.113 ms  2.119 ms  2.159 ms
 3  g4-0.cr.nyc1.ny.towerstream.com (69.38.244.13)  2.253 ms  2.260 ms  2.296 ms
 4  br.nyc0203.ny.towerstream.net (69.38.138.110)  3.181 ms  3.190 ms  3.209 ms
 5  64.125.173.225 (64.125.173.225)  3.299 ms  3.308 ms  3.394 ms
 6  xe-1-2-1.er2.lga5.us.above.net (64.125.31.166)  4.224 ms  2.113 ms  2.123 ms
 7  core1.nyc4.he.net (198.32.118.57)  3.733 ms  10.968 ms  10.960 ms
 8  tserv1.nyc4.he.net (209.51.161.14)  2.088 ms  1.694 ms  1.870 ms

kwai:~%traceroute 72.69.184.141
traceroute to 72.69.184.141 (72.69.184.141), 30 hops max, 60 byte packets
 1  jordan.gnat.com (205.232.38.200)  5.888 ms  6.295 ms  6.442 ms
 2  towerstream-gw.gnat.com (69.38.252.177)  2.062 ms  2.066 ms  2.108 ms
 3  g4-0.cr.nyc1.ny.towerstream.com (69.38.244.13)  2.201 ms  2.206 ms  2.319 ms
 4  xe-4-0-1.edge4.NewYork1.Level3.net (4.28.130.57)  3.124 ms  3.129 ms  3.156 ms
 5  vlan70.csw2.NewYork1.Level3.net (4.69.155.126)  3.248 ms vlan60.csw1.NewYork1.Level3.net (4.69.155.62)  3.299 ms vlan80.csw3.NewYork1.Level3.net (4.69.155.190)  3.304 ms
 6  ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73)  4.702 ms ae-62-62.ebr2.NewYork1.Level3.net (4.69.148.33)  2.372 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73)  2.392 ms
 7  4.69.201.42 (4.69.201.42)  2.377 ms ae-45-45.ebr2.NewYork2.Level3.net (4.69.141.22)  2.366 ms ae-47-47.ebr2.NewYork2.Level3.net (4.69.201.34)  2.407 ms
 8  ae-1-51.edge2.NewYork2.Level3.net (4.69.138.195)  2.369 ms  2.518 ms  2.529 ms
 9  po6-20G.ar6.NYC1.gblx.net (208.51.134.113)  18.468 ms  18.474 ms  18.655 ms
10  0.ae11.BR3.NYC4.ALTER.NET (204.255.168.193)  20.372 ms  19.718 ms  17.999 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *C^Cpotomac:%traceroute 209.51.161.14
traceroute to 209.51.161.14 (209.51.161.14), 64 hops max, 52 byte packets
 1  wireless_broadband_router (192.168.1.1)  1.238 ms  0.852 ms  0.805 ms
 2  l100.nycmny-vfttp-102.verizon-gni.net (71.190.186.1)  5.275 ms  5.189 ms  5.732 ms
 3  g1-15-4-1.nycmny-lcr-22.verizon-gni.net (130.81.218.160)  9.572 ms  7.315 ms  8.120 ms
 4  so-3-1-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.199.12)  7.135 ms
    ae2-0.ny5030-bb-rtr1.verizon-gni.net (130.81.199.178)  7.228 ms
    so-5-0-0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.22.18)  7.047 ms
 5  0.xe-10-0-0.br3.nyc4.alter.net (152.63.24.109)  7.925 ms
    0.xe-11-3-0.br2.nyc4.alter.net (152.63.23.137)  7.892 ms
    0.xe-10-0-0.br3.nyc4.alter.net (152.63.24.109)  7.114 ms
 6  204.255.168.190 (204.255.168.190)  7.497 ms  10.291 ms  8.601 ms
 7  hurricane-electric-llc-new-york.tengigabitethernet1-3.ar5.nyc1.gblx.net (64.209.92.98)  8.228 ms  7.101 ms  17.883 ms
 8  tserv1.nyc4.he.net (209.51.161.14)  8.962 ms  8.231 ms  6.681 ms
potomac:%traceroute kwai.gnat.com
traceroute to kwai.gnat.com (205.232.38.4), 64 hops max, 52 byte packets
 1  wireless_broadband_router (192.168.1.1)  4.037 ms  2.140 ms  2.572 ms
 2  l100.nycmny-vfttp-102.verizon-gni.net (71.190.186.1)  6.554 ms  7.270 ms  7.757 ms
 3  g0-14-3-3.nycmny-lcr-22.verizon-gni.net (130.81.104.44)  11.689 ms  9.961 ms  9.519 ms
 4  so-6-1-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.151.224)  6.582 ms
    ae0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.209.126)  7.804 ms
    ae4-0.ny5030-bb-rtr1.verizon-gni.net (130.81.163.224)  7.244 ms
 5  0.xe-10-1-0.br1.nyc1.alter.net (152.63.18.225)  8.677 ms  8.347 ms  8.810 ms
 6  te-7-3-0.edge2.newyork2.level3.net (4.68.111.137)  27.316 ms
    ae11.edge2.newyork.level3.net (4.68.62.41)  29.472 ms  28.588 ms
 7  vlan51.ebr1.newyork2.level3.net (4.69.138.222)  25.019 ms
    vlan52.ebr2.newyork2.level3.net (4.69.138.254)  23.100 ms
    vlan51.ebr1.newyork2.level3.net (4.69.138.222)  23.718 ms
 8  ae-48-48.ebr2.newyork1.level3.net (4.69.201.49)  23.335 ms
    ae-46-46.ebr1.newyork1.level3.net (4.69.201.41)  24.846 ms
    4.69.201.37 (4.69.201.37)  25.430 ms
 9  ae-62-62.csw1.newyork1.level3.net (4.69.148.34)  24.207 ms
    ae-92-92.csw4.newyork1.level3.net (4.69.148.46)  24.709 ms
    ae-82-82.csw3.newyork1.level3.net (4.69.148.42)  27.682 ms
10  ae-2-70.edge4.newyork1.level3.net (4.69.155.84)  23.184 ms  22.921 ms
    ae-4-90.edge4.newyork1.level3.net (4.69.155.210)  25.784 ms
11  bandcon.edge4.newyork1.level3.net (4.28.130.58)  8.355 ms  8.672 ms  8.877 ms
12  e1-1.cr.nyc0007.c.ny.towerstream.net (69.38.231.173)  27.119 ms  25.984 ms  26.617 ms
13  jordan-towerstream.gnat.com (69.38.252.178)  28.139 ms  29.953 ms  29.601 ms
14  kwai.gnat.com (205.232.38.4)  28.848 ms  26.241 ms  28.212 ms

References:
- Verizon FIOS IPv6?
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- Verizon FIOS IPv6?
  - From: asr at latency.net (Adam Rothschild)
- Verizon FIOS IPv6?
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- Verizon FIOS IPv6?
  - From: sfrost at snowman.net (Stephen Frost)
- Verizon FIOS IPv6?
  - From: andrew.fried at gmail.com (Andrew Fried)
- Verizon FIOS IPv6?
  - From: iggdawg at gmail.com (Ian Bowers)
- Verizon FIOS IPv6?
  - From: streiner at cluebyfour.org (Justin M. Streiner)
- Verizon FIOS IPv6?
  - From: bosch at adacore.com (Geert Bosch)
- Verizon FIOS IPv6?
  - From: sfrost at snowman.net (Stephen Frost)
- Verizon FIOS IPv6?
  - From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
- Verizon FIOS IPv6?
  - From: sfrost at snowman.net (Stephen Frost)

Prev by Date: [Off-Topic] Ubersmith
Next by Date: Experiences with Spamhaus BGP DROP, EDROP and BGPCC BGP feeds
Previous by thread: Verizon FIOS IPv6?
Next by thread: Verizon FIOS IPv6?
Index(es):
- Date
- Thread