I’m Having a strange issue with a LoraWAN Gateway (SBC type device with allwinner H3) running armbian. The gateway would work for several days and then stop all network communication, it would disconnect from the router even though it is wired with an ethernet cable. I also tried to connect directly to the gateway via its fallback IP but the pings would timeout. Sometimes a reboot was all that needed to be done to make it work again.
The gateway is mounted in a 15U glass door network cabinet along with some switches, an Intel Nuc and mainly, an ISP router. The Router was broadcasting Wi-Fi from inside the cabinet and directly below the Nuc and Gateway.
So my question is, could the Wi-Fi signal affect the Gateway and cause this issue? It is to be noted that the Intel Nuc is not at all affected and is working perfectly fine.
You must log in or register to comment.
Extremely unlikely that wifi would affect it.
More likely a software crash or a hardware issue.
I’ve finally decided to replace the device and turn off the Wi-Fi, hopefully this will not happen again.
In theory, yes. That’s why most devices have those FCC / CE / etc stamps - these seals show that they have undergone EM compatibility testing and are most likely OK.
In this case, however, this looks like a kernel panic (as already said).
I don’t know much about loraWAN but I would check what frequencies it is on. I can’t imagine that WiFi would interfere as there are a lot of WiFi signals and LoraWAN wouldn’t function well.
I really suspect it is a software bug or some sort of hardware problem.
