Vilo: Difference between revisions
Brian Wilson (talk | contribs) |
Brian Wilson (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
It does 802.11AX to allow a GB connection for [[Pearl]]. | It does 802.11AX to allow a GB connection for [[Pearl]]. | ||
== History == | |||
2023-09-09 Replaced the UniFi WAP. Purchased from Streakwave 9/1 for $65 | |||
== Setup notes == | == Setup notes == | ||
| Line 22: | Line 25: | ||
If I have to use another Windows machine on WiFi here I will deal with it. | If I have to use another Windows machine on WiFi here I will deal with it. | ||
[[Category:Network]] | [[Category:Network]] | ||
Revision as of 02:46, 10 September 2023
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.
History
2023-09-09 Replaced the UniFi WAP. Purchased from Streakwave 9/1 for $65
Setup notes
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.
IPV6 DNS glitch
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 with is to disable DNS over IPV6 by doing this
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 255 /f
If I have to use another Windows machine on WiFi here I will deal with it.
