I have a Linux box with multiple LTE connections, e.g. wwan0, wwan1, etc., all using the modems' qmi interfaces. If I send dozens of UDP packets, when a modem's antennae are disconnected, they get delivered (many seconds late) when I reconnect the antennae. This shows that the radio is queuing packets. How can I see the size and occupancy of LTE radios' queues from Linux (for LTE modems using the qmi interface)?

I would like to use [Waveshare SIM7600E-H 4G HAT](https://www.waveshare.com/wiki/SIM7600E-H_4G_HAT) on OpenWrt (ideally) or at least on Raspbian. I would ideally like understand what is needed to be done from the command line (better than use [luci](https://openwrt.org/docs/guide-user/luci/start) or any other gui configuration). Following I found from various sources for [OpenWrt](https://www.waveshare.com/wiki/Raspberry_Pi_OpenWrt_Tutorial_2:_Build_a_Portable_Raspberry_Pi_4G_Wireless_Router#Raspberry_Pi_programming_OpenWrt_image) , [Raspbian](https://www.waveshare.com/wiki/SIM7600E-H_4G_HAT#Raspbian) [Raspbian - NDIS dial-up and self-starting](https://www.waveshare.com/wiki/NDIS_dial-up_and_self-starting) , [Raspbian - RNDIS Dial-Up](https://www.waveshare.com/wiki/Raspberry_Pi_RNDIS_dial-up_Internet_access) * boot/config.txt should have at least enable_uart=1. Anything else? [Raspbian instructions](https://www.waveshare.com/wiki/SIM7600E-H_4G_HAT#Raspbian) mention also dtoverlay=disable-bt. * Linux kernel must support [option module](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/serial/option.c#n2059) , via CONFIG_USB_SERIAL_OPTION=m kernel config option (or =y builtin module). I'm not sure if this is enabled for OpenWrt, it should be for Raspbian kernel. * Minimal kernel version. I suppose that kernel 5.15 which is in [OpenWrt 23.05](https://openwrt.org/docs/techref/targets/kernelversions) should be new enough, the module is very old and SIM7600 support was added in kernel 4.20 ([MBIM support](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc6730df08a291e51e145bc65e24ffb5e2f17ab6)) and in 5.2 ([RNDIS mode](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5417a7e482962952e622eabd60cd3600dd65dedf)) . * Support for Raspberry Pi not (yet) mainlined kernel code. I see /boot/config.txt mentioned in [OpenWrt Raspberry Pi wiki](https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi) , which should mean that hopefully anything which kernel needs for Raspberry Pi and it's not in [the mainline kernel](https://kernel.org/) is patched in OpenWrt kernel. https://openwrt.org/toh/start claims that OpenWrt 23.05.5 supports all RPI versions, just the newest Raspberry Pi 5 needs snapshot (the future version). * user space configuration - module should be visible

lsusb |grep -i Qualcomm
ls -la /dev/ttyUSB[0-4]

If not, it's needed to manually load module and even configure the mode

modprobe option
echo "1e0e 9011" > /sys/bus/usb-serial/drivers/generic/new_id
# or
echo "1e0e 9011" > /sys/bus/usb-serial/drivers/option1/new_id

In archive https://files.waveshare.com/upload/2/29/SIM7600X-4G-HAT-Demo.7z (referenced in [Raspbian](https://www.waveshare.com/wiki/SIM7600E-H_4G_HAT#Raspbian)) is file SIM7600X-4G-HAT-Demo/Raspberry/c/sim7600_4G_hat_init which sets some GPIO values:

echo "4" > /sys/class/gpio/export
sleep 0.1
echo "out" > /sys/class/gpio/gpio4/direction
echo "0" > /sys/class/gpio/gpio4/value
echo "6" > /sys/class/gpio/export
sleep 0.1
echo "out" > /sys/class/gpio/gpio6/direction
echo "0" > /sys/class/gpio/gpio6/value

I suppose this example is not needed for actual Waveshare use. * libqmi is of course supported for both distros, [ OpenWrt 23.05 has 1.32.4](https://github.com/openwrt/packages/blob/openwrt-23.05/libs/libqmi/Makefile) (quite new version).

I'm trying to make my Huawei E5372 USB modem work with my Debian 12 Linux with Gnome Desktop Environment but having no luck with it. When listing modems with ModemManager the USB modem is shown:

tiago@dell-inspiron-15-3520:~$ sudo mmcli -L
    /org/freedesktop/ModemManager1/Modem/1 [huawei] E5372

When listing the USB Modem info with ModemManager the following is shown:

tiago@dell-inspiron-15-3520:~$ sudo mmcli -m 1
  --------------------------------
  General  |                 path: /org/freedesktop/ModemManager1/Modem/1
           |            device id: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  --------------------------------
  Hardware |         manufacturer: huawei
           |                model: E5372
           |    firmware revision: 21.221.19.00.00
           |            supported: gsm-umts
           |              current: gsm-umts
           |         equipment id: XXXXXXXXXXXXXXX
  --------------------------------
  System   |               device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
           |              drivers: huawei_cdc_ncm, option
           |               plugin: huawei
           |         primary port: cdc-wdm0
           |                ports: cdc-wdm0 (at), ttyUSB0 (at), wwx0c5b8f279a64 (net)
  --------------------------------
  Status   |       unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                state: registered
           |          power state: on
           |          access tech: lte
           |       signal quality: 100% (recent)
  --------------------------------
  Modes    |            supported: allowed: 2g; preferred: none
           |                       allowed: 3g; preferred: none
           |                       allowed: 4g; preferred: none
           |                       allowed: 2g, 3g, 4g; preferred: 4g
           |                       allowed: 2g, 3g, 4g; preferred: 4g
           |                       allowed: 2g, 3g, 4g; preferred: 3g
           |                       allowed: 2g, 3g, 4g; preferred: 3g
           |                       allowed: 2g, 3g, 4g; preferred: 2g
           |                       allowed: 2g, 3g, 4g; preferred: 2g
           |                       allowed: 3g, 4g; preferred: 4g
           |                       allowed: 2g, 4g; preferred: 4g
           |                       allowed: 2g, 3g; preferred: 3g
           |                       allowed: 3g, 4g; preferred: 3g
           |                       allowed: 2g, 3g; preferred: 2g
           |                       allowed: 2g, 4g; preferred: 2g
           |                       allowed: 2g, 3g, 4g; preferred: none
           |              current: allowed: 2g, 3g, 4g; preferred: none
  --------------------------------
  IP       |            supported: ipv4, ipv6, ipv4v6
  --------------------------------
  3GPP     |                 imei: XXXXXXXXXXXXXXXX
           |          operator id: 72404
           |        operator name: TIMBRASIL
           |         registration: home
           | packet service state: attached
  --------------------------------
  3GPP EPS | ue mode of operation: csps-2
  --------------------------------
  SIM      |     primary sim path: /org/freedesktop/ModemManager1/SIM/1
  --------------------------------
  Bearer   |                paths: /org/freedesktop/ModemManager1/Bearer/4
           |                       /org/freedesktop/ModemManager1/Bearer/3
           |                       /org/freedesktop/ModemManager1/Bearer/2

ModemManager bearer info are:

tiago@dell-inspiron-15-3520:~$ sudo mmcli -m 1 -b 2
  --------------------------------------
  General    |                     path: /org/freedesktop/ModemManager1/Bearer/2
             |                     type: default
  --------------------------------------
  Status     |                connected: no
             |    connection error name: org.freedesktop.ModemManager1.Error.Core.Unsupported
             | connection error message: Only IPv4 is supported by this modem
             |                suspended: no
             |              multiplexed: no
             |               ip timeout: 20
  --------------------------------------
  Properties |                      apn: timbrasil.br
             |                  roaming: allowed
             |                  ip type: ipv4v6
             |                     user: tim
             |                 password: tim
  --------------------------------------
  Statistics |                 attempts: 8
             |                 attempts: 8

tiago@dell-inspiron-15-3520:~$ sudo mmcli -m 1 -b 3
  --------------------------------------
  General    |                     path: /org/freedesktop/ModemManager1/Bearer/3
             |                     type: default
  --------------------------------------
  Status     |                connected: no
             |    connection error name: org.freedesktop.ModemManager1.Error.MobileEquipment.Unknown
             | connection error message: Unknown error
             |                suspended: no
             |              multiplexed: no
             |               ip timeout: 20
  --------------------------------------
  Properties |                      apn: timbrasil.br
             |                  roaming: allowed
             |                  ip type: ipv4
             |                     user: tim
             |                 password: tim
  --------------------------------------
  Statistics |                 attempts: 8
             |                 attempts: 8

tiago@dell-inspiron-15-3520:~$ sudo mmcli -m 1 -b 4
  --------------------------------------
  General    |                     path: /org/freedesktop/ModemManager1/Bearer/4
             |                     type: default
  --------------------------------------
  Status     |                connected: no
             |    connection error name: org.freedesktop.ModemManager1.Error.Core.Unsupported
             | connection error message: Only IPv4 is supported by this modem
             |                suspended: no
             |              multiplexed: no
             |               ip timeout: 20
  --------------------------------------
  Properties |                      apn: timbrasil.br
             |                  roaming: allowed
             |                  ip type: ipv6
             |                     user: tim
             |                 password: tim
  --------------------------------------
  Statistics |                 attempts: 8
             |                 attempts: 8

ModemManager Interface info is:

tiago@dell-inspiron-15-3520:~$ sudo mmcli -i 1
  -------------------------------
  General    |              path: /org/freedesktop/ModemManager1/SIM/1
  -------------------------------
  Properties |            active: yes
             |              imsi: XXXXXXXXXXXXXXX
             |             iccid: XXXXXXXXXXXXXXXXXXXXXX
             |       operator id: 72404
             |     operator name: TIM
             |              gid2: FFFFFFFFFFFFFFFFFF

The huawei-4g **NetworkManager connection** is configured as following:

tiago@dell-inspiron-15-3520:~$ sudo nmcli c show huawei-4g | cat
connection.id:                          huawei-4g
connection.uuid:                        0aa9ce26-96a3-49a8-a509-f48e56a3981e
connection.stable-id:                   --
connection.type:                        gsm
connection.interface-name:              cdc-wdm0
connection.autoconnect:                 yes
connection.autoconnect-priority:        0
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   1726645128
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
connection.dns-over-tls:                -1 (default)
connection.mptcp-flags:                 0x0 (default)
connection.wait-device-timeout:         -1
connection.wait-activation-delay:       -1
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.routing-rules:                     --
ipv4.replace-local-rule:                -1 (default)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-iaid:                         --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.dhcp-hostname-flags:               0x0 (none)
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.required-timeout:                  -1 (default)
ipv4.dad-timeout:                       -1 (default)
ipv4.dhcp-vendor-class-identifier:      --
ipv4.link-local:                        0 (default)
ipv4.dhcp-reject-servers:               --
ipv4.auto-route-ext-gw:                 -1 (default)
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       --
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.routing-rules:                     --
ipv6.replace-local-rule:                -1 (default)
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.required-timeout:                  -1 (default)
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.addr-gen-mode:                     default
ipv6.ra-timeout:                        0 (default)
ipv6.mtu:                               auto
ipv6.dhcp-duid:                         --
ipv6.dhcp-iaid:                         --
ipv6.dhcp-timeout:                      0 (default)
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.dhcp-hostname-flags:               0x0 (none)
ipv6.auto-route-ext-gw:                 -1 (default)
ipv6.token:                             --
gsm.auto-config:                        no
gsm.number:                             --
gsm.username:                           tim
gsm.password:                           
gsm.password-flags:                     0 (none)
gsm.apn:                                "timbrasil.br"
gsm.network-id:                         --
gsm.pin:                                
gsm.pin-flags:                          0 (none)
gsm.home-only:                          no
gsm.device-id:                          --
gsm.sim-id:                             --
gsm.sim-operator-id:                    --
gsm.mtu:                                auto
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --

When trying to connect to it, the following error is shown:

tiago@dell-inspiron-15-3520:~$ sudo nmcli c up huawei-4g
Error: Connection activation failed: Unknown error
Hint: use 'journalctl -xe NM_CONNECTION=0aa9ce26-96a3-49a8-a509-f48e56a3981e + NM_DEVICE=cdc-wdm0' to get more details.

The syslog shows the following:

set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6054] device (cdc-wdm0): Activation: starting connection 'huawei-4g' (0aa9ce26-96a3-49a8-a509-f48e56a3981e)
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6055] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6063] device (cdc-wdm0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6075] device (cdc-wdm0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6271] modem-broadband[cdc-wdm0]: failed to connect modem: Only IPv4 is supported by this modem
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6272] device (cdc-wdm0): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6278] device (cdc-wdm0): Activation: failed for connection 'huawei-4g'
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6280] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6286] device (cdc-wdm0): Activation: starting connection 'huawei-4g' (0aa9ce26-96a3-49a8-a509-f48e56a3981e)
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6287] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6290] device (cdc-wdm0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6297] device (cdc-wdm0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6469] modem-broadband[cdc-wdm0]: failed to connect modem: Only IPv4 is supported by this modem
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6469] device (cdc-wdm0): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6473] device (cdc-wdm0): Activation: failed for connection 'huawei-4g'
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6475] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6481] device (cdc-wdm0): Activation: starting connection 'huawei-4g' (0aa9ce26-96a3-49a8-a509-f48e56a3981e)
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6482] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6487] device (cdc-wdm0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6495] device (cdc-wdm0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6663] modem-broadband[cdc-wdm0]: failed to connect modem: Only IPv4 is supported by this modem
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6663] device (cdc-wdm0): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6665] device (cdc-wdm0): Activation: failed for connection 'huawei-4g'
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6666] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6669] device (cdc-wdm0): Activation: starting connection 'huawei-4g' (0aa9ce26-96a3-49a8-a509-f48e56a3981e)
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6670] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6673] device (cdc-wdm0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6681] device (cdc-wdm0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6845] modem-broadband[cdc-wdm0]: failed to connect modem: Only IPv4 is supported by this modem
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6846] device (cdc-wdm0): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6850] device (cdc-wdm0): Activation: failed for connection 'huawei-4g'
set 18 04:44:31 dell-inspiron-15-3520 NetworkManager:   [1726645471.6852] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Also, the modem sometimes opens a storage device in Debian with the windows .exe drivers. Apart from that the modem is still visible through modem manager and lsusb. Do anyone knows what is going on and how to make a GSM/cellular connection work in this Debian GNU/Linux?

