Location of rmnet setup

Michał Mazur mkm at semihalf.com
Fri Oct 9 08:19:47 UTC 2020

Hi Daniele,

I don't know location of the official librmnetctl repo. We are using
snapshot from branch LC.UM.1.0 of


pt., 9 paź 2020 o 08:02 Daniele Palmas <dnlplm at gmail.com> napisał(a):

> Hi Michal,
> Il ven 9 ott 2020, 04:05 Michał Mazur <mkm at semihalf.com> ha scritto:
>> Hi Aleksander,
>> Thank you for the reply. As you suggested I created MMPortRmnet to handle
>> data port setup:
>> https://gitlab.freedesktop.org/mkm/ModemManager/-/commit/b25310666e41a19150fe2b18ff3b7cce73f9129a
>> It includes all the code that uses the rmnet library to configure devices
>> but it is not probed yet.
> Can you please post a link for the official librmnetctl code repository?
> I can find many, but I'm not sure of the correct one.
> Thanks,
> Daniele
>> Regards,
>> Michal
>> sob., 3 paź 2020 o 14:34 Aleksander Morgado <aleksander at aleksander.es>
>> napisał(a):
>>> Hey Michał!
>>> >
>>> > We've decided to move the rmnet configuration to libqmi. It seems to
>>> be a better place because there is already a class for QRTR control socket.
>>> I would suggest discussing in the public mailing list or in gitlab
>>> issues this kind of thing, so that everyone can participate in the
>>> discussion.
>>> >
>>> >
>>> https://gitlab.freedesktop.org/mkm/libqmi/-/commit/3e063884efd6cc217e91be4601ee3b
>>> > This patch adds a new class for QRTR data port. During initialization
>>> it opens an INET socket to bring up the rmnet_ipa device and uses the
>>> rmnetctl library to create a virtual network device (rmnet_data0). This new
>>> device will be used in ModemManager.
>>> How is it that the "QRTR data port" does nothing with the QRTR
>>> protocol? Yes, this rmnet data port is the one that would be used for
>>> data while QRTR is used for control, but I don't think libqrtr would
>>> be the place to add this. From an outsider perspective, you could say
>>> you need libqmi+libqrtr for control, and rmnetctl to bring up the data
>>> network interface, but I wouldn't add this new object in libqrtr, as
>>> it really has nothing to do with the QRTR protocol itself.
>>> If you ask me, ModemManager is a better place for this, e.g. a let's
>>> say a MMPortRmnet object which would map the virtual network interface
>>> created with rmnetctl. Oh wait, I did already suggest something like
>>> this in a previous email that was never replied...
>>> --
>>> Aleksander
>>> https://aleksander.es
>>> _______________________________________________
>>> ModemManager-devel mailing list
>>> ModemManager-devel at lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>> _______________________________________________
>> ModemManager-devel mailing list
>> ModemManager-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20201009/f4e20b7b/attachment-0001.htm>

More information about the ModemManager-devel mailing list