<div dir="ltr"><div>hi alex , bjorn , <br>Can you just tell me is there something to be done after setting the IP and gw manually (using AT^DHCP?) ? <br></div><div>I update my resolv.conf too .But still i was not able to connect to network . ping fails . <br>
<br><br></div><div>Regards , <br></div><div>Madhan<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 7:11 PM, Madhan <span dir="ltr"><<a href="mailto:madhan.mepco@gmail.com" target="_blank">madhan.mepco@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>hi bjorn , <br><div class="im"><br>>Which kernel (i.e. driver) version do you use?<br>
</div></div><b>I tried in 3.5 and also in 3.10 </b>, in both cases i was not successful using AT <br><div class="im"><br>>Why don't you want to use it?<br>
</div></div><b>I am trying to just sort out , what qmi connection is doing in addition after getting the AT . <br><br></b></div>Cause when I was <b>sniffing usb</b> i was able to find the same even when i am using <b>qmicli , this also <br>
uses AT^DHCP? command </b><br><br></div>+aleksander : Can you please give us some suggestions <br></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 6:19 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>Madhan <<a href="mailto:madhan.mepco@gmail.com" target="_blank">madhan.mepco@gmail.com</a>> writes:<br>
<br>
> hi ,<br>
> I have used qmi_wwan and cdc_wdm for my device<br>
><br>
> Sending At commands through /dev/ttyUSB0(option)<br>
</div>> a) *AT^NDISDUP*=1,1,"my_apn"<br>
> ok.<br>
> b)* AT^DHCP?*<br>
<div>> gives me IP also<br>
><br>
> But when I set the IP with the provided netmask , dns and gw<br>
</div>> I am *not able to connec*t to internet .<br>
<div>><br>
><br>
> But when I use the "libqmi"<br>
</div>> *qmicli -*d /dev/cdc-wdm0 --wds-start-network=<a href="http://airtelgprs.com" target="_blank">airtelgprs.com</a>,PAP,"",""<br>
> --client-no-release-cid<br>
><br>
> I am able to *successfully connect *to network using my network interface .<br>
<div>><br>
> Cant I do the same without using qmicli ?<br>
> Is there anything in specific which establishes connection after getting IP<br>
<br>
</div>Which kernel (i.e. driver) version do you use? A few fixes for known<br>
firmware bugs went into v3.9 and the still maintained stable kernels<br>
where they could be applied without changes. I could not make my E392<br>
work using AT^NDISDUP without some of these fixes.<br>
<br>
But I do believe the QMI connection method is more stable on these<br>
modems. The Windows driver/application use it, so that's the mode<br>
getting any testing. The AT command method might work, but I recommend<br>
using QMI. As you have already found out, it is more reliable. Why<br>
don't you want to use it?<br>
<span><font color="#888888"><br>
<br>
Bjørn<br>
</font></span></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Madhan<input type="hidden"><input type="hidden"><div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>Madhan<input type="hidden"><input type="hidden"><div></div>
</div>