I have set a VPN server (ubuntu) with a docker from the kyle/manna project. I want to establish two different VPN tunnels (VPN tunnel 1 and VPN tunnel 2) from another device (ubuntu) which owns two wireless connection (two LTE modems). Then the device which will have the VPN client will have two different interfaces called wwan0 and wwan1. How can I establish two different VPN tunnels? How can I send traffic via one VPN tunnel or the other? In other words, I want both tunnels to be connected to the same server via different interfaces at the same time. The reason is that each tunnel will send the traffic through different cellular networks. It could happen that pne cellular network does not work at a moment and the other one does. Then the traffic could be sent via the one working

Does anyone know of a Linux-compatible 4G/LTE modem (USB stick or otherwise) which allows setting a higher TX output power that the standard +23dbm?

How can I manage incoming and outgoing calls directly via a VoIP server with a compatible 5G/4G/3G stick? I want to use a SIM card that offers a flat rate for calls in Europe. The idea is to use it with multiple devices on Wi-Fi and via VPN with a VoIP client. I also want to share the Internet connection via the hotspot function (WLAN/USB). It's okay if the connection drops during a call. I have been looking for a solution for 2 years. Is there any hardware, e.g. an AVM Fritzbox, that redirects mobile calls from a 5G/4G stick to DECT? I haven't found anything suitable so far.

