Re: Comcast NOC - Bad IPv6 Routing

2020-02-16 Thread Robert Webb
IPv4 looks like I would expect traversing Charlottesville, VA then to Ashburn, VA. This is what I am used to seeing. Tracing route to 73.214.xxx.xxx over a maximum of 30 hops: 1<1 ms<1 ms<1 ms 192.168.1.1 2 7 ms11 ms 9 ms 96.120.80.37 3 7 ms 9 ms 7 ms

Re: Comcast NOC - Bad IPv6 Routing

2020-02-15 Thread Ross Tajvar
Interesting - does a v4 traceroute follow the same path? I.e. Richmond CRAN -> ibone Atlanta -> ibone Ashburn -> Pitt CRAN Not having detailed knowledge of Comcast's network, I'd expect the Richmond CRAN has a link to the ibone in Ashburn since it's fairly close (though there may be a closer ibone

Comcast NOC - Bad IPv6 Routing

2020-02-15 Thread Robert Webb
Could someone from Comcast NOC contact me off list. Looks like IPv6 routing from Richmond, VA to Grafton, WV has issues. IPSEC tunnel between gets less than 5Mbps over IPv6, switching endpoints to IPv4, I get the full 25Mbps down capability of the WV connection. Traceroute looks like below: Trac