I recently noticed that Cox has started handing out IPv6 for me, but I seem to be running into some issues getting it to actually work on my devices. I have Cox Ultimate running through a Motorola/Arris SB6141 and a pfSense router. Here's some info from the SB6141:
Model Name: SB6141Vendor Name: MotorolaFirmware Name: SB_KOMODO-1.0.6.14-SCM01-NOSHBoot Version: PSPU-Boot(25CLK) 1.0.12.18m3Hardware Version: 7.0Serial Number: 3747<snip>
Right now, on the WAN side, I have pfSense to use DHCP6. I have selected the option to get a /56 prefix, and I've checked the box that says "Send an IPv6 prefix hint to indicate the desired prefix size for delegation".
On the LAN side, I have a DHCP6 server running to hand out IP addresses, tracking the WAN interface.
At this point, I can look at the output of dhcp6c, and see that it looks like Cox is giving me a /56 (from which pfSense is carving out several /64's ?).
[2.3-RELEASE][admin@pfsense]/root: /usr/local/sbin/dhcp6c -dDf -c /var/etc/dhcp6c_wan.conf em0Apr/18/2016 21:45:53: extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:<snip>Apr/18/2016 21:45:53: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directoryApr/18/2016 21:45:53: failed initialize control message authenticationApr/18/2016 21:45:53: skip opening control portApr/18/2016 21:45:53: <3>[interface] (9)Apr/18/2016 21:45:53: <5>[em0] (3)Apr/18/2016 21:45:53: <3>begin of closure [{] (1)Apr/18/2016 21:45:53: <3>[send] (4)Apr/18/2016 21:45:53: <3>[ia-na] (5)Apr/18/2016 21:45:53: <3>[0] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>comment [# request stateful address] (26)Apr/18/2016 21:45:53: <3>[send] (4)Apr/18/2016 21:45:53: <3>[ia-pd] (5)Apr/18/2016 21:45:53: <3>[0] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>comment [# request prefix delegation] (27)Apr/18/2016 21:45:53: <3>[request] (7)Apr/18/2016 21:45:53: <3>[domain-name-servers] (19)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[request] (7)Apr/18/2016 21:45:53: <3>[domain-name] (11)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[script] (6)Apr/18/2016 21:45:53: <3>["/var/etc/dhcp6c_wan_script.sh"] (31)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>comment [# we'd like some nameservers please] (35)Apr/18/2016 21:45:53: <3>end of closure [}] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[id-assoc] (8)Apr/18/2016 21:45:53: <13>[na] (2)Apr/18/2016 21:45:53: <13>[0] (1)Apr/18/2016 21:45:53: <13>begin of closure [{] (1)Apr/18/2016 21:45:53: <3>end of closure [}] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[id-assoc] (8)Apr/18/2016 21:45:53: <13>[pd] (2)Apr/18/2016 21:45:53: <13>[0] (1)Apr/18/2016 21:45:53: <13>begin of closure [{] (1)Apr/18/2016 21:45:53: <3>[prefix] (6)Apr/18/2016 21:45:53: <3>[::] (2)Apr/18/2016 21:45:53: <3>[/] (1)Apr/18/2016 21:45:53: <3>[56] (2)Apr/18/2016 21:45:53: <3>[infinity] (8)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[prefix-interface] (16)Apr/18/2016 21:45:53: <5>[em1] (3)Apr/18/2016 21:45:53: <3>begin of closure [{] (1)Apr/18/2016 21:45:53: <3>[sla-id] (6)Apr/18/2016 21:45:53: <3>[0] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>[sla-len] (7)Apr/18/2016 21:45:53: <3>[8] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>end of closure [}] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: <3>end of closure [}] (1)Apr/18/2016 21:45:53: <3>end of sentence [;] (1)Apr/18/2016 21:45:53: calledApr/18/2016 21:45:53: calledApr/18/2016 21:45:53: reset a timer on em0, state=INIT, timeo=0, retrans=383Apr/18/2016 21:45:53: a new XID (909103) is generatedApr/18/2016 21:45:53: set client ID (len 14)Apr/18/2016 21:45:53: set identity associationApr/18/2016 21:45:53: set elapsed time (len 2)Apr/18/2016 21:45:53: set option request (len 4)Apr/18/2016 21:45:53: set IA_PD prefixApr/18/2016 21:45:53: set IA_PDApr/18/2016 21:45:53: send solicit to ff02::1:2%em0Apr/18/2016 21:45:53: reset a timer on em0, state=SOLICIT, timeo=0, retrans=1088Apr/18/2016 21:45:53: receive advertise from fe80::6e41:6aff:fef2:69d9%em0 on em0Apr/18/2016 21:45:53: get DHCP option client ID, len 14Apr/18/2016 21:45:53: DUID: 00:01:<snip>Apr/18/2016 21:45:53: get DHCP option server ID, len 14Apr/18/2016 21:45:53: DUID: 00:01:<snip>Apr/18/2016 21:45:53: get DHCP option DNS, len 32Apr/18/2016 21:45:53: get DHCP option identity association, len 40Apr/18/2016 21:45:53: IA_NA: ID=0, T1=43200, T2=69120Apr/18/2016 21:45:53: get DHCP option IA address, len 24Apr/18/2016 21:45:53: IA_NA address: 2600:8804:<snip>:ee5b pltime=86400 vltime=86400Apr/18/2016 21:45:53: get DHCP option IA_PD, len 99Apr/18/2016 21:45:53: IA_PD: ID=0, T1=43200, T2=69120Apr/18/2016 21:45:53: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:53: IA_PD prefix: 2600:<snip>:900::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:53: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:53: IA_PD prefix: 2600:<snip>:b00::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:53: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:53: IA_PD prefix: 2600:<snip>:c00::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:53: server ID: 00:01:00:01:56:1b:d2:50:c8:1f:66:e6:50:b3, pref=-1Apr/18/2016 21:45:53: reset timer for em0 to 0.975451Apr/18/2016 21:45:54: picked a server (ID: 00:01:00:01:56:1b:d2:50:c8:1f:66:e6:50:b3)Apr/18/2016 21:45:54: a new XID (bf53d7) is generatedApr/18/2016 21:45:54: set client ID (len 14)Apr/18/2016 21:45:54: set server ID (len 14)Apr/18/2016 21:45:54: set IA addressApr/18/2016 21:45:54: set identity associationApr/18/2016 21:45:54: set elapsed time (len 2)Apr/18/2016 21:45:54: set option request (len 4)Apr/18/2016 21:45:54: set IA_PD prefixApr/18/2016 21:45:54: set IA_PD prefixApr/18/2016 21:45:54: set IA_PD prefixApr/18/2016 21:45:54: set IA_PDApr/18/2016 21:45:54: send request to ff02::1:2%em0Apr/18/2016 21:45:54: reset a timer on em0, state=REQUEST, timeo=0, retrans=977Apr/18/2016 21:45:54: receive reply from fe80::6e41:6aff:fef2:69d9%em0 on em0Apr/18/2016 21:45:54: get DHCP option client ID, len 14Apr/18/2016 21:45:54: DUID: 00:01:<snip>Apr/18/2016 21:45:54: get DHCP option server ID, len 14Apr/18/2016 21:45:54: DUID: 00:01:<snip>Apr/18/2016 21:45:54: get DHCP option DNS, len 32Apr/18/2016 21:45:54: get DHCP option identity association, len 46Apr/18/2016 21:45:54: IA_NA: ID=0, T1=43200, T2=69120Apr/18/2016 21:45:54: get DHCP option status code, len 2Apr/18/2016 21:45:54: status code: successApr/18/2016 21:45:54: get DHCP option IA address, len 24Apr/18/2016 21:45:54: IA_NA address: 2600:8804:<snip>:ee5b pltime=86400 vltime=86400Apr/18/2016 21:45:54: get DHCP option IA_PD, len 105Apr/18/2016 21:45:54: IA_PD: ID=0, T1=43200, T2=69120Apr/18/2016 21:45:54: get DHCP option status code, len 2Apr/18/2016 21:45:54: status code: successApr/18/2016 21:45:54: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:54: IA_PD prefix: 2600:<snip>:900::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:54: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:54: IA_PD prefix: 2600:<snip>:b00::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:54: get DHCP option IA_PD prefix, len 25Apr/18/2016 21:45:54: IA_PD prefix: 2600:<snip>:c00::/56 pltime=86400 vltime=86400Apr/18/2016 21:45:54: nameserver[0] 2001:578:3f::30Apr/18/2016 21:45:54: nameserver[1] 2001:578:3f:1::30Apr/18/2016 21:45:54: make an IA: PD-0Apr/18/2016 21:45:54: status code for PD-0: successApr/18/2016 21:45:54: create a prefix 2600:<snip>:900::/56 pltime=140733193474432, vltime=140733193474432Apr/18/2016 21:45:54: add an address 2600:<snip>:900:<snip>:4070/64 on em1Apr/18/2016 21:45:54: create a prefix 2600:<snip>:b00::/56 pltime=140733193474432, vltime=140733193474432Apr/18/2016 21:45:54: add an address 2600:<snip>:b00:<snip>:4070/64 on em1Apr/18/2016 21:45:54: create a prefix 2600:<snip>:c00::/56 pltime=140733193474432, vltime=140733193474432Apr/18/2016 21:45:54: add an address 2600:<snip>:c00:<snip>:4070/64 on em1Apr/18/2016 21:45:54: make an IA: NA-0Apr/18/2016 21:45:54: status code for NA-0: successApr/18/2016 21:45:54: create an address 2600:<snip>:ee5b pltime=86400, vltime=86400Apr/18/2016 21:45:54: add an address 2600:<snip>:ee5b/128 on em0Apr/18/2016 21:45:54: executes /var/etc/dhcp6c_wan_script.shApr/18/2016 21:46:04: script "/var/etc/dhcp6c_wan_script.sh" terminatedApr/18/2016 21:46:04: removing an event on em0, state=REQUESTApr/18/2016 21:46:04: removing server (ID: 00:01:00:01:56:1b:d2:50:c8:1f:66:e6:50:b3)Apr/18/2016 21:46:04: got an expected reply, sleeping.^C
And if I run ifconfig in SSH on pfSense, I see that the WAN side has a /128, and the LAN side has several /64's set up.
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>ether 00:22:<snip>inet6 fe80::222:4dff:feb1:406e%em0 prefixlen 64 scopeid 0x1inet <snip> netmask 0xffffff00 broadcast <snip>inet6 2600:8804:<snip>:9715 prefixlen 128nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>media: Ethernet autoselect (1000baseT <full-duplex>)status: activeem1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>ether 00:22:<snip>inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255inet6 2600:8804:<snip>:4070 prefixlen 64inet6 2600:8804:<snip>:4070 prefixlen 64inet6 2600:8804:<snip>:4070 prefixlen 64inet6 fe80::1:1%em1 prefixlen 64 scopeid 0x2nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>media: Ethernet autoselect (1000baseT <full-duplex>)status: active
And my laptop is getting some IPv6 addresses.
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500ether 5c:<snip>inet6 fe80::<snip>:31d7%en1 prefixlen 64 scopeid 0x4inet 192.168.1.165 netmask 0xffffff00 broadcast 192.168.1.255inet6 2600:8804:<snip>:31d7 prefixlen 64 detached autoconfinet6 2600:8804:<snip>:8cd1 prefixlen 64 detached autoconf temporaryinet6 2600:8804:<snip>:31d7 prefixlen 64 autoconfinet6 2600:8804:<snip>:fc5d prefixlen 64 autoconf temporarynd6 options=1<PERFORMNUD>media: autoselectstatus: active
From the pfSense box, I can traceroute6 google.
[2.3-RELEASE][admin@pfsense]/root: traceroute6 google.comtraceroute6 to google.com (2607:f8b0:4000:800::200e) from 2600:8804:<snip>:9715, 64 hops max, 12 byte packets 1 2600:8804:9f03:200::1 8.968 ms 8.521 ms 7.964 ms 2 2001:578:1000:4::34c 8.793 ms 9.428 ms 7.768 ms 3 2001:578:1000:4::86 17.946 ms 19.252 ms 17.948 ms 4 2001:578:1:0:172:17:248:182 29.209 ms 28.635 ms 29.990 ms 5 2001:4860:1:1:0:58f5:0:25 30.157 ms 30.069 ms 30.436 ms 6 2001:4860::1:0:c04d 29.315 ms 29.322 ms 30.386 ms 7 2001:4860:0:1::15d3 30.562 ms 32.622 ms 29.797 ms 8 dfw25s07-in-x0e.1e100.net 30.375 ms 29.357 ms 30.635 ms
But if I try from my laptop, it seems to die after the first hop from my pfSense machine.
➜ ~ traceroute6 google.comtraceroute6 to google.com (2607:f8b0:4000:800::200e) from 2600:8804:<snip>:fc5d, 64 hops max, 12 byte packets 1 pfsense 1.110 ms 0.875 ms 0.924 ms 2 2600:8804:9f03:200::1 62.937 ms 8.670 ms 9.885 ms 3 * * *
If I do a traceroute using HE's Looking Glass (using the Equinix Dallas router), I get this on the WAN IP:
1 11 ms 26 ms 44 ms asn-cxa-all-cci-22773-rdc-as22773.10gigabitethernet6-9.core1.dal1.he.net (2001:470:0:391::2)2 31 ms 78 ms 14 ms 2001:578:1:0:172:17:248:1653 98 ms 147 ms 125 ms 2001:578:1000:4::874 87 ms 27 ms 45 ms 2001:578:1000:4::34d5 70 ms 83 ms 37 ms 2600:8804:<snip>:9715
But the pfSense LAN IP gets this:
1 5 ms 1 ms 14 ms asn-cxa-all-cci-22773-rdc-as22773.10gigabitethernet6-9.core1.dal1.he.net (2001:470:0:391::2)2 24 ms 35 ms 15 ms 2001:578:1:0:172:17:248:1643 32 ms 25 ms 28 ms 2001:578:1000:4::734 22 ms 22 ms 23 ms 2001:578:1000:4::875 24 ms 25 ms 25 ms 2001:578:1000:4::3516 * * * ?7 * * * ?8 * * * ?9 * * * ?IP: Errno(8) Trace Route Failed, no response from target node.
I used a different router in Kansas City, as well, and they both ended on the same IP's, :73, :87, then :351
I have a feeling that the PD isn't getting routed back to me, but I'm not sure where to go from here. I've seen a few other threads on here where people have been able to get some help from Cox employees. I hope I have provided plenty of detail, but if I need to include some other piece of information, please let me know.
↧