ager could be a solution for your use-case? I don't know,
> just proposing here.
>
> Enrico
>
>
> On Sat, 2 Oct 2021, Lucas Pelegrino wrote:
>
> > Date: Sat, 2 Oct 2021 23:21:22
> > From: Lucas Pelegrino
> > To: Yegor Yefremov
> > Cc: &quo
or your use-case? I don't know, just
proposing here.
Enrico
On Sat, 2 Oct 2021, Lucas Pelegrino wrote:
Date: Sat, 2 Oct 2021 23:21:22
From: Lucas Pelegrino
To: Yegor Yefremov
Cc: "ModemManager (development)"
Subject: Re: Modem connected but no internet
Just to give some m
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 p
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: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:
Hi Lucas,
On Sat, Oct 2, 2021 at 4:26 PM Lucas Pelegrino 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
> |
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
-
