u-blox plugin, questions while implementing support for TOBY-L210

[Aleksander Morgado]

Hey,

> In general, I think that the way that ublox intended to use the Toby-L2
> does not really match the way that MM works: In its application notes,
> ublox suggest to set the default bearer setting and then just to use the
> already connected context.
> If I map that to MM / NM, that would mean that MM exports the already
> connected default bearer (it already does, but who is using it?) and NM
> uses this bearer to show the device as connected. But that is not the
> way MM and NM work at the moment, right?

You're fully right here. If we wanted to properly support this
behavior, we would need to have some kind of "autoconnected" modem
behavior, so that e.g. NetworkManager could just use one connected
bearer object exposed by the modem instead of calling
Simple.Connect(). The initial bearer object exposed by MM won't have
IP settings, though, at least not implemented yet.

>
> This brings me to another question: What is the intention to export the
> initial bearer in ModemManager, as bearer object? Who will use this
> bearer object?
>

Whoever is interested in exposing the current initial EPS bearer
status :) MM has "initial EPS bearer settings" that can be configured
and queried, and on top of those, MM also exposes the "initial EPS
bearer" with the current status agreed with the network during LTE
registration.

> > One last question here; are the changes you're suggesting all
> > applicable and working in both bridge and router mode in the TOBY-L2?
> At the moment, I use the modem in router mode and I didn't test in
> bridge mode (yet). From the manuals, I don't see why it shouldn't work
> in bridge mode as well.
>
> When I think the the implementation works properly in router mode, I
> will do some tests in bridge mode, too.....
>

Nice!

-- 
Aleksander
https://aleksander.es