Automatic Reconnect

[Lynx de Cat]

Dear Enrico,

So what I tried instead was to simply directly install the
ModemManager .ipk from OpenWrt master on my 22.03.2 environment. It
worked, and now with the updated Modem Manager with dispatcher script
as per:

https://github.com/openwrt/packages/commit/bc754f31cfdb004eefa43038f8f0827922107fc6

netifd correctly sees that the interface has gone down:

Wed Nov  2 20:38:54 2022 daemon.info [2716]: <info>  [modem0] state
changed (connected -> disconnecting)
Wed Nov  2 20:38:54 2022 daemon.info [2716]: <info>  [modem0] state
changed (disconnecting -> registered)
Wed Nov  2 20:38:54 2022 daemon.info [2716]: <info>  [modem0/bearer3]
connection #1 finished: duration 121s, tx: 258333 bytes, rx: 371928
bytes
Wed Nov  2 20:38:54 2022 user.notice modemmanager: interface wan
(network device wwan0) disconnected
Wed Nov  2 20:38:54 2022 daemon.notice netifd: Interface 'wan' has
lost the connection
Wed Nov  2 20:38:54 2022 daemon.notice netifd: Network device 'wwan0'
link is down
Wed Nov  2 20:38:54 2022 daemon.warn dnsmasq[1]: no servers found in
/tmp/resolv.conf.d/resolv.conf.auto, will retry

However, netifd does not seem to do anything at this point - there is
no attempt to reconnect.

So this has only shifted the problem to netifd. Is there a line in
/etc/config/network or similar to tell netifd to immediately reconnect
(which was presumably the point of informing netifd that the interface
went down?).

On Wed, Nov 2, 2022 at 6:05 AM Enrico Mioso <mrkiko.rs at gmail.com> wrote:
>
> Hi!
>
> May i ask if you are able to reproduce it with OpenWrt master + packages in the feeds for master?
>
> Thanks,
> Enrico
>
> On Tue, Nov 01, 2022 at 10:40:58AM +0000, Lynx de Cat wrote:
> > I am using ModemManager version 1.18.6 on OpenWrt 22.03.2 with my
> > RG502Q-EA Quectel modem. My 4G ISP disconnects any connection after
> > exactly 48 hours, in relation to which ModemManager reports:
> >
> > Mon Oct 31 17:37:46 2022 daemon.info [2719]: <info>  [modem0/bearer1]
> > verbose call end reason (6,36): [3gpp] regular-deactivation
> >
> > and just leaves things disconnected. So I lose internet connectivity,
> > and, worse still, netifd / ifstatus wan still seems to think the
> > connection is active.
> >
> > This seems related to this:
> >
> > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/775
> >
> > In any question, my question is: why is the default behaviour not to
> > automatically reconnect, and how can I ensure that ModemManager will
> > reconnect upon:
> >
> > Mon Oct 31 17:37:46 2022 daemon.info [2719]: <info>  [modem0/bearer1]
> > verbose call end reason (6,36): [3gpp] regular-deactivation
> >
> > So that I retain internet connectivity?