Vilo

Here we go, trying to adapt to a new access point, a Vilo 6. It does 802.11AX to allow a GB connection for Pearl. That and getting rid of the UniFi controller software. Instead I have to use a management app on a smartphone. Not crazy over that but I can live with it.

I can't see any actual support for VLAN tagging on this thing.

History

2023/10/05 It's been installed and working flawlessly for a month now.

2023/09/09 Replaced the UniFi WAP. Purchased from Streakwave 9/1/23 for $65

Setup notes

Set up was a bit sketchy, but it's not as I feared, "cloud managed". So I can work with it.

It's in BRIDGE mode.

Also I did the thing that splits it into two SSID's "wildsong" is 5 GHz and "wildsong2" is 2.4. This is specifically to support our Tuya-based switches and dimmers, they are unhappy on combined networks according to their docs.

Android 10

The Lenovo Tab and probably all the other Android devices prefer the IPv6 DNS that's built in. I have to block IPv6 at the router to stop this. It makes my internal network unreachable, so Home Assistant doesn't work. Google probably does this to stop Pi Hole from working.

Linux Mint

Murre runs Mint now so forget the comments about Windows 10 below. When installing some software

I noticed Murre would try going to ipv6 addresses first and then grind away for some time before failing back to ipv4. To disable ipv6, try this. https://linuxconfig.org/how-to-disable-ipv6-on-ubuntu-24-04

Now when I do an "ip addr" and see no inet6 entries, so I know it worked.

Windows 11

Pearl was getting an IPv6 DNS server setting from the Vilo 6.

That meant Pearl was no longer paying attention to PiHole since it preferred the Vilo. Access to the Internet was fine but it did not resolve my local IP addresses.

The fix I came up for Windows 11 with is to disable DNS over IPV6 by doing this to favor IPv4 over IPv6. It is not recommended to use value 255 because that disables IPv6 entirely.

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 32 /f

Windows 10 is different. It turns out the Vilo is doing DHCP on the ethernet too! (It is in bridge mode after all.) It appears the registry fix is for W 11 only, so it won't work on Murre. I bet this one works on either. Not ideal darn darn. Breaks nslookup. Darn. https://superuser.com/questions/1450259/windows-10-disable-auto-configuring-dns-servers-via-ipv6-connection

Control Panel -> Network and Internet -> Network Connections -> Ethernet Properties -> Internet Protocol Version 6 -> "Use the following DNS Server addresses" set preferred to ::1 This works instantly, no need to log out or reboot. This works by breaking the IPv6 DNS server setting so that it fails to IPv4 always and requires no special registry hack.