Integration into NetworkManager
Dan Williams
dcbw at redhat.com
Mon Mar 20 18:46:16 UTC 2017
On Mon, 2017-03-20 at 16:48 +0000, colin.helliwell at ln-systems.com
wrote:
> So I've got a [reasonably?] sorted MM setup now - a mux driver
> providing two
> virtual ports: ttyMux0 (PPP) and ttyMux1 (Primary). I'm now wanting
> to hook
> the former into NetworkManager.
>
> From a fresh rootfs/boot-up, 'nmcli dev status' lists
>
> DEVICE TYPE STATE CONNECTION
>
> eth0 ethernet connected Wired connection 1
>
> ttyMux1 gsm disconnected --
>
> lo loopback unmanaged --
>
>
>
> I'm not sure why/where it's picking up ttyMux1, and in any case I
> need it to
> be using ttyMux0 instead. Where's this hooking in from?
>From ModemManager. NM reads the "control" port from ModemManager's
dbus interface, so it should be the same thing you see with 'mmcli -m
X'. But in the end it's just a name that NM chooses and NM doesn't do
anything interesting with it other than logging. Internally NM uses
the ModemManager D-Bus object path to refer to the modem.
> (Also struggling to create an NM connection - via nmcli - that it'll
> want to
> play with on that device... tips gratefully received..!)
[connection]
id=T-Mobile Internet
uuid=0083942e-b260-4b73-a1fd-860f3e6ca2c2
type=gsm
[gsm]
apn=epc.tmobile.com
[ipv4]
method=auto
[ipv6]
method=auto
is the file that would go into /etc/NetworkManager/system-connections.
Then 'nmcli con reload' and it should show up in NM and you can 'nmcli
con up "T-Mobile Internet"' and it'll use the first available WWAN
device to do that.
But with nmcli there are a couple ways. You can do it all from one
command-line if you want, though I just tried and it seems things
aren't quite working on NM 1.6.x as well as we'd like (filed https://bu
gzilla.gnome.org/show_bug.cgi?id=780323 for those).
Dan
More information about the ModemManager-devel
mailing list