WE3926 blocking local Network Traffic
Posted: Sun Dec 13, 2020 11:38 pm
I have a WE3926 with Quectel EC25 modem running GoldenOrb_2020-03-01 ( OpenWrt 18.06.7 ) firmware. It seems to be working as far as I can tell. I bought it to connect to marina wifi and have cell phone failover.
My issue is this, on my network I have a Yacht Devices YDNR-02 it takes my boat instrument data and converts it to UDP/TCP data stream on ports 1456 and 1457, that my mobile devices can listen to and display the data. It connects as a client via wifi. Initially it works fine I can see it on a network IP scan, log into its web interface, and my devices can receive the data streams. After about 30-45mins, data to my local devices, stop, I can’t log into the web interface, I can’t see it on a network scan, BUT I can ping the YDNR and it does show inside the WE3926 connected devices. So the YDNR is still on the network. I can still see the YDNR via my boat instruments and it is working correctly on that side of things.
Previously I had all my equipment working on a cheap TP-Link wifi router and NO issues of the YDNR dropping.
If I reboot the YDNR nothing happens, If I reboot the WE3926 I get the YDNR back on the network for another 30-45mins. So this leads me to believe it is something inside the settings of the WE3926 that is eventually blocking the YDNR traffic.
I have absolutely no idea what could cause this or even what terminology to use to figure out why it would block me from logging into the web interface or the traffic from the YDNR.
Any help would be greatly appreciated.
My issue is this, on my network I have a Yacht Devices YDNR-02 it takes my boat instrument data and converts it to UDP/TCP data stream on ports 1456 and 1457, that my mobile devices can listen to and display the data. It connects as a client via wifi. Initially it works fine I can see it on a network IP scan, log into its web interface, and my devices can receive the data streams. After about 30-45mins, data to my local devices, stop, I can’t log into the web interface, I can’t see it on a network scan, BUT I can ping the YDNR and it does show inside the WE3926 connected devices. So the YDNR is still on the network. I can still see the YDNR via my boat instruments and it is working correctly on that side of things.
Previously I had all my equipment working on a cheap TP-Link wifi router and NO issues of the YDNR dropping.
If I reboot the YDNR nothing happens, If I reboot the WE3926 I get the YDNR back on the network for another 30-45mins. So this leads me to believe it is something inside the settings of the WE3926 that is eventually blocking the YDNR traffic.
I have absolutely no idea what could cause this or even what terminology to use to figure out why it would block me from logging into the web interface or the traffic from the YDNR.
Any help would be greatly appreciated.