WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

TRB140 internal modem reconnects every hour after the scheduled reboot

0 votes
343 views 14 comments
by anonymous

Today my TRB140 reboots at midnight as every Sunday at 23:59 and from that time I receive a mail

  • Device name - TRB140; Event type - Mobile Data; Event text - Mobile data connected (internal modem)

every hour. I rebooted the device but there is nobody so I could perform only a soft reboot. The only result was that the previous connection times (1:00, 2:00,..) changed to the time of the reboot (7:24, 8:24,..). So every hour I receive a mail form TRB140, from my router (WAN2 is up) from my VOIP gateway (IP has changed)... And also my VPNs are corrupted

In the kernel log I see this repeatedly:

 10:24:56 2023 daemon.info dnsmasq-dhcp[5907]: read /etc/ethers - 0 addresses
Mon Jan  9 10:24:56 2023 kern.info kernel: [10921.884486] br-lan: port 1(eth0) entered disabled state
Mon Jan  9 10:24:57 2023 daemon.notice netifd: bridge 'br-lan' link is down
Mon Jan  9 10:24:57 2023 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon Jan  9 10:24:57 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (rmnet0)
Mon Jan  9 10:24:57 2023 kern.info kernel: [10923.104180] qcom-emac 7c40000.qcom,emac eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Jan  9 10:24:57 2023 kern.info kernel: [10923.111553] br-lan: port 1(eth0) entered forwarding state
Mon Jan  9 10:24:57 2023 kern.info kernel: [10923.116984] br-lan: port 1(eth0) entered forwarding state
Mon Jan  9 10:24:57 2023 daemon.notice netifd: Network device 'eth0' link is up
Mon Jan  9 10:24:57 2023 daemon.notice netifd: bridge 'br-lan' link is up
Mon Jan  9 10:24:57 2023 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Jan  9 10:24:58 2023 user.notice ddns-scripts[6288]: myddns: pid 6288 started at 2023-01-09 10:24
Mon Jan  9 10:24:59 2023 user.notice ddns-scripts[4808]: myddns: pid 4808 terminated by sigterm at 2023-01-09 10:24
Mon Jan  9 10:24:59 2023 user.notice dnsmasq: dhcp_check(): using cached value: 0
Mon Jan  9 10:25:00 2023 daemon.info dnsmasq[5907]: read /etc/hosts - 4 addresses
Mon Jan  9 10:25:00 2023 daemon.info dnsmasq[5907]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Jan  9 10:25:00 2023 daemon.info dnsmasq-dhcp[5907]: read /etc/ethers - 0 addresses
Mon Jan  9 10:25:01 2023 kern.info Mobile data connected (internal modem)

Is there a way how to return my TRB140 back to normal, please? The troubleshooting file is attached. As it appears exactly every hour +1 minute for reboot itself it is not a coincidence

1 Answer

0 votes
by anonymous
Hi,

Would you please clarify the below to help me if I understood you correctly:

Do you want to TRB140 to not to reboot every hour?
What are your desired configurations and expected router behavior?

Regards,
Ramandeep S.
by anonymous

Hello,

thank you for your reaction.

TRB140 does NOT reboot every hour. It only reconnects its LTE modem every hour.

Soft reboot of the device via menu does not change this behaviour which appeared affter the last scheduled reboot this night.

The reboot is set once per week every Sunday at 23:59. The settings of TRB140 was set during August, last modification was the FW upgrade in September. Since than the device was left alone and has been working perfectly till today.

by anonymous

Is it possible for you to perform device reset?
Remember: If you do not have physical access to the device, you might loose access to the device. 

Apart from that, when the TRB140 is connected to the internet. Go to CLI (Services->CLI) and issue the below and send the results here:
dfota

 

by anonymous
Well, I can do it but I am afraid. Isn't it a factory default reset? The device is in PassThrough mode and will not be physically accessible till March and its working state is crucial. Is it safe to perforn the command? Will be the PassThrough setting kept?
by anonymous
It would not be a safe practice then.
Did you perform "dfota" command?
Device is getting the lease renewed from operator after every one hour.
Also, it is running "EC25EUGAR06A05M4G_BETA1108" modem firmware, which quite old for this device.
"Dfota" command will execute the modem firmware upgrade script and for this working internet connection is required.
Make sure to perform this command shortly after the LTE connection has been rebooted, so that you can have enough time for modem upgrade.
by anonymous
Oh I understand now (or hope so). dfota is modem upgrade without a reset. So reset could not be performed now, but I can run dfota to update the firmware of the modem. I understand from your answer that this is a safe operation. I will do it in the evening after a new reconnection to have an hour of internet connection and let you know. I hope it will not brick the device.
by anonymous

Is it just

dfota

and nothing else? It does not seem to work

by anonymous

Re-flash the firmware and then run the command "dfota -u" on CLI. To reflash the firmware, follow below instructions:

1. Download the firmware version "TRB1_R_00.07.02.7" from HERE.
2. Go to webui and navigate to System->Firmware and select update from "file", browse the TRB1_R_00.07.02.7.bin file that you downloaded in the first step and select it. ( leave "Keep settings" turned on). 
3. Wait for verification page and click on "Proceed" button. It will take 2-7 mins for the update to complete. Once completed, go to CLI and check for internet connect with command "ping 8.8.8.8", if the ping is successful, it means internet is working.
4. Afterwards, issue the command "dfota -u" and see if it works. This command will initiate the modem update process.

by anonymous

I succesfully reflashed the FW but dfota -u is still not working

what about the commands from the removed suggestion? The first one will probably not work

opkg remove dfota
opkg update
opkg install dfota
dfota -u

by anonymous
Just confirmed that TRB140 does not support modem update functionality at this time. Performing a reset could do some trick at this time.
by anonymous

Reset could not be done now as nobody is there. What about sending me a new firmware for the modem as a file? There is an option to upgrade firmware and/or modem via UI. But I do not know if it can automatically reboot after that operation. So if it is a safe step I can do it. Otherwise I have to wait till March :-)

by anonymous
After reflashing FW of the device returned (permanently?) TRB140 to its previous state. No reconnection every hour since than. It is too soon to be sure but I am about to be a little bit optimistic. Thank you for your help and let us hope I will not need you.
by anonymous
Lets observe the unit for next 2-3 days and see if the issue reproduces.
by anonymous

I am sorry to say, you were right. The device reconnected again exactly after 60 hours. That is much better than after 60 minutes but still not optimal. There must be some counter... Couldn't we get to 60 days, please? :-)

by anonymous
As I wrote, the unit reconnected after 60 hours. This happened twice and then - voila - no unexpected reconnection; this positive behaviour even survived the scheduled reboot. I don't know what helped, but the key was reloading the firmware. I hope the problem does not return.