<div dir="ltr">Hi Bjorn and aleksander,<div><br></div><div>Thanks for reply.</div><div>E1732:</div><div>Before connection does it mandatory to register with circuit switch(CS) and packet switch(PS) and attach to packet switch?</div> <div> In windows registering with PS,CS and attaching to PS is done through serial interface(PC UI port) by sending AT commands.</div><div> And then, able to connect either modem or network interface to network.</div><div> <br></div><div>1) In ubuntu without sending any AT commands to the serial interface for registering and attaching with PS and CS, I am able to connect using NDIS interface by sending WDS start request. once connection is success if i am running udhcpc on wwan0 interface i am able to acquire IP address.(qmi_wwan(data and control) and cdc-wdm(subdriver)) </div> <div><br></div><div>In ubuntu how registering with network is happening before connection? does it depends on ISP?</div><div>---------------------------------------------------------------------------------------------------------------------------------------------</div> <div><br></div><div>2) In ubuntu i am switching E1732 using usb_modeswitch based on message content present in switching configuration target vendor ID and bInterfaceClass, bInterfaceSubClass and bInterfaceProtocol <span style="white-space:pre">are varying.</span></div> <div><span style="white-space:pre"><br></span></div><div><span style="white-space:pre">case 1: </span></div><div><span style="white-space:pre">vid: 140C</span></div><div><span style="white-space:pre">bInterfaceClass FFh Vendor-Specific bInterfaceSubClass FFh bInterfaceProtocol FFh</span><br></div><div><span style="white-space:pre"><br></span></div><div><div><span style="white-space:pre">case 2:</span></div><div><span style="white-space:pre">vid: 1436</span></div><div><span style="white-space:pre">bInterfaceClass 02h CDC bInterfaceSubClass 06h ECM bInterfaceProtocol FFh</span></div></div><div><span style="white-space:pre"><br></span></div><div><span style="white-space:pre">In windows after switch it is going to CASE 1. </span></div><div><span style="white-space:pre">I am using CASE 2 in ubuntu and able to connect.</span></div> <div><span style="white-space:pre">i am able to switch to case 1 but i am using case 2 only as of now.</span></div><div><br></div><div><span style="white-space:pre">Can I know any difference will be there regarding QMI request and response based on service(wds,nas,cat etc) for connection?</span><br> </div><div><span style="white-space:pre">or some services wont be supported in one configuration and some supported in other configuration?</span></div><div><span style="white-space:pre"><br></span></div><div><span style="white-space:pre">-----------------------------------------------------------------------------------------------------------------------------------------------------</span></div> <div><span style="white-space:pre">3)In general can i send QMI_NAS_INITIATE_NETWORK_REGISTER and QMI_NAS_INITIATE_ATTACH QMI requests to the device for registering with PS and CS, since i am not sending any AT commands for registering(PS and CS) before wds start request? even though it is connecting as of now. Can i know any other requests i need to send before wds start?</span></div> <div><br></div><div><span style="white-space:pre">even though all this depends on device firmware but in general you can tell me.</span></div><div><span style="white-space:pre">Thanks in advance.</span></div><div><span style="white-space:pre"><br> </span></div><div><span style="white-space:pre">Thanks </span></div><div><span style="white-space:pre">david</span></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 2, 2013 at 12:57 PM, Bjørn Mork <span dir="ltr"><<a href="mailto:bjorn@mork.no" target="_blank">bjorn@mork.no</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">david preetham <<a href="mailto:preetham.david@gmail.com">preetham.david@gmail.com</a>> writes:<br> <br> > Hi Bjorn Thanks for the reply.<br> ><br> > Can i know which are equivalent drivers can load for ndis interface in<br> > huawei E3121 device?<br> > The network interface is qmi + ncm based.<br> <br> </div>It is? Haven't heard about that combination before. Do you have a<br> "lsusb -v" ouput for that device. Huawei are nice enough to use the<br> subclass and protocol fields to separate different function types. I<br> wonder what this device says..<br> <div class="im"><br> > will cdc_ncm for data plane and cdc_wdm for control interface will work?<br> > Which driver handling qmi and ncm protocol.<br> <br> </div>This is getting a bit ugly. But Enrico Mioso has created a NCM driver<br> similar to qmi_wwan, exposing the embedded management channel as a<br> /dev/cdc-wdmX device: <a href="http://patchwork.ozlabs.org/patch/269325/" target="_blank">http://patchwork.ozlabs.org/patch/269325/</a><br> <br> The driver was made for modems using AT commands on the management<br> channel, but it should work equally well with QMI. I guess it will be<br> up to ModemManager to guess the protocol based on either probing or<br> device ID... The driver won't know.<br> <br> But this driver is not yet merged. It is work in progress. You'll need<br> the two other patches in the series if you want to test it now:<br> <br> <a href="http://patchwork.ozlabs.org/patch/269327/" target="_blank">http://patchwork.ozlabs.org/patch/269327/</a><br> <a href="http://patchwork.ozlabs.org/patch/269326/" target="_blank">http://patchwork.ozlabs.org/patch/269326/</a><br> <span class="HOEnZb"><font color="#888888"><br> <br> Bjørn<br> </font></span></blockquote></div><br></div>