<![CDATA[Dev1 Galaxy Forum / [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?id=5775 Sat, 29 Jul 2023 14:24:32 +0000 FluxBB <![CDATA[Re: [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?pid=43119#p43119 I don't know if it should be termed as a solution or rather a workaround. Finally it works.

The problem seems to be that the device presents itself in three modes, connected to ppp0 (ppp), ttyACM0 (mobile broadband) and usb0 (ethernet). Network manager seems to try each one and disconnect the others. I'm not sure about that, but to prevent network manager from handling the devices and giving the job to ifupdown solved the problem. Strange enough, nm-applet then shows this connections icon in the tray.

What to do:
Add to /etc/network/interfaces

allow-hotplug usb0
iface usb0 inet dhcp
iface usb0 inet6 auto

Create / add to /etc/NetworkManager/conf.d/unmanaged-devices.conf

[keyfile]
unmanaged-devices=interface-name:ppp0;interface-name:ttyACM0;interface-name:usb0

Make it happen as root by:

service network-manager restart
ifup usb0
]]> Sat, 29 Jul 2023 14:24:32 +0000 https://dev1galaxy.org/viewtopic.php?pid=43119#p43119 <![CDATA[Re: [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?pid=42761#p42761 There are isc-dhcp-client and conman installed.

conmand is running.

How can I find out which programs are managing network devices / connections?

]]> Tue, 04 Jul 2023 15:53:32 +0000 https://dev1galaxy.org/viewtopic.php?pid=42761#p42761 <![CDATA[Re: [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?pid=42751#p42751 felixed wrote:

Who the hell does control the network connections?

Some dhcp client, maybe? /etc/network/interfaces is for ifupdown

]]> Mon, 03 Jul 2023 19:06:09 +0000 https://dev1galaxy.org/viewtopic.php?pid=42751#p42751 <![CDATA[Re: [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?pid=42749#p42749 Is it a overconnection connection kill? On a cable-only system I

- uninstall network-manager. Still get connected.

- disable anything in /etc/network/interfaces. Still get connected.

- reinstall network-manager and disable ifupdown / keyfile in /etc/NetworkManager/NetworkManager.conf

#[main]
#plugins=ifupdown,keyfile

#[ifupdown]
#managed=false

Still get connected after reboot.

