On Mon, Nov 07, 2022 at 04:02:29PM +0100, Aleksander Morgado wrote:
> A very similar issue was fixed for Qualcomm modems using QMI in the
> following merge request:
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/789
>
> The problem solved there was that the connect
Beyond my skill level but as a temporary fix the following works well
for me - namely just amend the 10-report-down script so that it ends
with:
```
IFUP=$(ifstatus ${CFG} | jsonfilter -e '@.up')
logger -t "modemmanager" "interface ${CFG} (network device
${INTERFACE}) ${STATE}"
proto_init_update
Hello,
I hadn't realized that you had this list:
>> There is also an open source database we maintain in
>> https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info but
>> which also has the same problems, it lacks a lot of latest updates
>> even from major carriers.
It appears that you ar
On 11/7/22 10:22, Aleksander Morgado wrote:
Hey Peter!
This is obviously an awkward point to debug anything, and it's perhaps not
super important at this point, but it's pretty repeatable and has happened
as long as I can remember.
This is with MM 1.20.0, glib 2.70.4 and libqmi 1.32.0.
Di
Hey Peter!
On Fri, Nov 4, 2022 at 3:49 PM Peter Naulls wrote:
>
>
> When rebooting in OpenWrt:
>
> [ 548.410590] mtk_soc_eth 1e10.ethernet eth0: Link is Down
> [ 548.425055] device eth0 left promiscuous mode
> [ 548.434058] br-lan: port 1(eth0) entered disabled state
> [ 550.455000] do_pa
Hey
>
> I have a problem where rarely, but randomly ModemManager choosest to make
> the the connection over the AT rather than the QMI interface. A failed one
> looks on the log like:
>
> -snip-
> ModemManager (version 1.16.10) starting in system bus...
> systemd[1]: Started Modem Manager.
> [/d
Hi,
I have a problem where rarely, but randomly ModemManager choosest to make
the the connection over the AT rather than the QMI interface. A failed one
looks on the log like:
-snip-
ModemManager (version 1.16.10) starting in system bus...
systemd[1]: Started Modem Manager.
[/dev/cdc-wdm0] Open
Hey,
>
> It seems that after that, ModemManager breaks, because the NetworkManager
> install is doing something to break it.
>
NetworkManager brings as dependency libmm-glib, and will install it in
the same location as your custom built libmm-glib.
The way to avoid this is to first install NM wi
Hey Fredrik
> I'm working with a modem that supports GSM, LTE Cat-M, and NB-IoT. Ideally, I
> could both query and, more importantly, set which of these access technologies
> are allowed in the modem through ModemManager's API.
>
> As far as I understand, ModemManager understands the concepts of (
Hey,
>
> So what I tried instead was to simply directly install the
> ModemManager .ipk from OpenWrt master on my 22.03.2 environment. It
> worked, and now with the updated Modem Manager with dispatcher script
> as per:
>
> https://github.com/openwrt/packages/commit/bc754f31cfdb004eefa43038f8f0827
Hey,
> I have yet another question around the Fibocom MA510 modem. I'm
> observing an issue where the modem is in registered state when
> ModemManager starts up. MM ignores this due to
>
> 3GPP registration state change ignored as modem isn't enabled (line 832)
>
> MM then triggers an automatic ne
Hey,
On Tue, Oct 25, 2022 at 8:44 PM Arkadiusz Drabczyk
wrote:
>
> I use ModemManager 1.18.6 on OpenWRT 22.03.0-rc4. I run it:
>
> root@OpenWrt:~# ModemManager
> [6778]: ModemManager (version 1.18.6) starting in system bus...
>
> Report kernel events:
>
> root@OpenWrt:~# mmcli
> --report-kerne
Hey!
>
> > No, the DHCP server is running in the modem, to ease the configuration
> > process on the host side. Qualcomm modems have it for sure, there are
> > several other manufacturers that don't.
> > There is no DHCP protocol used in between the modem and the network,
> > IP assignment is don
Hey,
> My company produces a device with the Sierra EM7565 Modem and we have
> encountered problems related to the APN setting. (A collegue of mine sent a
> message into this list a week ago and has received kind help by Aleksander
> Morgado whom I'd like to thank.)
>
> We observed the followin
Hello,
After some further testing, it seems that this is caused by installing
NetworkManager via apt.
I run these commands to build and install:
> wget
> https://www.freedesktop.org/software/ModemManager/ModemManager-1.16.6.tar.xz
> tar -Jxvf ModemManager-1.16.6.tar.xz
> cd ModemManager-1.16.6
Hello,
Thanks for the reply, Alek.
> And "sudo make install" I hope?
Yes of course, I forgot to add that.
> If you tried to remove those flags it could very well be that you
> installed under /usr/local also and then there's a mix of libraries
> and binaries around.
I tried first with the flags,
Hi all,
I'm working with a modem that supports GSM, LTE Cat-M, and NB-IoT. Ideally, I
could both query and, more importantly, set which of these access technologies
are allowed in the modem through ModemManager's API.
As far as I understand, ModemManager understands the concepts of (1) modes,
(2)
Hey,
On Fri, Oct 28, 2022 at 11:47 AM Robin wrote:
>
> I have a problem with ModemManager, but only when trying to get an IPv4
> address when the network only supports IPv6 (Dual Stack, using IPv4v6).
>
> I have two different systems:
>
> - one running OpenWRT v19 and ModemManager v1.12.2
> - th
18 matches
Mail list logo
