Joined: 08 May 2018 Posts: 14247 Location: Texas, USA
Posted: Mon Dec 06, 2021 23:10 Post subject:
Every guide I have seen for all other firmware / router OSes on Comcast says to use native ISP and leave prefix at 64. There is also the possibility of these settings being conflicting:
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Tue Dec 07, 2021 3:41 Post subject:
[quote="Wildlion"]
PaulGo wrote:
Wildlion,
You might need to do this commands under the command line... and they should have been done one at a time... since the web-interpreter will think it is one command and not two ... so it probably errored out.
I did as you suggested and this is the result:
PING ff02::1%eth0 (ff02::1%4): 56 data bytes
64 bytes from fe80::861b:5eff:fe4e:bf4c: seq=0 ttl=64 time=0.490 ms
64 bytes from fe80::861b:5eff:fe4e:bf4c: seq=1 ttl=64 time=0.446 ms
64 bytes from fe80::861b:5eff:fe4e:bf4c: seq=2 ttl=64 time=0.456 ms
64 bytes from fe80::861b:5eff:fe4e:bf4c: seq=3 ttl=64 time=0.456 ms
64 bytes from fe80::861b:5eff:fe4e:bf4c: seq=4 ttl=64 time=0.460 ms
--- ff02::1%eth0 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.446/0.461/0.490 ms
PING ff02::1%br0 (ff02::1%11): 56 data bytes
64 bytes from fe80::861b:5eff:fe4e:bf4e: seq=0 ttl=64 time=0.490 ms
64 bytes from fe80::861b:5eff:fe4e:bf4e: seq=1 ttl=64 time=0.465 ms
64 bytes from fe80::861b:5eff:fe4e:bf4e: seq=2 ttl=64 time=0.464 ms
64 bytes from fe80::861b:5eff:fe4e:bf4e: seq=3 ttl=64 time=0.470 ms
64 bytes from fe80::861b:5eff:fe4e:bf4e: seq=4 ttl=64 time=0.468 ms
--- ff02::1%br0 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.464/0.471/0.490 ms
Last edited by PaulGo on Tue Dec 07, 2021 14:12; edited 2 times in total
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Tue Dec 07, 2021 4:23 Post subject:
kernel-panic69 wrote:
Every guide I have seen for all other firmware / router OSes on Comcast says to use native ISP and leave prefix at 64. There is also the possibility of these settings being conflicting:
Dynamic Routing from (WLAN) to (LAN & WLAN)
Used domain from (WLAN) to - (LAN & WLAN)
I did as you requested and WAN IPv6 is still disabled.
I tried it with Native ISP and DHCPv6 with Prefix Delegation both did not work (each with a reboot).
There has to be something that we are missing... but at least we know based on the link local responses that you are connected, so something is hooked up.
Out of stupidity when your windows 10 machine is connected... can you do a similar ping (ie if you are familiar with what you are doing) and see what responds (or even post your routing tables)
Then post the routing tables from the router for ipv6
so what I was looking for is to see if the routing is "similar" with the router connected to the modem vs when the the windows 10 machine is directly connected to the modem...
There is one that is in common:
fe80::861b:5eff:fe4e:bf4e
which means that from the ping on the router was answered by the windows machine...
So what I was hopeing to do is on the windows machine see what the ipv6 link local connection is to the modem or upstream device.... Then on the router see if it would acknowledge the same device and be able to ping it (plus check firewall rules)
Depending on how proficent you are with networking, we could start using wireshark to record packets and see the solicitations....
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Sat Dec 25, 2021 17:41 Post subject:
Comcast increased the lease time from two hour to four days (still using vCMTS). However dd-wrt still does not detect IPv6 from the WAN. I am using an Arris SB8200 modem which when rebooted states "Honoring MDD; IP provisioning mode = IPv6" in the event log.
I have spent some time thinking about this since your last post and I have a feeling it is a setting that we do not understand or we are talking past each other (not understanding a nuance that the other is saying)
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Sun Dec 26, 2021 13:59 Post subject:
[quote="Wildlion"]I have spent some time thinking about this since your last post and I have a feeling it is a setting that we do not understand or we are talking past each other (not understanding a nuance that the other is saying)[/quote]
It there anything else that I could try? vCMTS system is different then standard CMTS. If I go back to the Netgear firmware now that Comcast went to a four day lease IPv6 will be recognized and connected, but with the dd-wrt firmware I cannot get it to recognize IPv6. Using the Netgear firmware is not an option since Netgear has dropped support several years ago and it has too many security vulnerabilities.
Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sun Dec 26, 2021 21:39 Post subject:
Is your modem in modem node or is it acting as a router?
With Comcast, try with a /56 prefix.
There a two types of dhcp servers in IPv6, one for clients that handle out single addresses and a wide server that hands out delegated prefixes for routers. Most ISP routers does not have the latter.
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Mon Dec 27, 2021 1:22 Post subject:
The Arris SB8200 is a pure DOCSIS 3.1 modem. I purchase the modem about three years ago. It is on the Comcast approved list and Comcast is responsible for updating the firmware. They have updated the firmware several time since I purchased the modem. I will try the /56 prefix later this evening.
