When I am using raspbian with a 4g USB modem, sometimes the network goes down and there is no option to bring back the network unless I reboot the raspbian. In such cases, I try: service networking restart with a cron every hour; this doesn't work. I tried also ifdown -a && ifup -a -- not much better. The thing is, when I execute these commands in a terminal, I get no output. What is the solution to bring network as if I rebooted? root@raspberrypi:/home/pi# ifconfig -a eth0: flags=4163 mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::48f5:e07c:1544:2d24 prefixlen 64 scopeid 0x20 ether b8:27:eb:38:6e:29 txqueuelen 1000 (Ethernet) RX packets 23902 bytes 8949877 (8.5 MiB) RX errors 0 dropped 17 overruns 0 frame 0 TX packets 30039 bytes 6388288 (6.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Boucle locale) RX packets 20996 bytes 8495857 (8.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20996 bytes 8495857 (8.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099 mtu 1500 ether b8:27:eb:6d:3b:7c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

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 an ERRCISON F5521gw internal 3G modem which I have been using for years with many versions of Ubuntu, but since I have installed Ubuntu Mate 22.04 it stopped working. Here is output of lsusb showing that the hardware detected on the usb bus: Bus 001 Device 003: ID 0bdb:190d Ericsson Business Mobile Networks BV F5521gw but there is no broadband connection available in network manager and I can't find any /dev file for this device. Does anyone have the same experience and get it to work?

After configuring Raspbian linux and a Huawei E303 3G USB stick, I am stuck accessing the machine from the Internet by its public IP address. Details: The E303 stick was configured to work as an Ethernet device (mode switch worked OK). Linux creates an *eth1* device for it and receives an ip address via DHCP from the E303 after adding the device to */etc/network/interfaces*. After setting it as the default route, all access from the machine to the Internet works fine - *route add default gw 192.168.8.1*. The IP address *eth1* receives is 192.168.8.100 - or, if I use a different sub-model of the E303, it is 192.168.1.100. I can tell that the E303 devices are slightly different, because - after mode switching - one of them holds the USB product id 0x014db, the other 0x014dc. Besides the assigned subnets they are not distinct. Both sticks run a web server and may be accessed without problems, however, there are no configuration option on their network behaviour. They show their own IP address as from the 10.34.X.X subnet (from the device information web page). Then I registered a dynamic IP address (with no-ip.com) and installed the respective software package. My public IP address is properly registered with no-ip.com (when looking at the hosts listing on their web site) and ping displays the correct, public IP address of my machine. Both, when pinging from the Raspbian and from a different machine in a separate network. Btw, when using the *ddclient* package, instead, I see the exact same result. When not using the 3G stick, but plugging in the on-board Ethernet, the machine may be ping'ed, ssh'ed from the local network without problems, and I can get web pages served as well. My assumptions are that the configuration of the E303 device, routing out, and the dynamic IP address registration are basically OK. But I have no clue how to make the machine visible to the Internet. All connections from the outside time out. The Huawei 3G stick and the telephone provider infrastructure seem to act as intermediate network devices applying NAT without port forwarding to my machine.

I have to develop an application on embedded Linux which sends data over Internet. I have to choose a USB 3G modem with a SIM card holder, which works successfully or is supported on embedded Linux.

