Modem connected but no internet

Sat Oct 2 21:21:22 UTC 2021

Just to give some more information. When I do `dhclient wwan0` I can see a
new route being added and wwan0 works:

$ ip route show
*default via 100.72.135.138 dev wwan0 *
default via 192.168.0.1 dev wlan0 metric 1
default via 192.168.0.1 dev wlan0 proto dhcp metric 600
100.72.135.136/30 dev wwan0 proto kernel scope link src 100.72.135.137
100.73.179.140/30 dev wwan1 proto kernel scope link src 100.73.179.142
metric 700
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.16

But if I do `dhclient wwan1` nothing changes on the `ip route show`. I
don't understand much about networks, but I guess I can only have one route
set? I think `dhclient` might not be the issue. Any information is
appreciated.

Em sáb., 2 de out. de 2021 às 12:03, Lucas Pelegrino <lucas.wxp at gmail.com>
escreveu:

> I tried running `sudo dhclient wwan0`, it seems it got one of the modems
> to work, but I have two modems and `wwan1` remains with the same problem
> and `sudo dhclient wwan1` didn't seem to work on it.
>
> 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
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state
> DOWN group default qlen 1000
> link/ether b8:27:eb:87:22:8e brd ff:ff:ff:ff:ff:ff
> 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
> UP group default qlen 1000
> link/ether b8:27:eb:d2:77:db brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.16/24 brd 192.168.0.255 scope global dynamic noprefixroute
> wlan0
> valid_lft 85555sec preferred_lft 85555sec
> inet6 2804:14c:7582:46bf::1007/128 scope global dynamic noprefixroute
> valid_lft 85557sec preferred_lft 85557sec
> inet6 2804:14c:7582:46bf:cfbe:7945:f701:da92/64 scope global dynamic
> noprefixroute
> valid_lft 86372sec preferred_lft 71972sec
> inet6 fe80::5139:cd08:a2a9:9a4e/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
> 4: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 100.70.243.89/30 brd 100.70.243.91 scope global noprefixroute wwan0
> valid_lft forever preferred_lft forever
> 6: wwan1: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 100.71.207.216/28 brd 100.71.207.223 scope global dynamic wwan1
> valid_lft 518326sec preferred_lft 518326sec
>
>
>
> Em sáb., 2 de out. de 2021 às 11:36, Yegor Yefremov <
> yegorslists at googlemail.com> escreveu:
>
>> Hi Lucas,
>>
>> On Sat, Oct 2, 2021 at 4:26 PM Lucas Pelegrino <lucas.wxp at gmail.com>
>> wrote:
>> >
>> > Hello there.
>> >
>> > I have this behavior in my raspberry PI where a modem shows connected,
>> but I still can't connect to the internet:
>> > --------------------------------
>> > General | path: /org/freedesktop/ModemManager1/Modem/4
>> > | device id: ab1573a4186ee4930c3dbe7ee14e2dddcd10b4c2
>> > --------------------------------
>> > Hardware | manufacturer: huawei
>> > | model: E3276
>> > | firmware revision: 21.260.05.01.150
>> > | supported: gsm-umts
>> > | current: gsm-umts
>> > | equipment id: 866519011156587
>> > --------------------------------
>> > System | device:
>> /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.2
>> > | drivers: huawei_cdc_ncm, option
>> > | plugin: huawei
>> > | primary port: cdc-wdm0
>> > | ports: cdc-wdm0 (at), ttyUSB0 (at), ttyUSB1 (at), wwan0 (net)
>> > --------------------------------
>> > Numbers | own: +xxxx
>> > --------------------------------
>> > Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3),
>> sim-puk2 (10)
>> > | state: connected
>> > | power state: on
>> > | access tech: umts
>> > | signal quality: 41% (recent)
>> > --------------------------------
>> > Modes | supported: allowed: 2g; preferred: none
>> > | allowed: 3g; preferred: none
>> > | allowed: 4g; preferred: none
>> > | allowed: 2g, 3g, 4g; preferred: none
>> > | current: allowed: 2g, 3g, 4g; preferred: none
>> > --------------------------------
>> > IP | supported: ipv4, ipv6, ipv4v6
>> > --------------------------------
>> > 3GPP | imei: 866519011156587
>> > | operator id: 72416
>> > | operator name: Oi
>> > | registration: roaming
>> > --------------------------------
>> > 3GPP EPS | ue mode of operation: csps-2
>> > --------------------------------
>> > SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/4
>> > --------------------------------
>> > Bearer | paths: /org/freedesktop/ModemManager1/Bearer/5
>> >
>> >
>> >
>> > Weird thing is that on my Ubuntu desktop this modem works! The only
>> difference I noticed is that in my Ubuntu field 'access tech' is 'lte',
>> while above (on the pi) like you can see it's 'umts'.
>> >
>> > I figured the problem might be related to the 'access tech' field
>> above, so I tried forcing setting mode for '4g' but didn't work:
>> >
>> > $ sudo mmcli -m 4 --set-allowed-modes='4g' --set-preferred-mode='4g'
>> > error: couldn't set current modes:
>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: The
>> given combination of allowed and preferred modes is not supported'
>> >
>> >
>> > The only difference between my raspberry pi and my desktop machine is
>> that the pi is under a more recent version of ModemManager 1.16 vs 1.12
>> from my desktop Ubuntu.
>> >
>> > Any ideas?
>>
>> Could you share your IP configuration i.e. please post the output of
>> the "ip addr" command. Looks like you haven't run dhcpclient or alike
>> on your wwan0 interface.
>>
>> Best regards,
>> Yegor
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20211002/b267e2be/attachment.htm>