What, if anything, appears in the log every hour at the time the Internet breaks?
If the ISP changes your address on you, Internet will definitely stop working while all the client connections have to re-establish through the new address.
1 Like
I have verified that my public IP has remained the same before and after. Also, the issue doesn't occur running stock firmware vs openwrt.
Here are my logs prior to it happening:
ue Feb 7 18:08:19 2023 daemon.info hostapd: wlan0: STA a4:50:46:5c:48:11 IEEE 802.11: authenticated
Tue Feb 7 18:08:19 2023 daemon.info hostapd: wlan0: STA a4:50:46:5c:48:11 IEEE 802.11: associated (aid 3)
Tue Feb 7 18:08:19 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED a4:50:46:5c:48:11
Tue Feb 7 18:08:19 2023 daemon.info hostapd: wlan0: STA a4:50:46:5c:48:11 WPA: pairwise key handshake completed (RSN)
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPDISCOVER(br-lan) a4:50:46:5c:48:11
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPOFFER(br-lan) 192.168.1.131 a4:50:46:5c:48:11
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPDISCOVER(br-lan) a4:50:46:5c:48:11
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPOFFER(br-lan) 192.168.1.131 a4:50:46:5c:48:11
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPREQUEST(br-lan) 192.168.1.131 a4:50:46:5c:48:11
Tue Feb 7 18:08:23 2023 daemon.info dnsmasq-dhcp[2694]: DHCPACK(br-lan) 192.168.1.131 a4:50:46:5c:48:11
Tue Feb 7 18:10:50 2023 daemon.warn dnsmasq[2694]: possible DNS-rebind attack detected: 192-168-1-227.abcdefghijklmnopqrstuvwxyz012345.plex.direct
It happened around 18:12, also happens when plex is off, just happened to have it on this time.
Happened again. This time at 19:34
Below are logs:
Tue Feb 7 18:59:39 2023 authpriv.info dropbear[2817]: Exit (root) from <192.168.1.227:62878>: Exited normally
Tue Feb 7 19:23:21 2023 kern.info kernel: [ 4975.099345] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is down
Tue Feb 7 19:23:24 2023 kern.info kernel: [ 4978.170662] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is up
Tue Feb 7 19:24:21 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 IEEE 802.11: authenticated
Tue Feb 7 19:24:21 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 IEEE 802.11: associated (aid 5)
Tue Feb 7 19:24:21 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d6:c6:67:b4:b2:07
Tue Feb 7 19:24:21 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 WPA: pairwise key handshake completed (RSN)
Tue Feb 7 19:24:25 2023 daemon.info dnsmasq-dhcp[2694]: DHCPDISCOVER(br-lan) d6:c6:67:b4:b2:07
Tue Feb 7 19:24:25 2023 daemon.info dnsmasq-dhcp[2694]: DHCPOFFER(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:24:25 2023 daemon.info dnsmasq-dhcp[2694]: DHCPDISCOVER(br-lan) d6:c6:67:b4:b2:07
Tue Feb 7 19:24:25 2023 daemon.info dnsmasq-dhcp[2694]: DHCPOFFER(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:24:26 2023 daemon.info dnsmasq-dhcp[2694]: DHCPREQUEST(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:24:26 2023 daemon.info dnsmasq-dhcp[2694]: DHCPACK(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:34:31 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d6:c6:67:b4:b2:07
Tue Feb 7 19:34:31 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 IEEE 802.11: disassociated
Tue Feb 7 19:34:31 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 IEEE 802.11: authenticated
Tue Feb 7 19:34:31 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 IEEE 802.11: associated (aid 5)
Tue Feb 7 19:34:31 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d6:c6:67:b4:b2:07
Tue Feb 7 19:34:31 2023 daemon.info hostapd: wlan0: STA d6:c6:67:b4:b2:07 WPA: pairwise key handshake completed (RSN)
Tue Feb 7 19:34:32 2023 daemon.info dnsmasq-dhcp[2694]: DHCPREQUEST(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:34:32 2023 daemon.info dnsmasq-dhcp[2694]: DHCPACK(br-lan) 192.168.1.142 d6:c6:67:b4:b2:07
Tue Feb 7 19:34:33 2023 user.info : luci: accepted login on / for root from 192.168.1.142
It appears when I’m using a wireless device and it happens, the logs are more insightful as they actually show the disconnect, though I’m not sure what to draw from it.
Again at 21:12, doesn’t seem to be anything out of the ordinary, will stop posting new logs now.
Tue Feb 7 20:31:15 2023 kern.info kernel: [ 9049.555012] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is down
Tue Feb 7 20:31:16 2023 kern.info kernel: [ 9050.578765] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is up
Tue Feb 7 20:31:47 2023 kern.info kernel: [ 9081.298463] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is down
Tue Feb 7 20:31:50 2023 daemon.info dnsmasq-dhcp[2694]: DHCPDISCOVER(br-lan) 38:d5:47:df:3d:ff
Tue Feb 7 20:31:50 2023 daemon.info dnsmasq-dhcp[2694]: DHCPOFFER(br-lan) 192.168.1.227 38:d5:47:df:3d:ff
Tue Feb 7 20:31:50 2023 daemon.info dnsmasq-dhcp[2694]: DHCPREQUEST(br-lan) 192.168.1.227 38:d5:47:df:3d:ff
Tue Feb 7 20:31:50 2023 daemon.info dnsmasq-dhcp[2694]: DHCPACK(br-lan) 192.168.1.227 38:d5:47:df:3d:ff WIN-MV0CJP9SMLR
Tue Feb 7 20:31:50 2023 kern.info kernel: [ 9084.370095] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is up
Tue Feb 7 20:31:51 2023 daemon.info dnsmasq[2694]: read /etc/hosts - 4 addresses
Tue Feb 7 20:31:51 2023 daemon.info dnsmasq[2694]: read /tmp/hosts/odhcpd - 2 addresses
Tue Feb 7 20:31:51 2023 daemon.info dnsmasq[2694]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Tue Feb 7 20:31:51 2023 daemon.info dnsmasq-dhcp[2694]: read /etc/ethers - 0 addresses
Tue Feb 7 20:33:34 2023 kern.info kernel: [ 9187.792630] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is down
Tue Feb 7 20:33:37 2023 kern.info kernel: [ 9190.864266] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is up
Tue Feb 7 20:33:56 2023 kern.info kernel: [ 9210.320197] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is down
Tue Feb 7 20:33:59 2023 kern.info kernel: [ 9213.391823] Atheros AR8216/AR8236/AR8316 mdio.0:00: Port 2 is up
Tue Feb 7 20:34:13 2023 daemon.info dnsmasq-dhcp[2694]: DHCPREQUEST(br-lan) 192.168.1.227 38:d5:47:df:3d:ff
Tue Feb 7 20:34:13 2023 daemon.info dnsmasq-dhcp[2694]: DHCPACK(br-lan) 192.168.1.227 38:d5:47:df:3d:ff WIN-MV0CJP9SMLR
Tue Feb 7 21:12:58 2023 user.info : luci: accepted login on / for root from 192.168.1.142
So there are two things happening: ethernet port 2 goes up and down and also a wifi device disconnects and immediately reconnects.
If port 2 is connected to a laptop or desktop and the disconnect corresponds to the OS going into standby, that is normal.
1 Like
Yes the port 2 was my pc rebooting. The Wi-Fi disconnect was me losing internet, I guess it only shows in logs when I’m actively using that device.