In FreeBSD GUI is not installed by default and I have to install it manually. In order to install the GUI I need the Internet and I have only 3g-usb-modem Huawei E171. I don`t know how to connect to the internet via 3g-usb-modem in terminal FreeBSD.

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'm trying to use a 3G USB modem on a Rapsbian RPi and all goes well, except for some reason the PPP disconnects with exit code 16. I have debug mode enabled, but it doesn't say nothing, except that authentication is successful. Please see details below: WvDial: Internet dialer version 1.61 Initializing modem. Sending: ATZ ATZ OK Sending: AT+CPIN=XXXX AT+CPIN=XXXX OK Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK Sending: AT+CGDCONT=1,"IP","internet" AT+CGDCONT=1,"IP","internet" OK Modem initialized. Sending: ATD*99# Waiting for carrier. ATD*99# CONNECT 3600000 Carrier detected. Starting PPP immediately. Starting pppd at Sun Dec 7 22:23:20 2014 Pid of pppd: 2967 pppd: 8�fP�fh�f��f؉f0�f Using interface ppp0 pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f Authentication (CHAP) started pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f Authentication (CHAP) successful pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f pppd: 8�fP�fh�f��f؉f0�f Disconnecting at Sun Dec 7 22:23:24 2014 The PPP daemon has died: A modem hung up the phone (exit code = 16) man pppd explains pppd error codes in more detail. Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. Auto Reconnect will be attempted in 5 seconds The /var/log/messages shows: Dec 7 22:58:45 raspberrypi pppd: pppd 2.4.5 started by root, uid 0 Dec 7 22:58:45 raspberrypi pppd: Using interface ppp0 Dec 7 22:58:45 raspberrypi pppd: Connect: ppp0 /dev/ttyUSB2 Dec 7 22:58:45 raspberrypi pppd: CHAP authentication succeeded Dec 7 22:58:45 raspberrypi pppd: CHAP authentication succeeded Dec 7 22:58:48 raspberrypi pppd: Modem hangup Dec 7 22:58:48 raspberrypi pppd: Connection terminated. Dec 7 22:58:48 raspberrypi pppd: Exit.

I'm using Gentoo, and I have a problem with the 3g modem Huawei E8231. As far as I understand, to make it work I should switch its mode: $ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:07dc Intel Corp. Bus 001 Device 004: ID 0bda:572a Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 011: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass storage mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb_modeswitch -v 12d1 -V 12d1 -p 1f01 -P 14db -M "55534243123456780000000000000011062000000101000100000000000000" $ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:07dc Intel Corp. Bus 001 Device 004: ID 0bda:572a Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 012: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # dmesg [19469.255798] usb 1-3: new high-speed USB device number 11 using xhci_hcd [19469.396894] usb 1-3: New USB device found, idVendor=12d1, idProduct=1f01 [19469.396898] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [19469.396900] usb 1-3: Product: HUAWEI Mobile [19469.396901] usb 1-3: Manufacturer: HUAWEI [19469.396903] usb 1-3: SerialNumber: FFFFFFFFFFFFFFFF [19469.397809] usb-storage 1-3:1.0: USB Mass Storage device detected [19469.397868] scsi host5: usb-storage 1-3:1.0 [19470.397691] scsi 5:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [19470.470961] sr 5:0:0:0: [sr0] scsi-1 drive [19470.471189] sr 5:0:0:0: Attached scsi CD-ROM sr0 [19470.471320] sr 5:0:0:0: Attached scsi generic sg1 type 5 [19591.778652] usb 1-3: USB disconnect, device number 11 [19592.095020] usb 1-3: new high-speed USB device number 12 using xhci_hcd [19592.238652] usb 1-3: New USB device found, idVendor=12d1, idProduct=14db [19592.238655] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [19592.238658] usb 1-3: Product: HUAWEI Mobile [19592.238659] usb 1-3: Manufacturer: HUAWEI [19592.311677] cdc_ether 1-3:1.0 eth1: register 'cdc_ether' at usb-0000:00:14.0-3, CDC Ethernet Device, 00:1e:10:1f:00:00 # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 12 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=12d1 ProdID=14db Rev=01.02 S: Manufacturer=HUAWEI S: Product=HUAWEI Mobile C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_ether I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether It seems that everything is ok, but there aren't any new devices or interfaces: $ ls /dev | grep ttyUSB #empty result $ ifconfig #no usb0 eth0: flags=4099 mtu 1500 ether c4:54:44:b2:ca:45 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 0 (Local Loopback) RX packets 9445 bytes 5167034 (4.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 9445 bytes 5167034 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163 mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::fa16:54ff:fe6e:2940 prefixlen 64 scopeid 0x20 ether f8:16:54:6e:29:40 txqueuelen 1000 (Ethernet) RX packets 875123 bytes 1243972975 (1.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 391840 bytes 42394343 (40.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Wat's wrong? *note: I also asked this question on gentoo forum *

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

I have LTE USB modem identified as ID 0408:ea16 Quanta. It doesn't have problem with my windows machine, but with my Fedora (kernel 3.18.5-201) it is not working. I've found some [info](http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1729&view=unread) in the Internet, but those didn't work. I can't see it in NetworkManager (as output of nmcli dev command). What could be done?

If I connect two usb wireless adaptors (via a usb hub), only one of them gets assigned an ip address. I want each to be assigned a different ip address to be able to use both wireless adapters at the same time, each from a separate network namespace. The two devices have the same mac address and I think this is the reason. When the two usb adapters are different models (which have different mac addresses), they both get different ip addesses assigned automatically. output of 'ip a': 48: eth1: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff inet 192.168.8.100/24 brd 192.168.8.255 scope global dynamic noprefixroute eth1 valid_lft 86384sec preferred_lft 86384sec inet6 fe80::640:311a:de17:1163/64 scope link noprefixroute valid_lft forever preferred_lft forever 49: eth2: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff UPDATE: I changed the MacAddressPolicy as suggested which successfully gives a random mac address to each of these devices, meaning that now when two of these devices are connected, they have different mac addresses. However, the ip address still only gets assigned to one of them: 59: eth1: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether fe:ef:a8:28:41:df brd ff:ff:ff:ff:ff:ff inet 192.168.8.100/24 brd 192.168.8.255 scope global dynamic noprefixroute eth1 valid_lft 86393sec preferred_lft 86393sec inet6 fe80::640:311a:de17:1163/64 scope link noprefixroute valid_lft forever preferred_lft forever 60: eth2: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ca:9e:d4:c1:61:b9 brd ff:ff:ff:ff:ff:ff Is there a way to get an ip address assigned to both? (I can't give it a static ip because the internet doesnt work if I do that.) Is this happening because both devices are telling the OS that it's ip is 192.168.8.100 and they can't both use the same ip? Or could it have anything to do with the fact that the mac address was assigned on the OS but the devices still have the same mac address on their chips?

Can somebody explain me the meaning of this output of iptables command in Android running 3g connection? I forgot Chain INPUT Chain INPUT (policy ACCEPT 1522 packets, 486K bytes) pkts bytes target prot opt in out source destination 9579 2150K bw_INPUT all -- any any anywhere anywhere 9579 2150K firewall all -- any any anywhere anywhere 9579 2150K fw_INPUT all -- any any anywhere anywhere

I am having difficulty establishing SSH connection from outside to Raspberry Pi that has USB 4G modem as interface. I get timeout when trying to connect with ssh: ssh -l pi ccc.ccc.ccc.ccc -p 22 ssh_exchange_identification: read: Operation timed out Interface is obviously ppp0 and has correct IP address that can be pinged from outside. This is the ifconfig listing (ip address obfuscated) ppp0: flags=4305 mtu 1500 inet ccc.ccc.ccc.ccc netmask 255.255.255.255 destination 10.64.64.64 ppp txqueuelen 3 (Point-to-Point Protocol) RX packets 401 bytes 377702 (368.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 336 bytes 27694 (27.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ping from an other machine works OK, ssh does not and gets timeout. Monitoring the interface with tcpdumps shows some life when connected with ssh client sudo tcpdump -i ppp0 port 22 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 09:18:26.764806 IP yyy.yyy.yyy.yyy.53681 > ccc.ccc.ccc.ccc.ssh: Flags [S], seq 2675400197, win 65535, options [mss 1386,nop,wscale 5,nop,nop,TS val 672664602 ecr 0,sackOK,eol], length 0 after that there is no life, no logs in /var/log/auth or messages, nothing. sshd log level is set to DEBUG3 This is the SSHD conf file: Port 22 Port 7654 AddressFamily any ListenAddress 0.0.0.0 #ListenAddress :: # Ciphers and keying #RekeyLimit default none # Logging SyslogFacility AUTH LogLevel DEBUG3 I tried to add some obscure port 7654 in case 22 was blocked by ISP or something I tried to add specific firewall rules even though general policy is set to ACCEPT: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ctstate NEW,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:7654 ctstate NEW,ESTABLISHED Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp spt:ssh ctstate ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp spt:7654 ctstate ESTABLISHED route table looks like this: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.64.64.64 0.0.0.0 UG 0 0 0 ppp0 10.64.64.64 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 bbb.bbb.bbb.0 0.0.0.0 255.255.252.0 U 202 0 0 eth0 where that bbb thing is local ethernet network No luck, and I still get timeout when trying to connect. SSH from localhost to that IP address works ok. Any ideas where this is going wrong and how to fix it? It puzzles me that I get at least ICMP messages to the interface and internally SSH also works. Even externally there is some life in that interface when connecting from outside with ssh, but it still doesn't work.

In order to install the GUI in OpenBSD! I know how to connect to wifi but now I have only 3g-usb-modem Huawei E171 and I don`t know how to connect to the internet via 3g-usb-modem in OpenBSD ! How can I solve it ? Please help me !

