RM500Q slow with qmi_wwan, fast with proprietary

[Aleksander Morgado]

Hey,

> Still haven’t made progress with MM multiplexing on OpenWrt except for adding support to use the multiplex parameter in the connect args.  I’ll post what have in case anyone else has the same problem.  This should just be an incompatibility with the OpenWrt netifd script, right?  I am not quite sure if there would be anything else that needs to happen here because the documentation I have been able to find around this topic has been sparse.
>
>
> After using QMICLI to set it up the connection I set up qmimux0 and wwan0 OpenWrt interfaces in the WAN firewall zone. As you can see this works fine.
>
> root at OpenWrt:~# ip route
> default via 10.210.81.132 dev qmimux0 proto static src 10.210.81.131
> 10.210.81.128/29 dev qmimux0 proto kernel scope link src 10.210.81.131
> 192.168.1.0/24 dev br-lan proto kernel scope link src 192.168.1.1
>
> root at OpenWrt:~# ip link
> 4: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 32768 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
>     link/ether 36:36:d7:22:de:5e brd ff:ff:ff:ff:ff:ff
> 15: qmimux0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
>
> root at OpenWrt:~# ping 8.8.8.8
> PING 8.8.8.8 (8.8.8.8): 56 data bytes
> 64 bytes from 8.8.8.8: seq=0 ttl=113 time=61.536 ms
>
>
> But after MM sets up the connection and manages the interface things are set up a little differently; MTU, links, number of links to name a few.  I created network interfaces for these links and added them to the WAN firewall zone as before, however although the route seems to be configured correctly, pings to the gateway fail.
>
> root at OpenWrt:~# ip route
> default via 10.211.71.62 dev qmimux0 proto static src 10.211.71.61
> 10.211.71.60/30 dev qmimux0 proto kernel scope link src 10.211.71.61
> 192.168.1.0/24 dev br-lan proto kernel scope link src 192.168.1.1
>
> root at OpenWrt:~#  ip link
> 4: wwan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 31744 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
> 15: qmimux0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
> 16: qmimux1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
> 17: qmimux2: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
> 18: qmimux3: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
>     link/none
>

Don't recall about how openwrt firewall zones could be configured, but
can you add iface names with wildcards like qmimux* to a zone in
openwrt?
Out of curiosity, did you try to fully disable the firewall altogether
in openwrt and retry?

In the issue you're having, I think the first thing to do is rule out
the effect of iptables.

-- 
Aleksander