My kubernetes cluster is k3s1, k3s2, k3w1, k3w2, etc. My load balancer is called… lb.home.lan. I guess that we are not as creative.

I redirect to IIS.net just to be annoying.

.home.lan for me.

Thank you!! Yes, it is a DHCP war. I just realized that I can talk to my hardwired devices but only by IP! Even though I specify my DNS server in google, its ignoring it for the browser. I wonder if that is DNS over HTTPS (DOH) in Chrome.

Yea, complete shit: https://www.googlenestcommunity.com/t5/Nest-Wifi/Changing-the-Domain-Name-Domain-Suffix/td-p/183313

In opnsense they divide up the rule categories into Floating, LAN, Loopback, WAN. In LAN i have rule which is allow any to any, so as I understand it all devices on the LAN can talk to each other. Thanks for the reply.

It is a complete shit device, I had to buy smart switches to automatically reboot them every night one by one so they don’t randomly drop from the ‘mesh’ the next day. And they were expensive and I have 5 nodes which is why I am hoping to keep using the damn things. I hate them though.

As I understand it, the effect that you are suggesting is to move the Google Wifi IP Ranges to be the same as the wired, all 192.168.1.0.

I will think on that. Thanks

This turned out to be the solution that I chose. My internet provider did not support DHCP and even DNS was hard coded which made it hard for me. So, i switched the modem into Bridge mode and installed opnsense on a computer that I had after installing a 2x1GB NIC for it. Now I have full control over naming and now everything mostly works as I need it to.

Thanks for this, i am also now using Heimdall! Its great.

I use NPM which is also a docker image and has automatic let’s encrypt and a nice interface. Nginx Proxy Manager.