It was for example because its the same ISP, but its 2 different locations. The DSL setup is at my home and the 4G is on a remote location on the countryside, there is just a house there with normal electrical devices, nothing special.
Edit: For now im using the package mentioned above with a timeout of 90s as a failsafe when uqmi cant reconnect in 60s. I hope that works.
Ahh OK
You could extend the time for uqmi to re-connect.
Change 20 to 30, to add 30sec, in /lib/netifd/proto/qmi.sh
# Check registered network and used radio technology
first_registration=true
wait_for_registration=true
while [ "$wait_for_registration" = true ] && [ $x -lt 20 ]
I will do that and report back , i hope thats it.
Hi again,
it was reconnecting for the past 4 times but i had to raise the sleep between registration to 10s like this.
# Check registered network and used radio technology
first_registration=true
wait_for_registration=true
while [ "$wait_for_registration" = true ] && [ $x -lt 30 ]
do
[ $first_registration = false ] && sleep 10
since it never did that 4 times in a row i consider this a huge step forward.
In the log you can see that it allways takes a few tries to reach a network. A neighbour told me that the cell tower in the village is very old and its to many people now using it.
Sun Jul 10 22:48:29 2022 daemon.notice netifd: Interface '4G' is now down
Sun Jul 10 22:48:29 2022 daemon.notice netifd: Interface '4G' is setting up now
Sun Jul 10 22:48:29 2022 daemon.notice netifd: 4G (16971): PINcode disabled
Sun Jul 10 22:48:29 2022 daemon.notice netifd: 4G (16971): Data format set to ra w-ip
Sun Jul 10 22:48:30 2022 daemon.notice netifd: 4G (16971): Default profile numbe r: 1
Sun Jul 10 22:48:30 2022 daemon.notice netifd: 4G (16971): searching on 26203
Sun Jul 10 22:48:40 2022 daemon.notice netifd: 4G (16971): searching on 26203
Sun Jul 10 22:48:50 2022 daemon.notice netifd: 4G (16971): searching on 26202
Sun Jul 10 22:49:00 2022 daemon.notice netifd: 4G (16971): searching on 26202
Sun Jul 10 22:49:10 2022 daemon.notice netifd: 4G (16971): registered on 26203
Sun Jul 10 22:49:11 2022 daemon.notice netifd: 4G (16971): Registered to Willkom men on LTE
Sun Jul 10 22:49:12 2022 daemon.notice netifd: 4G (16971): Default profile conne cted with ipv4
Sun Jul 10 22:49:12 2022 daemon.notice netifd: 4G (16971): Setting up wwan0
Sun Jul 10 22:49:12 2022 daemon.notice netifd: Interface '4G' is now up
Sun Jul 10 22:49:12 2022 user.notice firewall: Reloading firewall due to ifup of 4G (wwan0)
Sun Jul 10 22:49:13 2022 user.notice firewall: Reloading firewall due to ifupdat e of 4G (wwan0)
Mon Jul 11 22:48:13 2022 daemon.notice netifd: Interface '4G' has lost the conne ction
Mon Jul 11 22:48:13 2022 daemon.notice netifd: 4G (31853): Stopping network 4G
Mon Jul 11 22:48:14 2022 daemon.notice netifd: 4G (31853): Command failed: Permi ssion denied
Mon Jul 11 22:48:14 2022 daemon.notice netifd: Interface '4G' is now down
Mon Jul 11 22:48:14 2022 daemon.notice netifd: Interface '4G' is setting up now
Mon Jul 11 22:48:15 2022 daemon.notice netifd: 4G (31968): PINcode disabled
Mon Jul 11 22:48:15 2022 daemon.notice netifd: 4G (31968): Data format set to ra w-ip
Mon Jul 11 22:48:15 2022 daemon.notice netifd: 4G (31968): Default profile numbe r: 1
Mon Jul 11 22:48:15 2022 daemon.notice netifd: 4G (31968): searching on 26203
Mon Jul 11 22:48:25 2022 daemon.notice netifd: 4G (31968): searching on 26203
Mon Jul 11 22:48:36 2022 daemon.notice netifd: 4G (31968): searching on 26203
Mon Jul 11 22:48:46 2022 daemon.notice netifd: 4G (31968): searching on 26203
Mon Jul 11 22:48:56 2022 daemon.notice netifd: 4G (31968): searching on 26202
Mon Jul 11 22:49:06 2022 daemon.notice netifd: 4G (31968): searching on 26202
Mon Jul 11 22:49:16 2022 daemon.notice netifd: 4G (31968): registered on 26203
Mon Jul 11 22:49:16 2022 daemon.notice netifd: 4G (31968): Registered to Willkom men on LTE
Mon Jul 11 22:49:17 2022 daemon.notice netifd: 4G (31968): Default profile conne cted with ipv4
Mon Jul 11 22:49:17 2022 daemon.notice netifd: 4G (31968): Setting up wwan0
Mon Jul 11 22:49:17 2022 daemon.notice netifd: Interface '4G' is now up
Mon Jul 11 22:49:18 2022 user.notice firewall: Reloading firewall due to ifup of 4G (wwan0)
Mon Jul 11 22:49:19 2022 user.notice firewall: Reloading firewall due to ifupdat e of 4G (wwan0)
Tue Jul 12 22:48:19 2022 daemon.notice netifd: Interface '4G' has lost the conne ction
Tue Jul 12 22:48:20 2022 daemon.notice netifd: 4G (14612): Stopping network 4G
Tue Jul 12 22:48:20 2022 daemon.notice netifd: 4G (14612): Command failed: Permi ssion denied
Tue Jul 12 22:48:20 2022 daemon.notice netifd: Interface '4G' is now down
Tue Jul 12 22:48:20 2022 daemon.notice netifd: Interface '4G' is setting up now
Tue Jul 12 22:48:21 2022 daemon.notice netifd: 4G (14727): PINcode disabled
Tue Jul 12 22:48:21 2022 daemon.notice netifd: 4G (14727): Data format set to ra w-ip
Tue Jul 12 22:48:21 2022 daemon.notice netifd: 4G (14727): Default profile numbe r: 1
Tue Jul 12 22:48:22 2022 daemon.notice netifd: 4G (14727): searching on 26203
Tue Jul 12 22:48:32 2022 daemon.notice netifd: 4G (14727): searching on 26203
Tue Jul 12 22:48:42 2022 daemon.notice netifd: 4G (14727): searching on 26203
Tue Jul 12 22:48:52 2022 daemon.notice netifd: 4G (14727): searching on 26203
Tue Jul 12 22:49:02 2022 daemon.notice netifd: 4G (14727): searching on 26202
Tue Jul 12 22:49:12 2022 daemon.notice netifd: 4G (14727): searching on 26202
Tue Jul 12 22:49:22 2022 daemon.notice netifd: 4G (14727): registered on 26203
Tue Jul 12 22:49:23 2022 daemon.notice netifd: 4G (14727): Registered to Willkom men on LTE
Tue Jul 12 22:49:24 2022 daemon.notice netifd: 4G (14727): Default profile conne cted with ipv4
Tue Jul 12 22:49:24 2022 daemon.notice netifd: 4G (14727): Setting up wwan0
Tue Jul 12 22:49:24 2022 daemon.notice netifd: Interface '4G' is now up
Tue Jul 12 22:49:24 2022 user.notice firewall: Reloading firewall due to ifup of 4G (wwan0)
Tue Jul 12 22:49:25 2022 user.notice firewall: Reloading firewall due to ifupdat e of 4G (wwan0)
Wed Jul 13 22:48:56 2022 daemon.notice netifd: Interface '4G' has lost the conne ction
Wed Jul 13 22:48:56 2022 daemon.notice netifd: 4G (29667): Stopping network 4G
Wed Jul 13 22:48:57 2022 daemon.notice netifd: 4G (29667): Command failed: Permi ssion denied
Wed Jul 13 22:48:57 2022 daemon.notice netifd: Interface '4G' is now down
Wed Jul 13 22:48:57 2022 daemon.notice netifd: Interface '4G' is setting up now
Wed Jul 13 22:48:57 2022 daemon.notice netifd: 4G (29782): PINcode disabled
Wed Jul 13 22:48:58 2022 daemon.notice netifd: 4G (29782): Data format set to ra w-ip
Wed Jul 13 22:48:58 2022 daemon.notice netifd: 4G (29782): Default profile numbe r: 1
Wed Jul 13 22:48:58 2022 daemon.notice netifd: 4G (29782): searching on 26203
Wed Jul 13 22:49:08 2022 daemon.notice netifd: 4G (29782): searching on 26202
Wed Jul 13 22:49:18 2022 daemon.notice netifd: 4G (29782): searching on 26202
Wed Jul 13 22:49:29 2022 daemon.notice netifd: 4G (29782): registered on 26203
Wed Jul 13 22:49:29 2022 daemon.notice netifd: 4G (29782): Registered to Willkom men on LTE
another thing i did was upgrading the uqmi version to 0.6. Did you made changes that can explain that it is working better now ?
Hi
No, it is only some minor cosmetics changes in 0.6.
The change of the delay seems to be the solution in your case. I don't have any better solution, for the moment.
I still don't understand why your ISP is disconnecting your LTE modem from the network. How will your normal cell-phone behave?
I did put the Simcard from the Router in my cellphone because its using another Provider. I didnt notice any reconnect for 2 days, there where 5 new ip adresses i think in that time when i checked.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.