So, I am facing a problem with several Rpi units I have here. Most of the time they work fine, but after several days, the LTE modem (TELIT 910C1-LA) stops working with no reason. Luckily, I could reproduce the problem and saw what is happening before it: The system has booted I have a HTML page that exhibits the modem status LTE Modem had the status: "Connecting" LTE Modem has changed the status to "Disconnecting" LTE Modem has changed the status to blank I have connected trought SSH to the Rpi and run some commands to check what was happening: mmcli -L has returned "No modems were found" mmcli -m 0 has returned "couldn't find modem at " qmicli -d has returned the ICCID of the SIM Card It seems to me that the modem has dropped, then I have connected SSH again an checked the lsusb: It is possible to see that the "Telit Wireless Solution" is conencted on the USB Do you guys has any tips on that? I am kind of newbie to Linux OS, I know how to execute basic commands, but I am definetly not an advanced user. Thanks in advance! I did not tried anything, as I don't want the problem to go away before further analisys. This is an intermitent problem and I want to understand why it is happening and how can I fix it.

I have problem new USB LTE modem Brovi E3372-325 I can't get it to work on linux. When connected to a USB port, the modem identifies itself as:

# dmesg
...
[ 6731.401923] usb 1-3.4.4: new high-speed USB device number 22 using xhci_hcd
[ 6731.503252] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6731.503261] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6731.503265] usb 1-3.4.4: Product: Mobile
[ 6731.503268] usb 1-3.4.4: Manufacturer: Mobile
[ 6731.503271] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6731.505527] usb-storage 1-3.4.4:1.0: USB Mass Storage device detected
[ 6731.505830] scsi host1: usb-storage 1-3.4.4:1.0
[ 6732.534864] scsi 1:0:0:0: CD-ROM            Linux    File-Stor Gadget 0310 PQ: 0 ANSI: 2
[ 6732.535947] sr 1:0:0:0: Power-on or device reset occurred
[ 6732.536717] sr 1:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy
[ 6732.540429] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 6732.540983] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 6732.803382] ISO 9660 Extensions: RRIP_1991A

