Hi
I cannot see any mobile disconnections.
I expected that was the case, since yesterday morning it still had the same IP as the day before. So I had already accepted that my guess (that it was mobile disconnections causing the problem) was wrong.
DHCP lease gets extended sucesfully and that's about it.
I assume you are referring to the mobile connection IP address here? Correct?
However, I did notice that the LAN1 port of the device keeps connecting and disconnecting.
LAN 1 is connected to the "device on the internal network" I mention in my original post. You may be seeing disconnections because we have been rebooting that device quite often during setup. Any LAN3 disconnections will be my laptop connecting to the LAN for testing.
Yesterday morning (27 April NZT), I couldn't even connect to the WebUI from the internal LAN. I had to hard reset the router.
Also yesterday, I set up the ping auto reboot feature, as per your suggestion. It appears to have worked. By that I mean that the charger was accepting WebUI connections on the external (mobile) interface this morning. Once I determined what the new IP address was, of course..
But I don't like that this is necessary. It is concerning that
- the router at some point starts refusing connections on the mobile interface
- and sometimes also on the internal gateway address (192.168.2.1)
We had an issue with talking to the "device on the internal network" (it's an embedded Linux device running PTXdist), that turned out to be caused by clashing DHCP servers. That is why we changed the router to use 192.168.2.1 for its DHCP server. Do you think our continuing problems could also be related to that?
I will attach a new troubleshooting file in case it helps. I really appreciate your assistance!
Paul