Forum Discussion

JaredF's avatar
JaredF
New Contributor
Solved

Not Getting a Response from Cox's IPv6 DHCP Server...

I am sending IPv6 DHCP Solicits out through my WAN interface, but I am not getting any response from Cox's servers...  IPv6 had been working for several months previously; I just noticed this behavior about a week ago.

This is the solicit message I'm sending out (slightly redacted):

01:39:04.858176 IP6 (flowlabel 0x070ba, hlim 1, next-header UDP (17) payload length: 58) fe80::cee1:ffff:ffff:ffff.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=71e4b9 (client-ID hwaddr type 1 cce1ffffffff) (rapid-commit) (elapsed-time 65535) (option-request DNS-server) (IA_PD IAID:0 T1:0 T2:0))

But I never see any response.  I am located in San Diego.

Anyone else seeing this?

DHCP
dhcp6
dhcp6c
dhcp6s
dhcpv6
iPv6
san diego
  • JaredF's avatar
    JaredF

    Hi Chris,

    Thanks for the reply!  Sometime over the weekend (after Feb. 16), it suddenly started working again.  I'm assuming that it was fixed on Cox's end because I made no changes on my side and was in fact out of town when it came back up.

    The response I am seeing now is:

    14:43:24.761673 IP6 (flowlabel 0x56aee, hlim 1, next-header UDP (17) payload length: 58) fe80::cee1:ffff:ffff:ffff.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=74b6ba (client-ID hwaddr type 1 cce1ffffffff) (rapid-commit) (elapsed-time 0) (option-request DNS-server) (IA_PD IAID:0 T1:0 T2:0))


    14:43:24.775078 IP6 (class 0xe0, hlim 255, next-header UDP (17) payload length: 193) fe80::224:14ff:ffff:ffff.547 > fe80::cee1:ffff:ffff:ffff.546: [udp sum ok] dhcp6 reply (xid=74b6ba (client-ID hwaddr type 1 cce1ffffffff) (server-ID hwaddr/time type 1 time 1486550587 c81f66ffffff) (rapid-commit) (DNS-server cdns1.cox.net cdns6.cox.net cdns1.cox.net cdns6.cox.net cdns1.cox.net cdns6.cox.net) (IA_PD IAID:0 T1:43200 T2:69120 (IA_PD-prefix 2600:8801:ffff:ff::/64 pltime:86400 vltime:86400)))

2 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @JaredF

    From this end the router appears to have a valid IPv6 address. I'd start by trying to connect a PC directly to the modem and see if that works. If so, that could suggest there is something in the Buffalo settings holding you back.

  • JaredF's avatar
    JaredF
    New Contributor

    Hi Chris,

    Thanks for the reply!  Sometime over the weekend (after Feb. 16), it suddenly started working again.  I'm assuming that it was fixed on Cox's end because I made no changes on my side and was in fact out of town when it came back up.

    The response I am seeing now is:

    14:43:24.761673 IP6 (flowlabel 0x56aee, hlim 1, next-header UDP (17) payload length: 58) fe80::cee1:ffff:ffff:ffff.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=74b6ba (client-ID hwaddr type 1 cce1ffffffff) (rapid-commit) (elapsed-time 0) (option-request DNS-server) (IA_PD IAID:0 T1:0 T2:0))


    14:43:24.775078 IP6 (class 0xe0, hlim 255, next-header UDP (17) payload length: 193) fe80::224:14ff:ffff:ffff.547 > fe80::cee1:ffff:ffff:ffff.546: [udp sum ok] dhcp6 reply (xid=74b6ba (client-ID hwaddr type 1 cce1ffffffff) (server-ID hwaddr/time type 1 time 1486550587 c81f66ffffff) (rapid-commit) (DNS-server cdns1.cox.net cdns6.cox.net cdns1.cox.net cdns6.cox.net cdns1.cox.net cdns6.cox.net) (IA_PD IAID:0 T1:43200 T2:69120 (IA_PD-prefix 2600:8801:ffff:ff::/64 pltime:86400 vltime:86400)))