# lsusb -vvv
...
Bus 001 Device 028: ID 3566:2001 Mobile Mobile
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x3566 
  idProduct          0x2001 
  bcdDevice           ff.ff
  iManufacturer           2 Mobile
  iProduct                3 Mobile
  iSerial                 4 123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              1 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000000
      (Missing must-be-set LPM bit!)
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x0004
      Device can operate at High Speed (480Mbps)
    bFunctionalitySupport   4
      Lowest fully-functional device speed is at an unknown speed!
    bU1DevExitLat           1 micro seconds
    bU2DevExitLat         500 micro seconds
Device Status:     0x0000
  (Bus Powered)

now I switch them to "modem": usb_modeswitch -v 3566 -p 2001 -X:

# dmesg
...
[ 6971.308148] usb 1-3.4.4: USB disconnect, device number 22
[ 6971.544052] usb 1-3.4.4: new high-speed USB device number 23 using xhci_hcd
[ 6971.645772] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6971.645787] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6971.645794] usb 1-3.4.4: Product: Mobile
[ 6971.645799] usb 1-3.4.4: Manufacturer: Mobile
[ 6971.645804] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6971.647121] usb 1-3.4.4: Interface #0 referenced by multiple IADs
[ 6971.647643] usb 1-3.4.4: Interface #1 referenced by multiple IADs
[ 6971.678702] cdc_ncm 1-3.4.4:1.5: MAC-Address: c2:ab:11:ee:2f:15
[ 6971.679449] cdc_ncm 1-3.4.4:1.5 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3.4.4, CDC NCM, c2:ab:11:ee:2f:15
[ 6971.743416] cdc_ncm 1-3.4.4:1.5 enxc2ab11ee2f15: renamed from usb0

# ip a s enxc2ab11ee2f15
14: enxc2ab11ee2f15:  mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether c2:ab:11:ee:2f:15 brd ff:ff:ff:ff:ff:ff

# mmcli -L
No modems were found

