Re: AT port not attacted with RM520N-GL

2024-02-14 Thread Pradeep Gopanapalli
Hi Aleksander,

I found these two stable releases, which one you recommend given that we
are
currently using MM 1.16:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tags/1.22.0
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tags/1.20.6
Are there any libqmi and libmbim requirements for 1.20.6 ?
(modemmanager - 1.16.6-3
libqmi - 1.28.6-3
libmbim - 1.24.8-2)

Thanks,
Pradeep G



On Tue, Feb 13, 2024 at 2:19 PM Aleksander Morgado <
aleksande...@chromium.org> wrote:

> >
> > Thanks for your reply, I will try out the suggested methods.
> > And another thing is we are planning to update ModemManager
> > ,currently we are at 1.16.6-2) and we can go to 1.20 stable versions.
> > Is there any stable version that you can push into ModemManager sources?
> > https://www.freedesktop.org/software/ModemManager/
> >
>
> Please use the signed git tags to retrieve the stable versions, we
> stopped publishing tarballs some time ago.
>
> --
> Aleksander
>

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.


Re: No IP address for a successful connection on LTE modem

2024-02-14 Thread Garfield Watkins
I think what confused me is that without the ModemManager i.e. using 
just cgact=1,1 to manually connect, i suddenly got an ip address 
assigned to the network interface provided by the modem. I thought it 
was NetworkManager running its dhcp client on that interface after 
getting a dhcp discover ? from the modem ? (i'm not too sure about how 
dhcp goes about its business)


Anyway i have now tried to use Network Manager to setup and connect but 
now am getting the following message:


modem-broadband[ttyUSB0]: failed to connect 'meig': Connection requested 
both IPv4 and IPv6 but dual-stack addressing is unsupported by the modem.


and disabling ipv6 I get:

 failed to connect 'meig': Connection requested IPv4 but IPv4 is 
unsupported by the modem.


Any idea where to start debugging that ?


On 2/14/24 11:24, Aleksander Morgado wrote:

Hey!

On Tue, Feb 13, 2024 at 1:49 PM Garfield Watkins
  wrote:

Did you connect the modem using NetworkManager (e.g. using nmcli) or
did you connect the modem using mmcli?

I see where you are going with this. It seems I expected more of the 
interaction between the ModemManager and Network Manager . To answer your 
question, no I have only used mmcli. Let me try the process with nmcli.


:) NM only processes the connections that have been started via NM.
There's a fundamental reason for that, which is that all the
network-specific routing is done at NM level, MM knows nothing about
it. In order for NM to know how to route traffic to through the LTE
connection, it needs to use its own connection settings.


Re: No IP address for a successful connection on LTE modem

2024-02-14 Thread Aleksander Morgado
Hey!

On Tue, Feb 13, 2024 at 1:49 PM Garfield Watkins
 wrote:
>
> Did you connect the modem using NetworkManager (e.g. using nmcli) or
> did you connect the modem using mmcli?
>
> I see where you are going with this. It seems I expected more of the 
> interaction between the ModemManager and Network Manager . To answer your 
> question, no I have only used mmcli. Let me try the process with nmcli.
>

:) NM only processes the connections that have been started via NM.
There's a fundamental reason for that, which is that all the
network-specific routing is done at NM level, MM knows nothing about
it. In order for NM to know how to route traffic to through the LTE
connection, it needs to use its own connection settings.

-- 
Aleksander