Hi,
for quite some time i used an Edgerouter-X running OpenWrt with Adblock as the DNS in my home network. I never had issues with this configuration.
As the Arris Cable modem from my ISP has limited functionality I recently set the modem into bridge mode and configured the Edgerouter-X as my main router (using the most recent stable 19.07.4 build). I also have one TP-Link Archer C7 and one Asrock G10 running stock firmware but configured as APs. This configuration works fine, but since I use the Edgerouter-X as the main router (for about a week now) my network went down completely three or four times and I had to power-cycle the Edgrouter-X to make it work again. It also happens if hardware acceleration is turned of. And when the network is down I can't access the TP-Link or the Asrock even they are configured with static IP Adresses.
Has anyone else had similar experiences with an Edgerouter-X and OpenWRT?
No. My Edgerouter X has been very stable on 19.07.4 and prior OpenWrt releases. It is our home gateway router, and has two AP's (also flashed with OpenWrt) connected to it.
More information about your configuration will be needed to help debug this.
I recently upgraded to OpenWrt 19.07.4 r11208 and resettet to the OpenWrt defaults. The error occurs even with this default configuration of OpenWrt.
The WAN port is connected to an Arris TG862s cable modem. Of course there are multiple devices connected to the LAN which are mostly clients. But there are also two wifi access points with static IP addresses (Tplink Archer C7, Asrock G10).
As the problem just occurred while i was typing this text, i could confirm, that I could access the devices with static IPs when i defined a static IP for my notebook. But access to the Edgerouter was not possible.
As it is the the default configuration for OpenWrt I am not sure if there is any other information which could help to pin down the problem.
I don't think there is any temperature sensor. In the other thread it was noted that external heat is the main problem. There's very little internal heating. Convective cooling would be improved by mounting on end with port 4 down, but don't block the air holes on what is now the bottom.
Any time there seems to be hardware instability, try a different power supply. The input is built for 24 volts so a 24 volt power cube may be better, or supply Ubiquiti 24 volt PoE to port 0.
Thank you @mk24 for mentioning the power supply. I found a post where a user mentioned problems after switching from PoE to 12V. I could not try switching to PoE because i do not have an injector, but i tried to use a more powerful 12V power supply but the the router keeps freezing.
I also tried heating the router intentionally but this did not trigger the issues, so i think i can rule out overheating issues.
What i find interesting is the fact, that the router seems to work without issues with either EdgeOS or OpenWRT 18.06.9 (which I am using at the moment).
I'm having similar @bruno_l LAN setup and ER-X crash problem.
Hardware Offloading is active and sirq is almost 0% and just 1%-5% few time with my FTTC DL100Mbps/UL30Mbps full usage.
I've been using ER-X with Open-WRT for years without any problem until 19.07.3, 5 days ago I upgrades to 19.07.5 and network problem began, I head around 4 crash up to now.
When ER-X crash I can't ssh it and can't ping the router or 1.1.1.1 but once I could ping the AP.
The first time the problem happened I was using all the DL and UL bandwidth but then I couldn't reproduce the crash forcing traffic load.
The only solution is to unplug the ER-X power supply and than power it again.
Once I noticed that with uptime that the router rebooted alone.
Once, after a temporary network stop, maybe the router uncrashed alone and I could ssh and see this log:
As suggested somewhere I tried to do a clean reinstall of OpenWRT following the instructions on the device page (starting with a custom image vor 19.07.2 and then flashing the official release). I used 19.07.2 until it froze (also hardware flow offloading did not work with this release) and also tried to upgrade to 19.07.5 which also kept freezing.
In a next step i flashed the current snapshot release (Kernel Version 5.4.86) which is running without an issue for 24h. Today also a PeO power supply arrived, but I have not installed it yet.
I did not check the major differences between 19.07.5 and the snapshot but i already noticed, that the switch configuration changed. It seems DSA driver is used now.