# lsusb -vvv
Bus 001 Device 029: ID 3566:2001 Mobile Mobile
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x3566 
  idProduct          0x2001 
  bcdDevice           ff.ff
  iManufacturer           2 Mobile
  iProduct                3 Mobile
  iSerial                 4 123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x00f9
    bNumInterfaces          7
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction              10 CDC Serial
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              8 CDC Abstract Control Model (ACM)
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 01
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 00 01
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              9 CDC ACM Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             11 Marvell DIAG
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         3
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction              14 CDC Serial
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             12 CDC Abstract Control Model (ACM)
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 04
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 03 04
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             13 CDC ACM Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass      13 
      bFunctionProtocol       0 
      iFunction               0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass     13 
      bInterfaceProtocol      0 
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        5
        bSlaveInterface         6 
      CDC Ethernet:
        iMacAddress                     17 FE1EA1E4D9D7

        bmEthernetStatistics    0x00000000
        wMaxSegmentSize               1514
        wNumberMCFilters            0x0000
        bNumberPowerFilters              0
      CDC NCM:
        bcdNcmVersion        1.00
        bmNetworkCapabilities 0x01
          packet filter
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      1 
      iInterface              0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      1 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000000
      (Missing must-be-set LPM bit!)
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x0004
      Device can operate at High Speed (480Mbps)
    bFunctionalitySupport   4
      Lowest fully-functional device speed is at an unknown speed!
    bU1DevExitLat           1 micro seconds
    bU2DevExitLat         500 micro seconds
Device Status:     0x0000
  (Bus Powered)

