hp-lt4132 'unavailable' in NetworkManager on Debian 10

[Aleksander Morgado]

> cfocke at hp-eb-x360-1030-g3<mailto:cfocke at hp-eb-x360-1030-g3>:~$ ip addr
> 
> 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: wwp0s20f0u3c3: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
> 
>     link/ether c6:4e:86:9d:4e:44 brd ff:ff:ff:ff:ff:ff
> 
> 3: enx0050b6983a69: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
> 
>     link/ether 00:50:b6:98:3a:69 brd ff:ff:ff:ff:ff:ff
> 
> 4: wlp108s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
> 
>     link/ether 20:16:b9:f2:53:c3 brd ff:ff:ff:ff:ff:ff
> 
>     inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp108s0
> 
>        valid_lft 86280sec preferred_lft 86280sec
> 
>     inet6 2a02:8388:180a:f580:603a:d001:36d8:f92b/64 scope global dynamic noprefixroute
> 
>        valid_lft 1075621sec preferred_lft 604797sec
> 
>     inet6 fe80::cd4a:9a4:1160:450e/64 scope link noprefixroute
> 
>        valid_lft forever preferred_lft forever
> 
> cfocke at hp-eb-x360-1030-g3<mailto:cfocke at hp-eb-x360-1030-g3>:~$ ip route
> 
> default via 192.168.0.1 dev wlp108s0 proto dhcp metric 600
> 
> 169.254.0.0/16 dev wlp108s0 scope link metric 1000
> 
> 192.168.0.0/24 dev wlp108s0 proto kernel scope link src 192.168.0.31 metric 600
> 
> cfocke at hp-eb-x360-1030-g3<mailto:cfocke at hp-eb-x360-1030-g3>:~$
> 
> ... no IP address, no route; maybe I should take this issue with the NetworkManager people?
> 

Thomas, Lubomir, Dan, any idea of what could be happening here?

MM connection attempt using MBIM goes well, MM reports IP settings to use, NM reports the device is connected, but the network interface isn't being configured properly. Is there any known issue with this logic in 1.14.6?


-- 
Aleksander
https://aleksander.es