02-22-2023, 05:23 AM
(02-22-2023, 05:00 AM)chanthing Wrote: Thanks very much for the troubleshooting info. I tried running with a static IP and that seemed to help. However, what ends up seeming to happen is that for some reason, the wireless connection loses its IPV4 information. After I started seeing the NetworkUnreachable error, I did an ifconfig and here's what I see for my wireless connection
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::df87:b801:a8:5a69 prefixlen 64 scopeid 0x20<link>
ether e4:5f:01:e6:07:48 txqueuelen 1000 (Ethernet)
RX packets 97485 bytes 99865071 (95.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 37143 bytes 11967105 (11.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
For some reason, wlan0 is no longer has an inet entry associated with its address.
daemon.log has these interesting entries:
Feb 21 22:59:12 savagemusic winbindd[559]: [2023/02/21 22:59:12.343316, 0] ../../source3/rpc_server/rpc_ncacn_np.c:454(rpcint_dispatch)
Feb 21 22:59:12 savagemusic winbindd[559]: rpcint_dispatch: DCE/RPC fault in call lsarpc:32 - DCERPC_NCA_S_OP_RNG_ERROR
Feb 21 22:59:44 savagemusic dhcpcd[892]: wlan0: hardware address 00:00:00:00:00:00 claims 192.168.1.85
Feb 21 22:59:46 savagemusic dhcpcd[892]: wlan0: hardware address 00:00:00:00:00:00 claims 192.168.1.85
Feb 21 22:59:46 savagemusic dhcpcd[892]: wlan0: 10 second defence failed for 192.168.1.85
Feb 21 22:59:46 savagemusic avahi-daemon[405]: Withdrawing address record for 192.168.1.85 on wlan0.
Feb 21 22:59:46 savagemusic avahi-daemon[405]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.85.
Feb 21 22:59:46 savagemusic avahi-daemon[405]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 21 22:59:46 savagemusic dhcpcd[892]: wlan0: deleting route to 192.168.1.0/24
Feb 21 22:59:46 savagemusic dhcpcd[892]: wlan0: deleting default route via 192.168.1.1
FWIW, the RPC error happens a bunch before this sequence removing the address record and the and the route are removed. I included it for completeness, but I don't think it's related.
Any insights on what might be causing this are welcome. If I haven't exited my ssh connection, I can restart dhcpcd and everything is cool, but why is it bailing?
[Obviously this affects more than just librespot]
FWIW, my router's dhcp is configured to only hand out addresses higher than 192.168.1.100. But I have some cheap LED bulbs that connect via wireless. Could they be trying to grab that IP?
