Hello,
We have a park of 130 routers (RUT240/RUT950) live in the field, 400 more to come used to provide connectivity to EV charging stations.
We experience a lot of routers that do not “survive” an auto-reboot at night or due to ping reason. Maybe 3 or 4 per week.
When we send someone, we found the router with the power led on, and the status bar blinking and we had to unplug it and plug it again.
All of our routers have been updated to the lastest firmware (07.05).
What can we do ?
What do the logs say?
This looks like it is not connecting to the mobile network.
Did you try setting a static APN?
I noticed that auto APN is not working proper after last firmware update 7.05.3, giving me " Mobile network rejection was recently detected" and “All available APNs were tried, unable to make connection to operator”
Issue tracker => Auto APN not working correct after 7.05.3 update
We use a static custom APN.
The logs doesn’t seem to show something past the current boot.
I also found that time may be wrong as it jumps after ntpclient is launched:
Thu Nov 9 03:46:51 2023 kern.notice kernel: [ 0.000000] Linux version 5.4.251 (app@runner-3levzzyc-project-352-concurrent-0) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16279-5cc0535800)) #0 Thu Oct 5 06:04:53 2023
Thu Nov 9 03:46:51 2023 kern.info kernel: [ 0.000000] printk: bootconsole [early0] enabled
Thu Nov 9 03:46:51 2023 kern.info kernel: [ 0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
Thu Nov 9 03:46:51 2023 kern.info kernel: [ 0.000000] MIPS: machine is Teltonika RUT2XX
Thu Nov 9 03:46:51 2023 kern.info kernel: [ 0.000000] SoC: Atheros AR9330 rev 1
...
Thu Nov 9 03:49:10 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is now up
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain test
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain onion
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain localhost
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain local
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain invalid
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain bind
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using only locally-known addresses for domain lan
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using nameserver 10.4.0.240#53
Thu Nov 9 03:49:10 2023 daemon.info dnsmasq[3176]: using nameserver 10.4.0.230#53
Thu Nov 9 03:49:11 2023 user.warn mwan3-hotplug[5613]: hotplug called on mob1s1a1 before mwan3 has been set up
Thu Nov 9 03:49:15 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
Thu Nov 9 09:34:07 2023 kern.warn kernel: [ 173.025983] process 'ntpclient' launched '/usr/sbin/ntpd-hotplug' with NULL argv: empty string added
Thu Nov 9 09:34:07 2023 daemon.info dfota[4557]: WAN found on interface: mob1s1a1_4
Thu Nov 9 09:34:07 2023 daemon.info dfota[4557]: Preparing for gsm.modem0 update!
Thu Nov 9 09:34:08 2023 daemon.info dfota[4557]: Searching for updates...
Thu Nov 9 09:34:09 2023 daemon.info dfota[4557]: No update found!
Seems logs are saved in RAM so it makes sense.
By status leds do you mean the signal strength leds or connection status leds?
Are you able to login on site without reboot, if DHCP enabled do you get a IP?
This topic was automatically closed after 15 days. New replies are no longer allowed.