How to issue an "ifup broadband" when this is logged

[Mark Wahlert]

Hi!

On Tue, Feb 7, 2017 at 5:19 PM, Aleksander Morgado
<aleksander at aleksander.es> wrote:
>
> On Tue, Feb 7, 2017 at 11:10 PM, Russ Westrem
> <lspwaterproofing at gmail.com> wrote:
> > Out of it from everything I know.
> >
> > I'm thinking of going the easy route and doing a tail of the logfile
>
> Oh please no; don't do that.
>
> If you can run a script, you could source the  modemmanager.proto file and then:
>
> # Load connected bearer information
> bearerpath=$(modemmanager_get_bearer "${device}")
> bearerstatus=$(/usr/bin/mmcli --bearer "${bearerpath}")
>
> being ${device} the sysfs path configured for the modem
>
> The bearerstatus variable will say connected/disconnected, and if
> disconnected, you can ifup the interface yourself
>
>
> --
> Aleksander
> https://aleksander.es
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Russ and I have been fighting similar challenges.  We both want to
leverage MM, and we want to do everything possible to maintain a
stable "always on" connection.  Aleksander - did you notice anything
in the debug logs I had provided in my "connection instability" thread
that gave any indication as to why the disconnects were occurring?
I've not noticed any change in behavior with the ebc766 version.

I agree it would be excellent if we can incorporate additional logic
into MM to automate the re-up when the bearer status changes, but I'd
also like to get to the root of the disconnects so we can try to
minimize them.

I find it interesting that when the bearer state changes the network
interface still maintains its IP address.  There seems to be a
disconnect between MM and the resulting network interface.  I'm sure
most of this is my ignorance to how MM is working behind the scenes.