Skip to content

wds: Add WDS Bind Data Port message

Stephan Gerhold requested to merge (removed):wds-bind-data-port into master

This is similar to WDS Bind Mux Data Port, but for older systems without QMAP. It allows binding a WDS CID to one particular network interface when using the BAM DMUX network driver (see ModemManager!363 (closed)).

This MR adds the QMI message to the JSON files and also --wds-bind-data-port. I tested this as follows on a device with RPMSG + BAM-DMUX:

  1. Right now I need to patch qmi-proxy so it does not close the RPMSG device (see #51).
  2. Prepare modem: 
    qmicli -p -d /dev/modem --uim-verify-pin=PIN1,<pin>
qmicli -p -d /dev/modem --dms-set-operating-mode=online
  3. Assign port to WDS session and connect: 
    qmicli -p -d /dev/modem --client-no-release-cid --wds-noop
qmicli -p -d /dev/modem --client-no-release-cid --client-cid=1 --wds-bind-data-port=a2-mux-rmnet5
qmicli -p -d /dev/modem --client-no-release-cid --client-cid=1 --wds-start-network="apn=<apn>,ip-type=4"
  4. Now rmnet5 is functional, while other network interfaces are not: 
    ip link set rmnet5 up
udhcpc -i rmnet5
  5. We can repeat step 3 and 4 multiple times (with different network interfaces), as long as the APNs are different. Then multiple network interfaces are functional at the same time.

Overall this is an alternative solution for using multiple RPMSG QMI channels (that refer to one particular network device by default). It's probably a more convenient solution especially when we also use WDS Bind Mux Data Port for e.g. qmi_wwan.

Merge request reports