Re: primary device changing from boot to boot

I don't know if it's going to help you with this issue, but if you can hardcode a path to the serial port 
somewhere, take a look in the "/dev/serial/by-id" directory - it has symlinks to /dev/tty* entries that 
correspond to hardware serial ports currently connected. Names of the symlinks are generated from some kind 
of hardware IDs, so should be the same, no matter the order of enumeration (unless your hardware doesn't 
expose an unique ID that udev, or whatever makes those symlinks, could use)

05.09.2017, 19:39, "Tim Harvey" <tharvey gateworks com>:


This makes sense, but how do I configure NetworkManager to use the
device-id? I don't see it as an available option for type gsm, so
perhaps I need to edit the file in
/etc/NetworkManager/system-connections/mymodem and add it to the 'gsm'
section but maybe I've got larger issues because nm seems to not even
like ttyACM0 for the interface:

root@ventana:~# mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id
  Hardware | manufacturer: 'Sierra Wireless'
           | model: 'HL7588'
           | revision: 'RHL75xx.V.3.7.151600.201702071034.x7160_1'
           | supported: 'gsm-umts, lte'
           | current: 'gsm-umts, lte'
           | equipment id: '014284000070452'
  System | device:
           | drivers: 'cdc_acm, cdc_ncm'
           | plugin: 'Generic'
           | primary port: 'ttyACM0'
           | ports: 'wwx000011121314 (net), ttyACM0 (at),
wwx000011121316 (net), wwx00001112131a (net), wwx000011121318 (net),
ttyACM2 (at)'
  Numbers | own : '+19529136397'
  Status | lock: 'none'
           | unlock retries: 'unknown'
           | state: 'enabled'
           | power state: 'on'
           | access tech: 'unknown'
           | signal quality: '0' (cached)
  Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
           | current: 'allowed: 2g, 3g, 4g; preferred: none'
  Bands | supported: 'unknown'
           | current: 'unknown'
  IP | supported: 'ipv4, ipv6, ipv4v6'
  3GPP | imei: '014284000070452'
           | enabled locks: 'none'
           | operator id: 'unknown'
           | operator name: 'unknown'
           | subscription: 'unknown'
           | registration: 'idle'
  SIM | path: '/org/freedesktop/ModemManager1/SIM/0'

  Bearers | paths: 'none'

root@ventana:~# dbus-send --print-reply --system \
   --dest=org.freedesktop.ModemManager1 \
   /org/freedesktop/ModemManager1/Modem/0 \
   org.freedesktop.DBus.Properties.Get \
   string:org.freedesktop.ModemManager1.Modem string:DeviceIdentifier
method return time=1504629466.392532 sender=:1.3 -> destination=:1.25
serial=31 reply_serial=2
   variant string "6909b49a4d44867387a2b09b8095c579e031874c"

root@ventana:~# nmcli --version
nmcli tool, version 1.2.6

root@ventana:~# nmcli device status
eth0 ethernet disconnected --
ttyACM0 gsm unavailable --
can0 can unmanaged --
lo loopback unmanaged --

root@ventana:~# nmcli connection add type gsm ifname ttyACM0 con-name
mymodem apn vzwinternet
Connection 'mymodem' (ce87bf21-f700-4c61-8165-dda4b6c44ea8) successfully added.

nmcli connection add type gsm ifname ttyACM0 con-name mymodem apn vzwinternet

root@ventana:~# nmcli connection up mymodem
Error: Connection activation failed: No suitable device found for this
^^^^^^ not sure why ttyACM0 isn't acceptable here


ModemManager-devel mailing list
ModemManager-devel lists freedesktop org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]