IPv6 support in NJ

[jberwick]

What's the status of IPv6 support in southern New Jersey?  I have checked every few months for the past two years or so, and the results appear to be the same.  My firewall requests and receives a /56 prefix.  I carve out a /64 for my inside test network, and this is the traceroute I get: (I always seem to get a prefix inside of 2600:4040:E110::/48)

In the case below, I was assigned 2600:4040:E110:DB00::/56 via PD.  My test inside interface ended up at 2600:4040:E110:DB00:FF::1, and my test client on that interface ended up at 2600:4040:E110:DB00:2A3:8EFF:FEEC:E5EB, although I see the same results when trying directly from FF::1.

Tracing the route to lga34s38-in-x0e.1e100.net (2607:F8B0:4006:822::200E)

1 2600:4040:E110:DB00:FF::1 5 msec 1 msec 1 msec
2 2600:4040:E110::1 2 msec 11 msec 5 msec
3 2600:4000:1:222::D2 8 msec
2600:4000:1:222::D0 11 msec
2600:4000:1:222::D2 6 msec
4 * * *
5 *

My traffic gets through my firewall and out into Verizon, but then it dies at hop four every time.

Externally, it looks like there is a BGP announcement covering the /56 I am receiving:

route-views>show ipv6 route 2600:4040:E110:DB00:FF::1
Routing entry for 2600:4040:E000::/36
Known via "bgp 6447", distance 20, metric 0, type external
Route count is 1/1, share count 0
Routing paths:
2001:470:0:1A::1
MPLS label: nolabel
Last updated 2w6d ago

Trying to reach an address in the /56 from outside of Verizon, however, just loops:

route-views>traceroute ipv6 2600:4040:E110:DB00:FF::1
Type escape sequence to abort.
Tracing the route to 2600:4040:E110:DB00:FF::1

1 2001:468:D01:33::1 [AS 3582] 48 msec 48 msec 48 msec
2 FCFB:9D69:EF7F:9400::1 [AS 6453] 48 msec 1 msec 1 msec
3 vl-3402-gw.uoregon.edu (2607:8400:2EFD:22::1) [AS 3582] 36 msec
vl-3462-gw.uoregon.edu (2607:8400:2EFD:20::1) 1 msec
vl-3402-gw.uoregon.edu (2607:8400:2EFD:22::1) 44 msec
4 2607:8400:2EFD:D414::1 [AS 3582] 2 msec
2607:8400:2EFD:D314::1 1 msec 1 msec
5 0.et-0-3-0.cc-bdr1-gw.uoregon.edu (2607:8400:2EFD:C9FF::249) [AS 3582] 2 msec
2607:8400:2EFD:CAFF::249 2 msec 5 msec
6 2607:8400:2EFD:C9FE::246 [AS 3582] 1 msec 2 msec
2607:8400:2EFD:CAFE::246 2 msec
7 eugn-oh-pe-02.net.linkoregon.org (2605:BC80:200F:A::1) [AS 3701] 2 msec 1 msec 2 msec
8 * * *
9 2001:1900::3:208 [AS 3356] 17 msec * *
10 eugn-oh-pe-02.net.linkoregon.org (2605:BC80:200F:A::1) [AS 3701] 1 msec * *
11 * * *

I get a similar result from any AS I source traffic from.

I can release and request a new prefix but get the same results with any /56 I get assigned.

I have no idea where to go for support for this type of problem.  This is on residential fios 1g service.

[smith6612]

Normally I would say Verizon's tech support. That would be the best place to report this sort of thing. What you're seeing is a situation where the Netblock you've received is configured locally and can route in and out of your central office, but there is likely a route filter configured on the Verizon backbone which isn't permitting traffic to or from your IPv6 subnet. It's a reasonably quick fix for any network engineer. Route filters are pretty common, and a lot of networks utilize them to prevent subnets that are known to be unallocated within the provider's network, from routing across the backbone.

I just fear that you might run into a problem trying to explain to tech support that the issue isn't with your home network, your own router, or with IPv6 being enabled.

I had this same situation happen with an another Enterprise Fiber provider I use. The Static IPv6 allocation I received for both my router's Transit Address, as well as the /48 block of IPv6 for me to route in my network, was being filtered out at the backbone, but was being properly announced in BGP. A quick call to the provider's NOC with some traceroutes showing the problem, and the routing was fixed within a few hours.