<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Hi all,<br>
<br>
Using DSS we got 2 issues due to VLAN mapping of DSS channels:<br>
1. If your interface come down you can not anymore communicate
with your DSS, but DSS should not be related to wwan intarface
status.<br>
2. DSS are not IP based, but as kernel saw them as network
interface it forward ip broadcast and multicast to it. Even when
we set VLAN interface flags to only UP we got some unknown packets
forwarded to it (Wireshark is not able to decode them).<br>
<br>
After some discussions with Bjørn Mork to understand how mbim
driver is working for DSS channels we concluded that currently DSS
channels are fully dependent of wwan interface state. It means
that even if we switch to TTY we will get the same behavior except
for point 2 that should be solved.<br>
<br>
MBIM specification says that we have 2 bulk endpoints for data
communications (IP based and DSS), one is used for TX and the
second for RX. But those endpoints are handled by usbnet driver
that don't know about DSS.<br>
<br>
One solution could be to alter usbnet driver to add a new flag
preventing endpoints to be down when wwan interface come down and
at least one DSS channel is up.<br>
<br>
Does anyone already encounter this kind of problem?<br>
<br>
Windows is handling DSS channels as we could expect, It's a bad
news if Windows can do better than Linux :-)<br>
<br>
Regards,<br>
<br>
Arnaud<br>
</font>
<p></p>
<p>-- IMPORTANT NOTICE: </p>
<p>The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.</p></body>
</html>