OpenWrt Chaos Calmer 15.05.1. USB dongle ZTE MF190. I executed some installation commands from this tutorial. Now dmesg | grep usb shows me the following: [ 4.150000] usbcore: registered new interface driver usbfs [ 4.160000] usbcore: registered new interface driver hub [ 4.160000] usbcore: registered new device driver usb [ 4.560000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 12.520000] usbcore: registered new interface driver usbserial [ 12.530000] usbcore: registered new interface driver usbserial_generic [ 12.530000] usbserial: USB Serial support registered for generic [ 12.800000] usbcore: registered new interface driver option [ 12.800000] usbserial: USB Serial support registered for GSM modem (1-port) As I understand, the modem is detected by OS and corresponding kernel module was loaded. But! There is no '/dev/ttyUSBX' devices. How to obtain the device file?

I'm trying to get a Huawei E398 3G USB modem to work on my Raspberry Pi 3 When I run wvdial I get the following response: pi@mypi:~ $ sudo wvdial --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ERROR --> Bad init string. This is my wvdial.conf: pi@mypi:~ $ cat /etc/wvdial.conf [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = USB Modem ISDN = 0 New PPPD = yes Stupid Mode = yes Modem = /dev/ttyUSB0 Phone = *99# Username = internet Password = internet Baud = 115200 Anyone have any clue on what could cause this? I've tried every other init string I could come across, but every single one gives me the same error.

