This is a quick brain-dump, as doing a quick Google search did not help, taking me to a mailing list thread I had posted about 2.5 years ago. I swear there’s a song in that… something about the dreaded Google Echo.
Anyway, unlike that last occasion where the modem wasn’t even seen at all (and no, I didn’t solve it, we stuffed a 3G dongle in the case in the end), this time around, ModemManager sees it. It just so happens that nmtui doesn’t do wireless broadband. These were the magic commands.
root@wsg-74fe481fe117:~# nmcli connection edit type gsm con-name telstra-nextg ===| nmcli interactive connection editor |=== Adding a new 'gsm' connection Type 'help' or '?' for available commands. Type 'describe [.]' for detailed property description. You may edit the following settings: connection, gsm, serial, ipv4 nmcli>
From here, we need to set the APN, telstra.internet.
nmcli> set gsm.apn telstra.internet
Having done that, we give the configuration a last check before saving it:
nmcli> print all … lots of settings … nmcli> save persistent Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection. Do you still want to save? (yes/no) [yes] (enter) Connection 'telstra-nextg' (57c78d91-4a66-475b-8843-2cba590fbcfd) successfully saved. nmcli> quit