But there is missing /dev interface (something like /dev/cdc*//dev/ttyUSB*). Tested on Ubuntu 22.04 with kernel 5.15 and Ubuntu 23.04 (daily build) with kernel 5.19. Without success. I tried dhclient enxc2ab11ee2f15, ip link enxc2ab11ee2f15 up - without success. For qmicli/mbimcli there is missing /dev/cdc* interface. On Windows 10 PC it connects automatically and gets IP from DHCP. It uses RNDIS driver. Can you please help me? How can I switch modem to the right mode?

I have a Thinkpad T590 that I dual-boot Windows and Linux on. I installed an OEM Fibocom L850-GL WWAN card in the laptop, and after driver installation it works perfectly in Windows. However, after trying to set it up in my Fedora 37 Workstation installation I discovered that there was no official driver, and the card was only officially supported in USB mode. I tried to install the unofficial PCIe driver found [here,](https://github.com/xmm7360/xmm7360-pci) but was presented with the following error message, even after reboots:

(most recent call last):
  File "/home/quowlord/Downloads/xmm7360-pci-master/scripts/../rpc/open_xdatachannel.py", line 42, in 
    r = rpc.XMMRPC()
        ^^^^^^^^^^^^
  File "/home/quowlord/Downloads/xmm7360-pci-master/rpc/rpc.py", line 19, in __init__
    self.fp = os.open(path, os.O_RDWR | os.O_SYNC)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/dev/xmm0/rpc'
RTNETLINK answers: No such device

the output of

/dev

is:

cpu_dma_latency  fd         kmsg          mcelog  nvme0n1    ppp            sgx_vepc  tty    tty16  tty24  tty32  tty40  tty49  tty57  tty8    ttyS15  ttyS23  ttyS31   uinput       vcs    vcsa2  vcsu4        video1
autofs            cuse             full       kvm           media0  nvme0n1p1  ptmx           shm       tty0   tty17  tty25  tty33  tty41  tty5   tty58  tty9    ttyS16  ttyS24  ttyS4    urandom      vcs1   vcsa3  vcsu5        watchdog
block             disk             fuse       log           mei0    nvme0n1p2  ptp0           snapshot  tty1   tty18  tty26  tty34  tty42  tty50  tty59  ttyS0   ttyS17  ttyS25  ttyS5    usbmon0      vcs2   vcsa4  vcsu6        watchdog0
btrfs-control     dma_heap         gpiochip0  loop-control  mem     nvme0n1p3  pts            snd       tty10  tty19  tty27  tty35  tty43  tty51  tty6   ttyS1   ttyS18  ttyS26  ttyS6    usbmon1      vcs3   vcsa5  vfio         wwan0at0
bus               dri              hpet       lp0           mqueue  nvme0n1p4  random         stderr    tty11  tty2   tty28  tty36  tty44  tty52  tty60  ttyS10  ttyS19  ttyS27  ttyS7    usbmon2      vcs4   vcsa6  vga_arbiter  wwan0at1
char              drm_dp_aux0      hugepages  lp1           net     nvme0n1p5  rfkill         stdin     tty12  tty20  tty29  tty37  tty45  tty53  tty61  ttyS11  ttyS2   ttyS28  ttyS8    usbmon3      vcs5   vcsu   vhci         zero
console           drm_dp_aux1      hwrng      lp2           ng0n1   nvme0n1p6  rtc            stdout    tty13  tty21  tty3   tty38  tty46  tty54  tty62  ttyS12  ttyS20  ttyS29  ttyS9    usbmon4      vcs6   vcsu1  vhost-net    zram0
core              drm_dp_aux2      initctl    lp3           null    nvram      rtc0           tpm0      tty14  tty22  tty30  tty39  tty47  tty55  tty63  ttyS13  ttyS21  ttyS3   udmabuf  userfaultfd  vcsa   vcsu2  vhost-vsock
cpu               fb0              input      mapper        nvme0   port       sgx_provision  tpmrm0    tty15  tty23  tty31  tty4   tty48  tty56  tty7   ttyS14  ttyS22  ttyS30  uhid     v4l          vcsa1  vcsu3  video0

with no apparent device of the name mentioned in the error. Since the card works on Windows, it can be assumed it's installed correctly on a hardware level. Do you know where the device is/why it's not showing up in

/dev

?

I have two 4G modems connecting to a network and sending and receiving data. There is a problem though, as the modems keep getting kicked off the network because the source IP address of the packets is incorrect. It seems that packets that originate from datacard 1 have the source IP address of datacard 2. The mobile network checks the source IP address of the packet against the IP address of the connected modem, sees there is a mismatch and kicks that modem off the network. I need to rectify this problem and have both modems send IP packets with the correct source IP address. However, I'm very inexperienced in this kind of thing, and I would very much appreciate some advice for starting points. I believe that the IP tables and IP route have been checked and that hasn't resolved this problem.

Is anyone aware of a LPAd for Linux devices, both Android and Windows support this as of currently. I have searched the internet and was unable to find any information about if / or an eSIM LPAd will ever be supported on Linux. Maybe someone is aware of a program capable of this which can run on Linux? Or maybe someone here has successfully implemented an eSIM in a Linux environment? https://source.android.com/devices/tech/connect/esim-overview https://support.microsoft.com/en-us/windows/use-an-esim-to-get-a-cellular-data-connection-on-your-windows-pc-0e255714-f8be-b9ef-9e84-f75b05ed98a3 Thank you!

I have an LTE Surf Stick which I would like to get working inside my virtual machine. The Stick is called "ZTE MF 823". I am running openSUSE 13.1 with NetworkManager and I was not able to find any device that matches a hard drive or a modem. Because this stick got also a hard drive for installing the Windows software. Within Windows, it is running as integrated webserver, which I can access with my browser. But this should also work under Linux, because the hardware access driver should be the same. My virtualizer is Virtual Box. I also configured the USB forwarding in Virtual Box. However, when I type lsusb on openSUSE I get the following output: Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub I struggled with the vendor id's of the first entry of lsusb but I can't get it working.

We have our own yocto image on IMX8 device (NXP). The device internet is served by simcon EU 4G modem and IOT sim (Monogoto). The connection id created with libqmi and created wwan0 successfully. - the sshd recipe was left untouched (expcet for preventing root logins) - the ssh access to the device is on demand, when requested ngrok forwards TCP port 22 and on ngrok site i can see my URI to connect to. When trying to connect i'm successfull. However when i try to use commands with large output like dmesg or copy paste large test files to vi the terminal hangs and connection shuts down. If i connect using ngrok to a regular PC the connections remains open just fine. I thought it might be the modem. So i connected to my ubuntu using a USB similar modem (EC25e - same SIM provder though) the ssh connection was ok. Tried to compare and change the sshd_config settings but all the settings that were different between my laptop version and the Compulab (NXP) and were changed did not seem to help. Any idea as for why the disconnection ? Any lead ? Thanks.

I want to setup an LTE connection via nmcli which auto connects at startup. My current configuration looks like this:

# mmcli -m 0
  --------------------------------
  General  |            dbus path: /org/freedesktop/ModemManager1/Modem/0
           |            device id: ****
  --------------------------------
  Hardware |         manufacturer: Sierra Wireless, Incorporated
           |                model: ****
           |             revision: ****
           |            supported: gsm-umts, lte
           |              current: gsm-umts, lte
           |         equipment id: ****
  --------------------------------
  System   |               device: /sys/devices/3530000.xhci/usb1/1-3/1-3.2
           |              drivers: GobiSerial driver, GobiNet
           |               plugin: Generic
           |         primary port: ttyUSB2
           |                ports: ttyUSB0 (qcdm), eth2 (net), eth3 (net), ttyUSB2 (at)
  --------------------------------
  Numbers  |                  own: ****
  --------------------------------
  Status   |       unlock retries: sim-pin (3), sim-puk (10)
           |                state: connected
           |          power state: on
           |          access tech: lte
           |       signal quality: 0% (recent)
  --------------------------------
  Modes    |            supported: allowed: 2g, 3g, 4g; preferred: none
           |              current: allowed: 2g, 3g, 4g; preferred: none
  --------------------------------
  IP       |            supported: ipv4, ipv6, ipv4v6
  --------------------------------
  3GPP     |                 imei: ****
           |          operator id: ****
           |        operator name: ****
           |         registration: home
  --------------------------------
  3GPP EPS | ue mode of operation: csps-2
  --------------------------------
  SIM      |            dbus path: /org/freedesktop/ModemManager1/SIM/0
  --------------------------------
  Bearer   |            dbus path: /org/freedesktop/ModemManager1/Bearer/1
           |                       /org/freedesktop/ModemManager1/Bearer/0

and

# nmcli c show LTE
connection.id:                          LTE
connection.uuid:                        ****
connection.stable-id:                   --
connection.type:                        gsm
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        0
connection.autoconnect-retries:         -1 (default)
connection.auth-retries:                -1
connection.timestamp:                   1606296274
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       ""
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --                          
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.dad-timeout:                       -1 (default)
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       ""
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.token:                             --
gsm.number:                             *99#
gsm.username:                           --
gsm.password:                           
gsm.password-flags:                     0 (none)
gsm.apn:                                --
gsm.network-id:                         --
gsm.pin:                                
gsm.pin-flags:                          0 (none)
gsm.home-only:                          no
gsm.device-id:                          --
gsm.sim-id:                             --
gsm.sim-operator-id:                    --
gsm.mtu:                                auto
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --
GENERAL.NAME:                           LTE
GENERAL.UUID:                           ****
GENERAL.DEVICES:                        ttyUSB2
GENERAL.STATE:                          activated
GENERAL.DEFAULT:                        yes
GENERAL.DEFAULT6:                       no
GENERAL.SPEC-OBJECT:                    --
GENERAL.VPN:                            no
GENERAL.DBUS-PATH:                      /org/freedesktop/NetworkManager/ActiveConnection/4
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/Settings/1
GENERAL.ZONE:                           --
GENERAL.MASTER-PATH:                    --
IP4.ADDRESS:                         ****
IP4.GATEWAY:                            ****
IP4.ROUTE:                           ***
IP4.ROUTE:                           ****
IP4.DNS:                             ****
IP4.DNS:                             ****

With this configuration basically everything works fine, as long I do have a connection at the startup of my Linux device. If I do not have a connection, mmcli -m 0 will correctly notice that there is no connection, in which it connects as soon as there is a connection available. On the other hand nmcli c show LTE will stuck with the state GENERAL.STATE: activating no matter if there already is a LTE connection or not. Setting the nmcli connection down and up, will make nmcli connect correctly. How can I make nmcli connect as soon as the LTE connection is there without having to set the connection down and up?

During the past 6 days, I had the chance to interact with an LTE modem (https://sixfab.com/product/quectel-ec25-mini-pcle-4glte-module/) , I managed to set up 4G Internet access on a Raspberry Pi using "QMI". But I still have A LOT of questions, I read many tutorials, articles and even articles from books but I'm still confused, I hope you have time to clarify things for me and for future readers: - How do PPP, AT commands and QMI interact with each other and with LTE? - What is the role of each of them? Do we need them all? - Can you explain what happens (in details) when establishing a connection or rec/send data from the internet using these protocols? schemas will be great. - I understand that PPP is used to connect the modem to the ISP, why do people say that it should be replaced by QMI? - In this response https://unix.stackexchange.com/a/168690 we recommend using the wwan0 interface over tty for more speed, but all data shares the same only USB connection, right? - if the max serial speed is 115200 bps, how do modems reach 150Mbps ? do they have buffers? - According to https://www.quectel.com/UploadImage/Downlad/Quectel_WCDMA<E_Linux_USB_Driver_User_Guide_V1.8.pdf (page 8/47) the model provides many interfaces and they say that wwan* interface can be used as USB network adapter, what is the difference between wwan* and /dev/ttyUSB* ? - Can you suggest some articles or books about that?

I have a 4G module that requires me to run echo '03f0 581d' > /sys/bus/usb-serial/drivers/generic/new_id after every startup/resume to make the modem visible. How should I make this automatic? - Add the VID&PID to usb-serial sources and recompile - Create script that run on startup/resume that adds them dynamically - Some sort of udev rule? What would be the best approach. I think the udev approach sounds the most reasonable. I assume that would work over suspend/resume too? The modem is a HP lt4112 LTE/HSPA+ Gobi 4G Modem (Huawei ME906E). Bonus question: Why does the command need to be re-run after a suspend/resume cycle. Does the kernel module get unloaded or somehow reset when the laptop gets suspended to RAM?

I'm by no means an experienced person in this regard. ### Context, if you find it helpful We are developing an IoT solution for telemetry purposes. The device that retrieve the data to send it to the cloud is a custom Debian (9) gateway developed by the same company that provide us the software that help us achieve this kind of things (Moxa). My problem is that I can't connect it to the internet through the cellular (LTE), so this is the reason I can't install libraries in the device (like the Google Cloud SDK). ## Situation The device has the following interfaces: $ sudo ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:90:e8:7c:e0:2e brd ff:ff:ff:ff:ff:ff inet 192.168.3.127/24 brd 192.168.3.255 scope global eth0 valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:90:e8:7c:e0:2f brd ff:ff:ff:ff:ff:ff inet 192.168.4.127/24 brd 192.168.4.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::290:e8ff:fe7c:e02f/64 scope link valid_lft forever preferred_lft forever 21: usb0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether c6:d4:e8:d9:64:3e brd ff:ff:ff:ff:ff:ff inet 10.127.34.103/32 scope global usb0 valid_lft forever preferred_lft forever inet6 fe80::c4d4:e8ff:fed9:643e/64 scope link valid_lft forever preferred_lft forever According to the docs, the eth0 is for WAN and eth1 for LAN purposes. This is the content of my /etc/network/interfaces file: $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 eth1 lo iface lo inet loopback iface eth0 inet static address 192.168.3.127 network 192.168.3.0 netmask 255.255.255.0 broadcast 192.168.3.255 iface eth1 inet static address 192.168.4.127 network 192.168.4.0 netmask 255.255.255.0 broadcast 192.168.4.255 And this is the content of the /etc/resolv.conf. Those values are the DNS of the carrier (Movistar Peru): $ cat /etc/resolv.conf nameserver 200.48.225.130 nameserver 200.48.225.146 By the way, I've already set up the correct APN so the SIM should work (I did it through the admin panel of the gateway). This are the results of ping: $ ping 8.8.8.8 connect: Network is unreachable $ ping google.com ping: google.com: Temporary failure in name resolution Of course there might be errors in this config. What am I doing wrong? Thanks in advance. ---- # Update As requested, this is what the ip r/ip route returned: $ ip r 192.168.3.0/24 dev eth0 proto kernel scope link src 192.168.3.127 linkdown 192.168.4.0/24 dev eth1 proto kernel scope link src 192.168.4.127 Also, this is what the manual states regarding the ethernet interfaces: > The ETH0 Ethernet interface is used for the WAN and the ETH1 > interface is used for the LAN. The default IP addresses are: > > eth0=192.168.3.127 > eth1=192.168.4.127 And: > Interfaces of your eligible device could include: > > - tun0: VPN Tunnel // not using this > > - wlan0: Wi-Fi // Our required device doesn't include this module > > - wwan0: Cellular // > - eth0: Ethernet (usually LAN1 when the default setting is WAN). A diagram that might help:

I currently have a gnome menu that looks like this: Can anyone tell me how I can remove the 3/4G mobile networks? I have an inbuilt mobile network device, which I've never used and would rather not see and recently the other 2 devices have appeared.They may have been plugged in to my laptop at some point. I've checked and they don't appear in

/etc/NetworkManager

, and I don't see any config or extension that can help me remove them. They do appear in the NetworkManager applet, but the remove button is greyed out.

I want to automate some command the thing is we login to the server and the next commandline isn't a linux commandline but rather that of an application it self. My current attempt of solution is the following. #!/bin/bash # smsme.sh i=0 i=$((i+1)) rancli sleep 3 echo add saf dest=4949 orig=Wim text=$i sleep 120; # --- Quick hint it breaks on add. I tried piping the commands as well it just echoed in the linux enverimont without ever hitting the rancli Updated scripts after update #!/bin/bash # smsme.sh i=0 i=$((i+1)) rancli read $reply Answer script #!/usr/bin/env expect set timeout -1 spawn ./smsme.sh expect { "Quortus Core CLI (c) 2019 No entry for terminal type "xterm-256color"; using dumb terminal settings. Connecting to RAN at 127.0.0.1:3012QCore> LTE64b>" } eof } send -- add saf dest=4949 orig=Wim text=wim expect "Submitted, message number $1" expect eof

I have a Linux-based OS (Rasbian) running on Raspberry Pi 2+ and it is using **Huawei E3372s** 4G/LTE USB Stick for internet connection. All my outbound connections work perfectly (Huawei USB mode changed using usb_modeswitch-ruling and Udev/rules.d) but I am unable to receive any kind of inbound connection to the Raspi. **Incoming is just not working**. I **cannot receive** any packets or connections, which I have tracked realtime and from logs using tools provided by Raspbian package distributions. I have already confirmed with my 4G ISP that the extended service which allows two-way traffic is enabled, reseted and so much of their knowledge, to my 3G/4G subscription, working perfectly from their end but I am unable to receive any packets with the Raspi. **Huawei E3372s** (unlike most of the older sticks which use dialing like wvdial) uses **CDC_ETH** driver system which creates an ethernet-like device to the system (ETH1 in this case) and should work in this case flawlessly. I have cleared, re-created, tested, modified, re-cleared and again done all needed tasks with IPTables, checked, modified and tested Route several times as well as confirmed that there are no known blocking systems preventing connection through Huawei USB-stick, yet I still cannot receive even Ping to my system, although there are fully functional services running. I have also checked more simple and straightforward areas such as hosts allow/deny rules and have had no luck with them. It is not APN name either as all settings with the Huawei's internal configuration have been set correctly using it's web interface. I have, however, encountered on few occasion from random forums, that Huawei CDC_ETH solution may have flaws handling incoming connections with its driver. If any of you have experience with Debian/Rasbian/Linux incoming connection problems with **Huawei E3372s** or relative 3G/4G USB product which use **CDC_ETH** and have found solution to this problem