I'm trying to set up a Huawei E3276 LTE stick with German Telekom and Modem Manager on Raspberry Pi (latest Raspbian), and basically it works but I'm failing to create a configuration that is deployable to the RPi via ansible. When I connect the LTE stick, ModemManager sets everything up correctly and I end with a wwan0 interface and a 169.254.0.0/16 address assigned to it. Afterwards, I always have to run sudo mmcli -m 0 --simple-connect="apn=internet.t-d1.de,user=t-mobile,password=tm,number=*99#" which triggers network manager to get me somehow an IP. Everything's fine. Since I want to automate this, I want to get rid of manually executing the mmcli command but am currently failing. - Option 1: cronjob and script - ugly but most likely to work. I want to avoid this - Option 2: Configuration file for modem manager / mmcli. I did not find any configuration file where I can place this data - Option 3: udev rule executing the command pi@raspberrypi:~ $ cat /etc/udev/rules.d/90-lte.rules ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="0c:5b:8f:27:9a:64", RUN+="/usr/local/bin/lte_setup.sh" pi@raspberrypi:~ $ cat /usr/local/bin/lte_setup.sh #!/bin/sh sleep 2 mmcli -m 0 --simple-connect='apn=internet.t-d1.de,user=t-mobile,password=tm,number=*99#' This doesn't work and I don't actually know why. So, the basic question: _What is the simplest way to deploy this configuration/scripts via ansible to the Raspberry Pi in order to just get a public IP automatically via Modem-/NetworkManager after pluging the E3276 in?_ One last thing: I am **not** searching for a solution using wvdial or other tools. I spent days trying to use them using "working" configurations from the Internet just to find out they are not working. ModemManager and NetworkManager have proven to work, so I'm just trying to complete the setup without building the ugly cronjob workaround.

I am developing a Debian 8 (Jessie) based system for an embedded solution, using multistrap to build a rootfs. The system is headless, and can be accessed via a serial console meant for debugging and via SSH. I am having a problem with ModemManager in this system. It installs with no problems, but once I have it enabled and it actually starts up, it usually (not always but generally) starts flooding the debug console. The output is usually just meaningless stream of characters, but sometimes there are various AT-commands too. I know this flooding is caused by ModemManager because it can ceases once I remove ModemManager. I could live with some random flooding, but the problem is that this flooding almost always somehow makes the console non-responsive and that way prevents me from logging in. Sometimes, though very rarely, I have been able to log in despite of this flooding, check the IP of device and then log in via SSH. Usually, though, that option to work around the problem is not available as I can't even get to find out the IP given to the device by a DHCP server. I found out that this problem is due to ModemManager scanning for modem in that serial port. I also found out that there is a way to fix the problem using an udev rule. The rule that is supposed to work is like this: ATTRS{idVendor}=="0ca6" ATTRS{idProduct}=="a050", ENV{ID_MM_DEVICE_IGNORE}="1" My case is a little different because the serial port is a peripheral of the CPU i.e. not a USB serial port, so I modified the rule to this form: KERNEL=="ttyS0", ENV{ID_MM_DEVICE_IGNORE}="1" udevadm now tells me that the line is being recognized and that attribute (or whatever it is called) added to the attributes of the device. The problem is not yet solved, though. For some reason, ModemManager still keeps flooding the console and makes logging in impossible. Removing ModemManager is not an option because my application needs it.

I have strange behaviour. I have USB 3G Modem and it doesnt auto-connect, yet that's what I want. I am just in headless mode; I'm trying "nmcli" and it doesn't work at all. But when I start desktop X11 system, it also starts nm-applet and it auto connects to 3G. Why so?

root@chip:~# nmcli g
STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN
connected  full          enabled  enabled  enabled  enabled

root@chip:~# nmcli c
NAME            UUID                                  TYPE             DEVICE
Ruter           00d82c8e-6ef2-49b7-b1ac-a66c303a560e  802-11-wireless  wlan0
ZZ              32f8fa94-35d6-4a51-9a5d-5c500270a0ed  gsm              --
usb0_linklocal  3c8ee1db-c6b3-4db6-8bfc-4e94e72cab17  802-3-ethernet   --

ZZ is 3G connection Wi-Fi is auto connecting, but 3G no! Also:

root@chip:~# nmcli c up ZZ
Error: Connection activation failed.

But nm-applet works fine and it automatically connects to 3G.