Who the hell does control the network connections?

]]> Mon, 03 Jul 2023 18:22:13 +0000 https://dev1galaxy.org/viewtopic.php?pid=42749#p42749 <![CDATA[[SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected]]> https://dev1galaxy.org/viewtopic.php?pid=42742#p42742 system: Devuan Chimaera, amd64, same problem on different laptops, network-manager
lsusb: Bus 001 Device 010: ID 2ecc:3010 Asrmicro Asrmicro (it's the eth mode)

When booting with connected stick it is connected to the internet as mobile broadband. Connection data from nm-applet:

Schnittstelle GSM (ttyACM0)
Treiber cdc_acm, mdis_host
Geschwindigkeit Unbekannt
Ipv4
IP-Adresse 10.38.155.185
Broadcast-Adresse 10.38.155.185
Subnetz-Maske 255.255.255.255
» Weitere Adressen
Vorgaberoute 0.0.0.0
Primärer DNS 10.74.210.210
Sekundärer DNS 10.74.210.211
IPv6
IP-Adresse fe80::d57a:d23:a13c:f9d6/64
» Weitere Adressen
Vorgaberoute fe80:albf:dcea:4ea4:817a

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ea:4c:6a:a6:95:1a brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 7165sec preferred_lft 7165sec
    inet6 fe80::7b53:b95a:c413:a84e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 3
    link/ppp 
    inet 10.37.206.186 peer 10.64.64.64/32 scope global ppp0
       valid_lft forever preferred_lft forever
    inet 10.37.206.186/32 scope global noprefixroute ppp0
       valid_lft forever preferred_lft forever
    inet6 fe80::6d41:b7f8:7dfb:741 peer fe80::a1bf:dcea:4ea4:817a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::1a36:4075:1d47:f02f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

After some minutes the device is disconnected, ppp0 gone:

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ea:4c:6a:a6:95:1a brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 6798sec preferred_lft 6798sec
    inet6 fe80::7b53:b95a:c413:a84e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

After executing 

sudo service network-manager restart

several times, the usb device is connected as ethernet device.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 72:f9:66:ad:f0:b6 brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 7108sec preferred_lft 7108sec
    inet6 fe80::a0c1:cdec:e7f8:ada1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

According to nm-applet now:

Schnittstelle Ethernet (usb0)
Hardware-Adresse 4E:05:1C:E7:24:45
Treiber mdis_host
Geschwindigkeit Unbekannt
Sicherheit Keine
IPv4
IP-Adresse 192.168.0.231
Broadcast-Adresse 192.168.0.255
Subnetz-Maske 255.255.255.0
Vorgaberoute 192.168.0.1
Primarer DNS 192.168.0.1
IPv6
IP-Adresse fe80::6a38:14c2:ad6:48f4/64

Starting network-manager by

sudo service network-manager stop
sudo NetworkManager -d

leads to the following messages:

sudo NetworkManager -d
<info>  [1688297559.5098] NetworkManager (version 1.30.6) is starting... (after a restart)
<info>  [1688297559.5099] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
<info>  [1688297559.5127] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
<info>  [1688297559.5150] manager[0x564e8124c020]: monitoring kernel firmware directory '/lib/firmware'.
<info>  [1688297559.5151] monitoring ifupdown state file '/run/network/ifstate'.
<info>  [1688297559.5164] hostname: hostname: couldn't get property from hostnamed
<info>  [1688297559.5165] hostname: hostname changed from (none) to "lenovo-debian"
<info>  [1688297559.5168] dns-mgr[0x564e81245170]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
<info>  [1688297559.5173] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/ieee80211/phy0/rfkill0) (driver rtw_8821ce)
<info>  [1688297559.5174] manager[0x564e8124c020]: rfkill: Wi-Fi hardware radio set enabled
<info>  [1688297559.5174] manager[0x564e8124c020]: rfkill: WWAN hardware radio set enabled
<info>  [1688297559.5194] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wwan.so)
<info>  [1688297559.5197] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-adsl.so)
<info>  [1688297559.5201] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-bluetooth.so)
<info>  [1688297559.5204] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wifi.so)
<info>  [1688297559.5213] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-team.so)
<info>  [1688297559.5216] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
<info>  [1688297559.5217] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
<info>  [1688297559.5218] manager: Networking is enabled by state file
<info>  [1688297559.5219] dhcp-init: Using DHCP client 'internal'
<info>  [1688297559.5222] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-settings-plugin-ifupdown.so")
<info>  [1688297559.5222] settings: Loaded settings plugin: keyfile (internal)
<info>  [1688297559.5222] ifupdown: management mode: managed
<info>  [1688297559.5223] ifupdown:       interface-parser: parsing file /etc/network/interfaces
<info>  [1688297559.5223] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
<info>  [1688297559.5372] device (lo): carrier: link connected
<info>  [1688297559.5375] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
<info>  [1688297559.5383] device (usb0): carrier: link connected
<info>  [1688297559.5386] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
<info>  [1688297559.5413] device (usb0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
<info>  [1688297559.5424] device (usb0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
<info>  [1688297559.5434] device (usb0): Activation: starting connection 'usb0' (e270cee1-1313-40f9-8f45-07bff69db3ca)
<info>  [1688297559.5436] device (wlan0): driver supports Access Point (AP) mode
<info>  [1688297559.5442] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
<info>  [1688297559.5453] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
<info>  [1688297560.0874] device (wlan0): set-hw-addr: set MAC address to 62:CA:32:80:E9:7D (scanning)
<info>  [1688297560.6091] device (usb0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6099] device (usb0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6159] agent-manager: agent[60f2fca35ecc68ce,:1.41/org.freedesktop.nm-applet/1000]: agent registered
<info>  [1688297560.6160] modem-manager: ModemManager available
<info>  [1688297560.6161] device (usb0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6164] device (usb0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6188] device (usb0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6192] device (usb0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6197] manager: NetworkManager state is now CONNECTED_LOCAL
<info>  [1688297560.6213] device (usb0): Activation: successful, device activated.
<info>  [1688297560.6225] manager: NetworkManager state is now CONNECTED_GLOBAL
<info>  [1688297560.6630] device (wlan0): supplicant interface state: internal-starting -> disconnected
<info>  [1688297560.6631] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
<info>  [1688297561.1658] manager: startup complete

Surprisingly the device gets connected too when network-manager is stopped.

/etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
#auto lo
#iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

Any ideas who is connecting and cancelling the connections? How can I just connect the stick as ethernet device or leave it in mobile broadband mode?

The laptops are also using WLAN and cable connections as well so I would prefer an automatic solution.

Thanks for any help.

]]> Sun, 02 Jul 2023 17:31:02 +0000 https://dev1galaxy.org/viewtopic.php?pid=42742#p42742