Anyone know why opening #IPv6 ports on #GoogleWifi might be failing for me? I have IPv6 service from my ISP (sonic.net - they're awesome!) and have a web server set up on my #RaspberryPi.

Requests from outside my network sent to the pi's IPv6 GUA keep failing, even though I have ports 80 and 443 open for the pi in the "Port Management" section of the google home app. Requests made to that same IPv6 GUA work fine within my network.

(I also have IPv4 port forwarding set up on that same page, and that seems to work fine to forward requests made to my router's external IPv4 address to the pi, so I could simply not set up an AAAA record and move forward with only IPv4 access to my server, but I'd prefer having a working dual-stack setup!)

#networking #HomeLab #IPv6 #Google #techsupport #DualStack

Gah. Wasted a day sorting out a #GoogleWifi network issue; as part of a cleanup process, I restricted the DHCP server from issuing IPs in a certain range. A bit later on I found that some devices were being assigned non-routable IPs and I couldn't add satellite pucks.

These were not unrelated events but it took hours to diagnose the relationship. Yeah, wifi's DHCP was *still* trying to assign IPs from the forbidden range, even when told not to, but failed (quietly) when doing so. What a maroon.

#openwrt merged initial support for #google #onhub into master branch!! https://github.com/openwrt/openwrt/commit/ef649b0b14814a84a480e9b7805e4a401e9e06b6

forum thread: https://forum.openwrt.org/t/onhub-tp-link-tgr1900-future-support/17899/140

#googlewifi #tplink #asus #googleonhub