My Nintendo switch will not connect to the internet, I see it connect to the router, then it fails. I am seeing below in the logs. Apparently my NTP cannot resolve as the logs indicate today is December 31st, 1.pool.ntp.org is what I was using.
I have made no changes at all, so I am not sure why all of a sudden I am getting an error about bad DHCP host name.
I am using wireguard and ProtonVPN.
Code:
Dec 31 18:27:38 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 IEEE 802.11: disassociated
Dec 31 18:27:39 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 MLME: auth request, signal -67 (Accepted)
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 IEEE 802.11: authenticated
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 MLME: assoc request, signal -69 (Accepted)
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 IEEE 802.11: associated (aid 1)
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 RADIUS: starting accounting session DB199014DE2C404B
Dec 31 18:27:43 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 WPA: pairwise key handshake completed (RSN)
Dec 31 18:27:44 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 IEEE 802.11: disassociated
Dec 31 18:27:45 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 MLME: auth request, signal -74 (Accepted)
Dec 31 18:27:45 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 IEEE 802.11: authenticated
Dec 31 18:27:45 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 MLME: assoc request, signal -74 (Accepted)
Dec 31 18:27:45 TekRouter daemon.info hostapd: wlan1: STA 98:b6:e9:01:3d:17 IEEE 802.11: associated (aid 3)
Dec 31 18:27:45 TekRouter daemon.info hostapd: wlan0: STA 98:b6:e9:01:3d:17 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 31 18:28:00 TekRouter user.info : [dnsmasq] : maybe died, we need to re-exec it
Dec 31 18:28:00 TekRouter daemon.crit dnsmasq[8889]: bad DHCP host name at line 15 of /tmp/dnsmasq.conf
Dec 31 18:28:00 TekRouter daemon.crit dnsmasq[8889]: FAILED to start up
Dec 31 18:28:00 TekRouter user.info : [dnsmasq] : daemon successfully started
Most of those highlighted messages seem to be either from attempts to connect from the internet into the WAN (eth0) or WG VPN (oet2), which should normally be blocked by default. So I don't see any of that as relevant to your present problems.
The DNSMasq error might be due to the use of invalid chars in the hostname. Let's see by dumping the file.
The Nintendo switch doesn't have a hostname for whatever reason, the * was blocking all wireless traffic I am assuming, I removed that just now, and my wireless network came back up. All my wired devices were working fine.
While I understand what having a wildcard in that entry was doing, what I don't understand is, why did it break wireless for the other devices, but not wired? It also doesn't explain why the switch wouldn't connect earlier, but I don't want to waste time trying to figure out why that started.
I caused the rest of the network to fail in an attempt to fix the one device.
And bizarrely, after enabling telnet to run that command, I started having multiple ip4/ip6 addresses attempting to get into my router.
Actually, I don't understand the purpose of the '*' in the dhcp-host record. I assume it was meant to prevent the DHCP server from using any client-id provided by the client, but the correct syntax is a follows.
If that was something YOU add manually in the Additional DNSMasq Options field of the Services page, then fine, it's just user error. But I'd be concerned if the router itself, in managing hostnames, made that same error.
The asterisk in the display (afaik) is simply when the GUI doesn't know the hostname, for whatever reason. But that shouldn't correspond to an actual asterisk as a hostname! Having an asterisk as a standalone option in the dhcp-host record makes no sense. It doesn't mean anything, and so DNSMasq complains.