HI, Thank you for your answer. This works, indeed, and it is the information I was looking for. However, I have a follow-up question:
When using the multiplex property, a virtual interface called mbimmux<modem dbus id>.<vlan id> is created. Is it possible to control the interface name and the VLAN ID used for this interface? This would be useful for having a consistent/simple routing configuration in the system. For example if the modem is being reset, the virtual interface name will change as well. Having a predefined name for the virtual interface might be easier. Thank you, Radu On Tue, Jan 23, 2024 at 2:42 AM Bjørn Mork <bj...@mork.no> wrote: > Radu C <rcer...@gmail.com> writes: > > > Hi, > > > > There are multiple tutorials online on how to connect a modem to a 5G > core > > with multiple PDUs using mbimcli (like > > > https://www.kernel.org/doc/html/latest/networking/cdc_mbim.html#mbim-data-channel-userspace-abi > , > > or > > > https://paldan.altervista.org/linux-mbim-wwan-multiple-pdn-setup/?doing_wp_cron=1705964667.8114559650421142578125 > > ). > > > > Essentially in mbimcli one can specify a session id, as part of the > access > > string. This session ID is then mapped to a VLAN ID, which is mapped to a > > virtual interface on top of the modem network interface. In short, > > something like this: > > > > ``` > > ip link add wwan0.1 link wwan0 type vlan id 1 > > ip link add wwan0.2 link wwan0 type vlan id 2 > > mbimcli -p -d /dev/cdc-wdm0 --connect=apn=apnA,session-id=1,ip-type=ipv4 > > --no-close --no-open=42 > > mbimcli -p -d /dev/cdc-wdm0 --connect=apn=apnB,session-id=2,ip-type=ipv4 > > --no-close --no-open=42 > > ``` > > > > Is it possible to achieve the same result using mmcli, or the > ModemManager > > API? > > mmcli -m any --simple-connect=apn=apnA,multiplex=requested > mmcli -m any --simple-connect=apn=apnB,multiplex=requested > > or use multiplex=required if you want mmcli to fail if unsupported > > Bjørn >
