differences between with rmnet and qmi_wwan

[Alexander 'lynxis' Couzens]

Hi Martin,

so far I understand it:

> |__ Port 001: Dev 004, If 4, Class=[unknown], Driver=qmi_wwan, 480M
> 
> I think it was automatically using qmi_wwan driver. Do I need to switch 
> off a kernel switch for qmi_wwan and enable one for rmnet to get to the 
> new one?

You'll always use qmi_wwan here. But you can configure rmnet on top of it.

modem -> qmi_wwan -> rmnet -> generic linux network if you use encapsulation like qmap.

> You mentioned:
> 
> > Yes, there are (e.g. uplink aggregation, flow control commands...).  
> 
> Are these all "internal" feature, which work by itself? Or are there programs like qmicli to control these?
> Or is qmicli detecting automatically that rmnet is used and offers me more commands?

No, you've to configure the modem and the kernel.
You have to configure the modem via user space tools qmiclient.
And you have to configure the kernel either qmiux over /sys/fs or add rmnet. 

The kernel driver doesn't do much here. It only takes care of the user plane (ip traffic).

> Has qmimux something to do with rmnet? Or is it even the same?

no. qmimux is the old implementation, not so flexible, doesn't support all encapsulations as rmnet supports
and can be only controlled via /sys/fs.
While rmnet is configured via netlink. You should able to use iproute2 to configure it.

Best Regards,
lynxis