Reconnect modem quickly after network drops?

Hello,

I made this thread some time ago about network drops:

Since that and after digging a lot inside the router, I’ve been able to create a script that reconnect the router in 10 seconds instead of a few minutes like it was the case before.

I wonder if there’s a way to cut those 10 seconds even more? While reconnecting, the router does something like this:

daemon.warn dnsmasq[21207]: no servers found in /tmp/resolv.conf.auto, will retry
daemon.notice netifd: modem_1_1_2 (19393): Stopping network modem_1_1_2
daemon.notice netifd: modem_1_1_2_4 (21977): udhcpc: received SIGTERM 
daemon.notice netifd: Interface 'modem_1_1_2_4' is now down
daemon.notice netifd: Network alias '' link is down
daemon.notice netifd: Interface 'modem_1_1_2_4' has link connectivity loss
daemon.notice netifd: Interface 'modem_1_1_2_4' is disabled
daemon.notice netifd: modem_1_1_2 (19393): Command failed: Permission denied
daemon.notice netifd: Interface 'modem_1_1_2' is now down
daemon.notice netifd: Interface 'modem_1_1_2' is setting up now
daemon.notice netifd: modem_1_1_2 (19462): Waiting for SIM initialization
daemon.notice netifd: modem_1_1_2 (19462): Waiting for network registration 
daemon.notice netifd: modem_1_1_2 (19462): Starting network modem_1_1_2
daemon.notice netifd: modem_1_1_2 (19462): Setting up wwan0
daemon.notice netifd: Interface 'modem_1_1_2' is now up
daemon.notice netifd: Network device 'wwan0' link is up
daemon.notice netifd: Network alias 'wwan0' link is up 
daemon.notice netifd: Interface 'modem_1_1_2_4' is enabled
daemon.notice netifd: Interface 'modem_1_1_2_4' has link connectivity
daemon.notice netifd: Interface 'modem_1_1_2_4' is setting up now
daemon.notice netifd: modem_1_1_2_4 (19927): udhcpc: started, v1.30.1 
daemon.notice netifd: modem_1_1_2_4 (19927): udhcpc: sending discover 
daemon.notice netifd: modem_1_1_2_4 (19927): udhcpc: sending select for x.x.x.x
daemon.notice netifd: modem_1_1_2_4 (19927): udhcpc: lease of x.x.x.x obtained, lease time 7200
daemon.notice netifd: Interface 'modem_1_1_2_4' is now up
daemon.info dnsmasq[21207]: reading /tmp/resolv.conf.auto
daemon.info dnsmasq[21207]: using local addresses only for domain test
daemon.info dnsmasq[21207]: using local addresses only for domain onion
daemon.info dnsmasq[21207]: using local addresses only for domain localhost
daemon.info dnsmasq[21207]: using local addresses only for domain local
daemon.info dnsmasq[21207]: using local addresses only for domain invalid
daemon.info dnsmasq[21207]: using local addresses only for domain bind
daemon.info dnsmasq[21207]: using local addresses only for domain lan
daemon.info dnsmasq[21207]: using nameserver x.x.x.x#53
daemon.info dnsmasq[21207]: using nameserver x.x.x.x#53
user.info mwan3rtmon[15160]: Detect rtchange event.
user.notice firewall: Reloading firewall due to ifup of modem_1_1_2 (wwan0)
user.info mwan3rtmon[15160]: Detect rtchange event.
user.notice firewall: Reloading firewall due to ifup of modem_1_1_2_4 (wwan0)

Can I speed up this process? My ISP portable router reconnect in only 2 seconds so I’m sure I can come close to that with the Spitz too.

1 Like

Could you share how you improve that?

Will these commands help?

ubus call network.interface.wwan down
ubus call network.interface.wwan up