On Fri, 2019-11-15 at 16:10 +0100, Aleksander Morgado wrote:
> Hey,
>
> Is there any benefit in keeping per-vendor plugins installed as
> separate .so files and loaded during runtime?
>
> Does anyone know of any out-of-tree MM plugin out there? I would bet
> there isn't any as we truly haven't
On Fri, 2019-11-15 at 10:33 +0100, Aleksander Morgado wrote:
> Hey,
>
> > > On Thu, Nov 14, 2019 at 06:57:54PM +0100, Aleksander Morgado
> > > wrote:
> > > > > Has the interpretation of the ip_type
> > > > > MM_BEARER_IP_FAMILY_IPV4V6
> > > > > changed when performing the connect?
> > > > >
> >
Yeah. That mechanism may be useful for a built in package. OpenVPN uses that I
think
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Hey,
Is there any benefit in keeping per-vendor plugins installed as
separate .so files and loaded during runtime?
Does anyone know of any out-of-tree MM plugin out there? I would bet
there isn't any as we truly haven't kept a stable plugin API like
never ever.
Thinking of installed size, I
Enrico Mioso writes:
> Or the keep.d directory... ?
Except that change won't survive sysupgrade. /etc/sysupgrade.conf will
Bjørn
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
Or the keep.d directory... ?
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Amol Lad writes:
> root@OpenWrt:/# mmcli -m 0 --firmware-list
> error: couldn't list firmware images:
> 'GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient
> disconnected from message bus without replying'
Odd. Works for me:
root@wrt1900ac-1:/# mmcli -m 0 --firmware-list
Hi Aleksander,
It seems "mmcli -m 0 -firmware-list" is crashing modemmanager. There is no
debug output also in -debug mode. Please see last two commands in bottom of
this email. I'm running MM 1.12.0 (in openwrt)
root@OpenWrt:/# mmcli -m 0
General |
Hey Amol,
>
> The patch works with ipv4-only APN. I've set iptype to 'any' and it connects
> good and stays connected.
>
> If someone can test with ipv6/ipv4v6 APNs then it would be really great.
>
I've pushed a new pull request to openwrt-packages now:
Bjørn Mork writes:
> Aleksander Morgado writes:
>
>> Just add a ID_MM_DEVICE_IGNORE rule as you would have done with udev,
>> and restart the daemon.
>
> I should obviously have tried that first. Worked perfectly. After a
> reboot though. I believe the caching made it a noop on restart?
One
Thanks Aleksander,
The patch works with ipv4-only APN. I've set iptype to 'any' and it connects
good and stays connected.
If someone can test with ipv6/ipv4v6 APNs then it would be really great.
Thanks
Amol
The information in this email communication (inclusive of attachments) is
On Fri, Nov 15, 2019 at 1:41 PM Amol Lad wrote:
>
> I'll test it straight away but before that, is similar change needed in
> proto_modemmanager_teardown () as well?
>
Yep yep, you're right, I've updated the patch:
I'll test it straight away but before that, is similar change needed in
proto_modemmanager_teardown () as well?
proto_modemmanager_teardown() {
local interface="$1"
local modemstatus bearerpath errorstring
local bearermethod_ipv4 bearermethod_ipv6
local device lowpower iptype
json_get_vars
> > > Please find logs for mm in debug mode for iptype set to "ipv4" and "any"
> > > separately
> > >
> >
> > Ah, I know what the issue is. The "any" ip-type case is not being
> > handled in the modemmanager.proto file in the openwrt package, so as
> > soon as the modem gets connected, it just
> > Please find logs for mm in debug mode for iptype set to "ipv4" and "any"
> > separately
> >
>
> Ah, I know what the issue is. The "any" ip-type case is not being
> handled in the modemmanager.proto file in the openwrt package, so as
> soon as the modem gets connected, it just fails. Let me
Hey,
On Fri, Nov 15, 2019 at 12:28 PM Amol Lad wrote:
>
> Please find logs for mm in debug mode for iptype set to "ipv4" and "any"
> separately
>
Ah, I know what the issue is. The "any" ip-type case is not being
handled in the modemmanager.proto file in the openwrt package, so as
soon as the
Please find logs for mm in debug mode for iptype set to "ipv4" and "any"
separately
Thanks
Amol
The information in this email communication (inclusive of attachments) is
confidential to 4RF Limited and the intended recipient(s). If you are not the
intended recipient(s), please note that any
Nick B writes:
> Ah right, I see the problem now. I think Dan’s suggestions would help
> tremendously.
>
> Nevertheless, I tried ipv4v6 on Optus and Telstra in Australia. On
> Telstra I get both, on Optus I’ll only get IPv4. Specifying IPv6 on
> Optus yields no connection. So maybe it’s
Hey,
> > On Thu, Nov 14, 2019 at 06:57:54PM +0100, Aleksander Morgado wrote:
> > > > Has the interpretation of the ip_type MM_BEARER_IP_FAMILY_IPV4V6
> > > > changed when performing the connect?
> > > >
> > >
> > > No it hasn't really. I really think you need to know whether the
> > > network
Hey
>
> I’m using openwrt-master with latest mm 1.12.0 with EM7430 modem. As there
> were few discussions regarding using iptype as “any” in this forum so I tried
> it using below openwrt configuration
>
>
>
> config interface 'wwan'
>
> option device
>
20 matches
Mail list logo
