|
to NetDog
Re: [IPv6] Evidence of Comcast IPv6 CPE Dual Stack (CPE and CPEP1) Mableton, GA 2) Zoom 5341J --> Netgear WNDR4500 |
|
|
to NetDog
Crystal, MN pfSense 2.1-RC1 (i386, built on Wed Aug 28 16:55:02 EDT 2013) |
|
djoye join:2009-08-15 Murfreesboro, TN |
to NetDog
Nashville 5341j Netgear WNDR4300 |
|
Chris 313Because It's Geekier Premium Member join:2004-07-18 Houma, LA ·AT&T FTTP ·Comcast XFINITY
2 recommendations |
to NetDog
Houma, La Motorola SB6141 Asus RT-N66U Windows XP SP3 From » test-ipv6.com/ - Your IPv4 address on the public Internet appears to be 75 (COMCAST-22258 - Comcast Cable Communications Holdings, Inc) Your IPv6 address on the public Internet appears to be 2601 (COMCAST-7922 - Comcast Cable Communications, Inc.) Since you have IPv6, we are including a tab that shows how well you can reach other IPv6 sites. [more info] Good news! Your current configuration will continue to work as web sites enable IPv6. Rediness score: 10/10 Keep up with the good upgrades, NetDog. Your IPv6 upgrades have spread to Louisiana and the Cisco 10k CMTSs that we have here! |
|
Trips join:2002-06-14 Augusta, GA 2 edits |
to NetDog
Augusta, GA Arris CM820A Linksys E4200v2 Windows 7 Ultimate 64-bit |
|
|
willmo join:2013-06-03 Seattle, WA
1 recommendation |
willmo
Member
2013-Aug-15 3:20 pm
Working now, everything's 10/10. Thanks guys! This is about as good as it gets for residential ISP support. |
|
willmo |
to netcool
Now packets from my LAN aren't even making it to hop 3 in the traceroute I posted. PMs sent. I did have an issue a couple times where OpenWRT's new DHCPv6 client (odhcp6c) freaked out and started sending packets out the WAN interface as fast as it could (many thousands per second), using 100% CPU. This happened once a couple months ago and again a few days ago, which was why I decided to update OpenWRT Tuesday night. I didn't really have a chance to investigate since at the time I just needed my router to stop being slow (killing the process fixed it). I'd been wondering if that would cause me to be IPv6-blacklisted or something. But hopefully since IPv6 wasn't enabled then (at least the first time) the packets never made it to the DOCSIS side of my modem... |
|
netcool Premium Member join:2008-11-05 Englewood, CO |
to willmo
said by willmo:Clearly packets from my LAN *are* making it out of my router into Comcast's network (the 2001:558 addresses), but Comcast is not routing packets to and/or from my LAN. Can you run your tests again? Your CMTS wasn't properly advertising its IPV6 routes, we corrected the config and you should be good now. |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL |
to willmo
said by willmo:Seattle, WA (Capitol Hill) SB6121 Netgear WNDR3700v1 OpenWRT trunk r37767 (I build it from source myself) Performance Your CMTS is enabled for IPv6 CPE, I just checked send me your CM MAC please so I can check your modem. |
|
willmo join:2013-06-03 Seattle, WA |
willmo
Member
2013-Aug-15 5:17 am
Actually it appears that my router is working, and Comcast just hasn't finished enabling IPv6 here yet. My router itself has full IPv6 connectivity, but machines on my LAN can't reach the Internet. At first I assumed my router wasn't routing, but traceroute6 says otherwise. On the router: # traceroute6 ipv6.test-ipv6.com
traceroute to ipv6.test-ipv6.com (2001:470:1:18::119), 30 hops max, 16 byte packets
1 2001:558:600a:63::1 (2001:558:600a:63::1) 7.467 ms 7.149 ms 19.396 ms
2 2001:558:a2:2037::1 (2001:558:a2:2037::1) 8.975 ms 9.811 ms 10.053 ms
3 ae-20-0-ar03.seattle.wa.seattle.comcast.net (2001:558:a0:212::1) 10.455 ms 9.788 ms 9.513 ms
4 he-1-7-0-0-11-cr01.seattle.wa.ibone.comcast.net (2001:558:0:f741::1) 10.425 ms 9.843 ms 11.317 ms
5 if-xe-0-3-1.0.tcore1.00S-Seattle.ipv6.as6453.net (2001:5a0:1f00:200::d) 9.157 ms 7.804 ms 10.116 ms
6 if-ae14.2.tcore1.PDI-PaloAlto.ipv6.as6453.net (2001:5a0:200:400::e) 36.608 ms 32.630 ms 30.402 ms
7 if-ae2.2.tcore2.PDI-PaloAlto.ipv6.as6453.net (2001:5a0:1200:300::2) 27.083 ms 25.687 ms 27.414 ms
8 if-ae5.2.tcore2.SQN-SanJose.ipv6.as6453.net (2001:5a0:1500:500::1) 48.423 ms 54.270 ms 36.242 ms
9 gigabitethernet5-16.core1.sjc2.he.net (2001:470:0:196::1) 38.951 ms 38.941 ms 36.617 ms
10 10gigabitethernet1-1.core1.fmt1.he.net (2001:470:0:2f::1) 37.464 ms 36.564 ms 40.913 ms
11 ip119.gigo.com (2001:470:1:18::119) 37.621 ms 44.905 ms 39.549 ms
On a machine on my LAN: $ traceroute6 ipv6.test-ipv6.com
traceroute6 to ipv6.test-ipv6.com (2001:470:1:18::119) from 2601:8:b1xx:xxxx:xxxx:xxxx:xxxx:xxxx, 64 hops max, 12 byte packets
1 2601:8:b1xx:xxxx::1 1.131 ms 3.477 ms 1.396 ms
2 2001:558:4082:63::1 9.603 ms 12.047 ms 10.439 ms
3 2001:558:a2:2034::1 18.784 ms 17.231 ms 16.693 ms
[wait a while]
^C
Clearly packets from my LAN *are* making it out of my router into Comcast's network (the 2001:558 addresses), but Comcast is not routing packets to and/or from my LAN. It's interesting how they do this in stages: last night my router wasn't getting any DHCPv6 responses, but it was spewing messages about being unable to reach several addresses in 2001:558:4082:63::/64. I assume it was receiving ICMPv6 packets and trying to respond, but couldn't because it didn't have an IPv6 address (?). Oh well, I'm patient. :-) Seattle, WA (Capitol Hill) SB6121 Netgear WNDR3700v1 OpenWRT trunk r37767 (I build it from source myself) Performance |
|
willmo |
to NetDog
Looks like they're in the midst of enabling it here. comcast6.net says my CMTS is supported. test-ipv6.com says I have nothing, but machines on my LAN have an IP...or several...
en0: flags=8863 mtu 1500 ether 20:c9:xx:xx:xx:xx inet6 fe80::xxxx:xxxx:xxxx:xxxx%en0 prefixlen 64 scopeid 0x4 inet6 2601:8:b1xx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf inet6 2601:8:b1xx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf temporary inet6 fd9f:xxxx:xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 deprecated autoconf inet6 2601:8:b1xx:xxxx::xxx prefixlen 64 inet 192.168.1.x netmask 0xffffff00 broadcast 192.168.1.255 media: autoselect status: active
Very possible that my router is misconfigured or buggy (OpenWRT trunk from last night, with some old config files that probably need to be updated). I'm looking into it. |
|
Madtown Premium Member join:2008-04-26 93637-2905 |
to NetDog
Madera, Ca (Parkwood) SB6121 Netgear WNDR3700 Performance |
|
your moderator at work
hidden :
|
PaulGo join:2005-01-29 Gaithersburg, MD |
to Oregonian
Re: [IPv6] Evidence of Comcast IPv6 CPE Dual Stack (CPE and CPEPCongratulations! You appear to have both IPv4 and IPv6 internet working. If a publisher publishes to IPv6, your browser will connect using IPv6. Your browser prefers IPv6 over IPv4 when given the choice (this is the expected outcome).
Your DNS server (possibly run by your ISP) appears to have IPv6 internet access. Your Readiness Scores 10/10 Important Measure: Your IPv4 stability, when sites offer both IPv4 and IPv6 10/10 Long-Term: Your IPv6 readiness when sites go IPv6-only - NOT CRITICAL right now
North Potomac, MD Netgear R6300 router Motorola SB6141 modem |
|
Oregonian Premium Member join:2000-12-21 West Linn, OR |
to NetDog
West Linn, Oregon SB6120 modem and a Linksys EA4500 router. |
|
grod46 join:2012-11-25 Fresno, CA |
to NetDog
|
|
ARRIS SB8200 Asus RT-AC68
|
to NetDog
Portland, Oregon Motorola SB6120 to a Netgear WNDR4500 |
|
Scilicet (banned)Spaced Out join:2005-04-11 Aurora, CO 1 edit |
to NetDog
1. Aurora, CO 2. Modem: Motorola SB6120 3. Neatgear WGR614v10 (not yet configured) I hadn't noticed this until today. The modem has been at IPv4 for I don't know how long. I've been troubleshooting a network problem and the IPv6 popped up on the modem status page. Edit: It would seem that the Netgear WGR614v10 does not support IPv6. Wonderful! |
|
bradyrYCCD - Network Operations Premium Member join:2008-10-27 Sonora, CA (Software) pfSense Netgear CM1200 Ubiquiti UAP-AC-HD
|
to NetDog
IPv6 Connection Type: Native with DHCP-PD WAN IPv6 Address: 2001:558:6012:38:4c81:eba6:7420:3b8a/64 WAN IPv6 Gateway: fe80::201:5cff:fe3d:ac41 LAN IPv6 Address: 2601:c:9c80:7b:62a4:4cff:fe29:6cb8/64 LAN IPv6 Link-Local Address: fe80::62a4:4cff:fe29:6cb8/64 DHCP-PD: Enabled LAN IPv6 prefix: 2601:c:9c80:7b::/64 DNS Address: 2001:558:feed::1 2001:558:feed::2
lit up IPv6 for a day and a half just for because. Everything seems ready to rock and roll. Might turn it on permanently once I get some proper IPv6 firewall rules setup.
-Sonora, CA (95370) -Zoom 5341J -ASUS rt-n66u running latest Merlin firmware (3.0.0.4.372.30_2 at the time of this post)
|
|
|
to NetDog
1. Salem, OR 2. Modem: Motorola SB6121 3. Linksys E3000, Running Tomato USB (Toastman, latest) |
|
|
to NetDog
1. Wilmette, IL (60091) 2. Modem: Motorola SurfBoard SB6141 3. Linksys EA2700 N600 Dual-Band Wireless-N Router
|
|
JNhome join:2012-07-15 Salinas, CA |
to NetDog
Went live in Salinas, CA (70mi south of San Jose) in June 2013 |
|
|
to NetDog
Winston Georgia ASUS RT-N66U - Firmware 3.0.0.4.370_172-g85af9d0 I never got IPv6 address until my firmware was updated |
|
bgoodbodyBill G join:2002-05-08 North Truro, MA
1 recommendation |
to NetDog
The Cisco CMTS has begun. » www.comcast6.net/ |
|
pende_tim Premium Member join:2004-01-04 Selbyville, DE |
to NetDog
Have IPv6 running down here in Selbyville, DE 19975. Asus RT-N16/Tomato 1.28 behind a Zoom Model "J". |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
to NetDog
Add another D-Link router to the list of routers that seem to fully support Comcast's dual stack implementation. I've got to give D-Link a big thumbs up; they seem to be trying very hard to make their entire current residential/soho router product line IPv6 functional. Of course (as with most vendors) if you have an older hardware version that is not in current production, you will likely be out of luck unless your particular router is supported by OpenWRT, DDWRT, et al. Netgear EBR-2310-C1 firmware rev 3.01
|
|
your moderator at work
hidden :
|
artie join:2002-07-14 Panama City, FL |
to NetDog
Re: [IPv6] Evidence of Comcast IPv6 CPE Dual Stack (CPE and CPEP1) Panama City, Florida 2) Direct Connect w/ Windows 7 3) ^ |
|
jmsq join:2013-04-25 West Lafayette, IN |
to NetDog
1) West Lafayette, IN 2) Linksys E3000 running Tomato |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
to NetDog
Here are the test results using the D-Link DIR601-A1 with 1.04NA firmware I obtained from the D-Link Canadian web site: » www.dlink.com/ca/en/supp ··· =ca_revaThe D-Link US website does not have that firmware release, and it contains some significant improvements to IPv6 implementation over the 1.02NA firmware that is available on the D-Link US web site.
|
|