Its been up for 2d 12h now after I removed the metal cover (to isolate the probability of overheating) and rebooted, will try older build once i get disconnection again.
while still monitoring the current running system, one thing caught my attention upon check system.log: Is it normal for dnsmasq not logging anymore after sometime?
Fri Feb 24 10:59:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Fri Feb 24 11:00:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Fri Feb 24 11:00:08 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Fri Feb 24 11:01:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Fri Feb 24 11:01:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Fri Feb 24 11:02:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Fri Feb 24 11:02:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Fri Feb 24 11:02:53 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Fri Feb 24 11:02:53 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Fri Feb 24 11:03:28 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Fri Feb 24 11:03:28 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 10 names
Fri Feb 24 11:03:28 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Fri Feb 24 11:03:28 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Feb 24 11:03:28 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Feb 24 11:03:29 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Feb 24 11:03:29 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Fri Feb 24 11:44:25 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 11:44:25 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 11:44:25 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 12:49:17 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 12:49:17 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: associated (aid 2)
Fri Feb 24 12:49:17 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 04:68:65:8b:ee:f8 auth_alg=ft
Fri Feb 24 13:25:50 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 13:25:50 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 13:25:51 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 13:46:41 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 04:68:65:8b:ee:f8
Fri Feb 24 13:46:41 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 13:46:41 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: associated (aid 2)
Fri Feb 24 13:46:41 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 04:68:65:8b:ee:f8 auth_alg=ft
Fri Feb 24 13:47:16 2023 kern.info kernel: [151165.682165] mt7530 mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control rx/tx
Fri Feb 24 13:47:16 2023 kern.info kernel: [151165.689768] br-lan: port 3(lan3) entered blocking state
Fri Feb 24 13:47:16 2023 kern.info kernel: [151165.695068] br-lan: port 3(lan3) entered forwarding state
Fri Feb 24 13:47:16 2023 daemon.notice netifd: Network device 'lan3' link is up
Fri Feb 24 13:47:25 2023 kern.info kernel: [151175.037269] mt7530 mdio-bus:1f lan3: Link is Down
Fri Feb 24 13:47:25 2023 kern.info kernel: [151175.042227] br-lan: port 3(lan3) entered disabled state
Fri Feb 24 13:47:25 2023 daemon.notice netifd: Network device 'lan3' link is down
Fri Feb 24 13:47:28 2023 kern.info kernel: [151177.230332] mt7530 mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control off
Fri Feb 24 13:47:28 2023 kern.info kernel: [151177.237752] br-lan: port 3(lan3) entered blocking state
Fri Feb 24 13:47:28 2023 kern.info kernel: [151177.243063] br-lan: port 3(lan3) entered forwarding state
Fri Feb 24 13:47:28 2023 daemon.notice netifd: Network device 'lan3' link is up
Fri Feb 24 15:30:48 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 15:30:48 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 15:30:48 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 15:35:45 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 15:35:45 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 15:35:45 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 15:35:45 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 15:41:24 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 15:41:24 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: associated (aid 3)
Fri Feb 24 15:41:24 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED d4:a3:3d:c1:03:e1 auth_alg=ft
Fri Feb 24 15:47:15 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 15:47:15 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 15:47:16 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 15:47:20 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED d4:a3:3d:c1:03:e1
Fri Feb 24 15:47:20 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 15:47:21 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 16:00:40 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 16:00:40 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 16:00:40 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 16:26:41 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 16:26:41 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 16:26:42 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 16:30:29 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 16:30:29 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 16:30:29 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 16:37:42 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 16:37:42 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 16:37:43 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 17:23:42 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 17:23:42 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 17:23:42 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 18:02:40 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 18:02:40 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 18:02:41 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 18:13:23 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 18:13:23 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Fri Feb 24 18:13:23 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=ft
Fri Feb 24 18:34:46 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Feb 24 18:34:46 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: associated (aid 3)
Fri Feb 24 18:34:46 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED d4:a3:3d:c1:03:e1 auth_alg=ft
Fri Feb 24 18:35:39 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED d4:a3:3d:c1:03:e1
Fri Feb 24 18:35:39 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: disassociated
Fri Feb 24 18:35:40 2023 daemon.info hostapd: phy1-ap0: STA d4:a3:3d:c1:03:e1 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 19:45:41 2023 daemon.notice netifd: wan (2663): udhcpc: sending renew to server 192.168.1.1
Fri Feb 24 19:45:41 2023 daemon.notice netifd: wan (2663): udhcpc: lease of 192.168.1.2 obtained from 192.168.1.1, lease time 86400
Fri Feb 24 20:07:16 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Fri Feb 24 20:07:16 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 20:07:17 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 20:36:40 2023 daemon.err uhttpd[2227]: [info] luci: accepted login on / for root from 192.168.0.200
Fri Feb 24 20:38:11 2023 authpriv.info dropbear[11960]: Child connection from 192.168.0.200:38596
Fri Feb 24 20:38:13 2023 authpriv.notice dropbear[11960]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:IxxZxaxzJ7QpaU6nVA262VDia2dNQPjMKQ+4+FccQcI from 192.168.0.200:38596
Fri Feb 24 20:40:10 2023 authpriv.info dropbear[11960]: Exit (root) from <192.168.0.200:38596>: Disconnect received
Fri Feb 24 21:20:19 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 04:68:65:8b:ee:f8
Fri Feb 24 21:20:19 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: disassociated due to inactivity
Fri Feb 24 21:20:20 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Feb 24 22:30:04 2023 daemon.notice netifd: Network device 'lan3' link is down
Fri Feb 24 22:30:04 2023 kern.info kernel: [182500.263868] mt7530 mdio-bus:1f lan3: Link is Down
Fri Feb 24 22:30:04 2023 kern.info kernel: [182500.268829] br-lan: port 3(lan3) entered disabled state
Sat Feb 25 07:45:42 2023 daemon.notice netifd: wan (2663): udhcpc: sending renew to server 192.168.1.1
Sat Feb 25 07:45:42 2023 daemon.notice netifd: wan (2663): udhcpc: lease of 192.168.1.2 obtained from 192.168.1.1, lease time 86400
Sat Feb 25 08:39:41 2023 daemon.err uhttpd[2227]: [info] luci: accepted login on / for root from 192.168.0.200
After removed the case cover, without modify any configuration it seems running stable and no more for disconnection for 4 days already. Possible over temp throttle issue, still observing for more time… will update again.
Do you have made any ventilation holes into the case?
By default case is very closed except the hole for boot-switch and the other right from it. I already mentioned that at least holes for fan are needed,but airflow needs also an entry (if fan used for outgoing flow)
There are two holes (for wall mounting) beneath the case, the case is sitting directly on top of a fan (suction) of laptop cooling pad.
I checked the temp by touching the case from time to time at the beginning of this setup, room temp is AC cooled at 26c-28c, and the case barely feel hot even without AC, just very slightly warm, had it ran for months without problem. (sorry for unable to obtain scientific temp measurement result due to lack of tool)
Although not strongly convinced its caused by the heat issue, but the periodic disconnect issue apparently gone after take off the top cover.
The wall mounting holes are not enough for cooling. Frank really aimed for home-made holes, manually created. You also might want to add a fan pointing towards the components, rather than trying to blow air from under neat. As Frank stated you might want to integrate an actual custom fan into the casing somehow.
Memory
I found the memory usage very high. Keep in mind the BPI-R3 has “only” 2GB ram. And you were using basically all of it (98%)! Assuming there is no swap partition, your router will crash since it has no additional RAM left anymore!!
What is using so much ram? Could you try to login via SSH maybe, and run commands like top. Shift+ M should order the processes by memory usage, in my case I’m not so sure about that. Since the top version on my OpenWRT seems old, I can’t even use interactive mode…
Anyway… hopefully you are able to pin point the process that is using a lot of memory. I mean look at my old router with only 56MB RAM, and I have more RAM available then you have…
OpenWRT
Last, I want to point out that the snapshot versions aren’t as stable as you might want it to be. It’s not advised to run snapshot OpenWRT version during production.
After remove the top cover and ran for straight a week without disconnection issue, I putted back the cover and rebooted, trying to reproduce the disconnection issue see if its really caused by overheat, which I really doubt as if it is caused by the heat with following evidence.
As the previous disconnection happened about every 2 days periodically, if it is heat or ventilation issue it should reach throttle point quicker than 48 hours.
With the help of the cooling pad, the case is barely hot, only slightly warm to touch (feels like when we check temp by touch someone’s forehead.)
Still, this is an unconfirmed case. I will try to drill holes on top of the case to adapt an exhaust fan if the disconnection happens again after put back the cover.
Memory Usage
I’ve checked the process list before when the memory usage was high, found no clue.
The only suspected process was transmission daemon I enabled for download torrents when my PC is off.
After disabled transmission daemon, I didn’t have high memory usage so far. (200MiB+ over 2GiB)
Checked the log, and the records are not looking good. Current highest is 78c, will check record again tomorrow see how high will it go after AC auto turned off.
Current settings
OEM metal case, fully closed.
Exhaust fan under the case pulling air from two mounting holes. (laptop cooling pad)
Room AC switched to FAN mode, and with OFF timer set at 2am.
only 3 client devices connected, no heavy network usage. Probably only 1 iPad is streaming from Netflix, other 2 phone devices are idling.
Sun Mar 5 23:50:37 PST 2023
mt7915_phy1-isa-18000000
Adapter: ISA adapter
temp1: +53.0°C (high = +120.0°C, crit = +110.0°C)
Checked the log, and the records are not looking good.
Not looking good? Maybe you want to share your logging…?
It could be overheat issues indeed, it could be software issue. We need to deep futher.
Regarding memory usage, 200M is at least better than 2GB. So hopefully there is no additional sudden memory increase anymore… And consider a dedicated machine/SBC for running the torrent daemon.
Thank you frank, I’ve also read your note in another topic. In such case, it proves that my case isn’t temperate related, if the output from sensors command is higher than the actual reading. I got 50c average through 48hrs of logging record, only a spike up to 82c on 2.4Ghz for less than a minute, way far from the threshold.
Hope this one is helpful.
I updated to latest snapshot, try to see if the memory usage would still reach high percentage after few days.
Here is the screenshot, hope it helps.
well… now… it’s not 98% memory usage anymore… It’s using 200Mb.
Anyway, use the same htop command and the same ordering by RES column, whenever it reaches that high memory consumption again.
That being said, if 1% memory is used by dnsmaq process, that would be 20 Mb + .8% + .6% + 2x .2% + 10x .1 = 1% = ~ 65 Mb. Let’s round up to 80 Mb. Adding the rest of process shouldn’t really add up to 200Mbm, but more like 80Mb. I’m I right? Where is let’s say the remaining ~120MB being allocated towards?
I could be correct… just thinking out loud. Anyway, keep us posted when it’s 99% memory again!
That was after upgraded to latest snapshot & rebooted, the previous firmware was also using around 200MiB after fresh reboot, but 97% after 4 days of running. I will monitor the mem usage and give update.
Here you have a crash in ethernet driver not wifi.
Can you do anything on the system after this? If yes is wired network accessable? I guess system or at least network is completely broken.
Yes, whenever that I lost connection (Ethernet) to DHCP server (BPI-R3), my PC would pop up a warning, thats the time I noticed. I barely pay attention on Wifi on my phone, as it is connected to a dump AP (Redmi AX6000) but not BPI-R3.
I can’t do anything after lost connection, can’t do ssh, ping to server (192.168.0.1), only thing I can do is to power circle the BPI-R3 for a reboot.
Here is the screenshot, hope it helps.