Double checked with the following loads without any problems....Oh, sorry. No, 44D9 pass2
Next update, 44EA, posted. This release addresses fixes for user reported issues, some component updates, and one new feature.
Newly added is support for UPNP to obtain the external WAN address via STUN. This may help in some CGNAT environments.
Also of note is updated timezone support, including updated regions and the default DST/TDT start/stop times for each region. Please check your timezone settings after the update, as it may have changed based on the new timezone data.
Please review the first post for the other updates/fixes.
Enjoy!
SHA256
Code:(Default Build - All supported routers) 622fceac1124060146b7e024747132eb26a3b8a77106a94f8734d78bf18f50af RT-N16_374.43_44EAj9527.trx 2812787eead4ada7ba8abd75c5c48bdb412eb8833cd6af0d977eb5461c3c12df RT-AC66U_374.43_44EAj9527.trx 8e363513f3a064d50339379093145358894effff311c38a311acb6b6e01a343b RT-N66U_374.43_44EAj9527.trx cfd4b929095a28d6eb26752af153ba8a6fdfc916b3448b6d9e8d80ce6973cd85 RT-AC68U_374.43_44EAj9527.trx 9bfddde75c53bac4b2909c904a1ed0ffd74f53d58abd99e7240f3fc311531d55 RT-AC56U_374.43_44EAj9527.trx
I know I've had Comcast customers using my fork so it should work. Maybe one of them could jump in if they had to do something special.Since I'm a comcast customer, I'm pretty sure I should be seeing a LAN IPv6 address start with 2601: if I remember correctly. I'm not sure why I'm not... does this mean prefix delegation isn't working?
Glad to hear it! (sorry it took longer than I expected to get it released...got caught in a little bit of 'scope creep' )Thanks! It's working now....................
I went back through my posts and the only anomaly I ever encountered with IPv6 on Comcast on the fork was an issue testing a dev build and ending up with multiple udhcpc processes. It wasn’t permanent. Other than that, I don’t recall any other issues when I was running the fork. This was after the radvd updates.I know I've had Comcast customers using my fork so it should work. Maybe one of them could jump in if they had to do something special.
I know I've had Comcast customers using my fork so it should work. Maybe one of them could jump in if they had to do something special.
I don't see anything wrong with your setup, so in the meantime....
The firmware change may somehow may be causing Comcast to see this as a new device. So first thing to try is powering down your modem for about 15-30min to get it to reset the connection at the head end.
Second, some ISPs are very slow to release IPv6 addresses with a change in config if it hadn't been released properly. So, next thing is just to try again in 8-24 hours (yes, it can take that long).
Lastly, would be to upload your full syslog following a reboot to a file sharing site for me to review (PM the link if you are concerned about privacy).
I went back through my posts and the only anomaly I ever encountered with IPv6 on Comcast on the fork was an issue testing a dev build and ending up with multiple udhcpc processes. It wasn’t permanent. Other than that, I don’t recall any other issues when I was running the fork. This was after the radvd updates.
Yes....the IPV6 prefix should be 4 hextets, and the LAN IPv6 address should be that prefix with the EUI64 address of the router (address based on the router MAC)Am I correct that I should see the "LAN IPv6 Address" and "LAN IPv6 Prefix" filled in on the UI when things are working correctly?
I know I've had Comcast customers using my fork so it should work. Maybe one of them could jump in if they had to do something special.
Hmmm....the last change to ipv6 was the radvd update back in April....and @dave14305 tested after that change. I wonder if Comcast changed something on their end recently? Cox ipv6 is still working fine for me.@luni @john9527
Out of curiosity I decided to flip on ipv6 to see what would happen and it indeed does not work now. I don't have time to toy with it at the moment because of covid stuff and working from home, can't have any extended downtime. But I thought I'd throw that information out for the time being since what I just said a bit earlier is no longer the case. I'll look into it more when the weekend comes and I can tinker.
Hmmm....the last change to ipv6 was the radvd update back in April....and @dave14305 tested after that change. I wonder if Comcast changed something on their end recently? Cox ipv6 is still working fine for me.
One quick thing to try is to set the 'Prefix delegation requires address request' option to Yes (last option on the ipv6 page)
Well it has been quite a while since I last used it successfully, many many builds ago. I know it’s sorta crappy to say oh hey this doesn’t work and give no details, so sorry about that on my end. For what it’s worth Comcast’s implementation of ipv6 even when it worked was pretty wonky and is part of why I stopped using it. But I’ll try your recommendations over the weekend.Hmmm....the last change to ipv6 was the radvd update back in April....and @dave14305 tested after that change. I wonder if Comcast changed something on their end recently? Cox ipv6 is still working fine for me.
One quick thing to try is to set the 'Prefix delegation requires address request' option to Yes (last option on the ipv6 page)
https://www.tenforums.com/tutorials/145372-how-enable-disable-dns-over-https-doh-google-chrome.htmlHey Guys, anyone found a way to effectively forward DoH to another provider. ?
Prevent Client auto DoH was meant for Firefox browsers. Chrome takes a different approach of upgrading to DoH if it detects the OS DNS is using a DNS provider that also offers DoH. If you point the PC DNS to the router, does it still use DoH? I don’t use Chrome, so I can’t test this.Hey Guys, anyone found a way to effectively forward DoH to another provider. ?
I have PiHole installed and to do some testing, I changed my PC DNS to be 9.9.9.9 then in my router (RT-N66U) changed the setting "Prevent Client auto DoH" to YES
Parental Control --> DNS Filtering , enabled it, and fwd all traffic to to my PiHole
To test it, I blocked Instagram in Pihole , in PC command line, pinged insta, no result, disabled my Pihole, ping again, got result, so I know its working, However, in Chrome, I can visit Instagram and all the ads show, which shows Chrome has found a way to bypass Pihole and is using PC DNS directly. Looks like Chrome is using DoH, is there anyway I can fix this? I am trying to block ALL devices on my network to use Pihole.
Thanks,
Thanks, however I am looking to see if possible to do this at the router level as oppose to disabling it on Chrome. the main reason is, I am trying to prevent ANY device (some that I might not know) to use any DNS other than my PiHole.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!