Problem with E392 connection using wwan0

[Madhan]

hi alex , bjorn ,
Can you just tell me is there something to be done after setting the IP and
gw manually (using AT^DHCP?) ?
I update my resolv.conf too .But still i was not able to connect to network
. ping fails .


Regards ,
Madhan


On Fri, Aug 16, 2013 at 7:11 PM, Madhan <madhan.mepco at gmail.com> wrote:

> hi bjorn ,
>
> >Which kernel (i.e. driver) version do you use?
> *I tried in 3.5 and also in 3.10 *, in both cases i was not successful
> using AT
>
> >Why don't you want to use it?
> *I am trying to just sort out , what qmi connection is doing in addition
> after getting the AT .
>
> *
> Cause when I was *sniffing usb* i was able to find the same even when i
> am using *qmicli , this also
> uses AT^DHCP? command  *
>
> +aleksander : Can you please give us some suggestions
>
>
> On Fri, Aug 16, 2013 at 6:19 PM, Bjørn Mork <bjorn at mork.no> wrote:
>
>> Madhan <madhan.mepco at gmail.com> writes:
>>
>> > hi ,
>> > I have used qmi_wwan and cdc_wdm for my device
>> >
>> > Sending At commands through /dev/ttyUSB0(option)
>> >      a) *AT^NDISDUP*=1,1,"my_apn"
>> >         ok.
>> >      b)* AT^DHCP?*
>> >         gives me IP also
>> >
>> > But when I set the IP with the provided netmask , dns and gw
>> > I am *not able to connec*t to internet .
>> >
>> >
>> > But when I use the "libqmi"
>> > *qmicli -*d /dev/cdc-wdm0 --wds-start-network=airtelgprs.com,PAP,"",""
>> >  --client-no-release-cid
>> >
>> > I am able to *successfully connect *to network using my network
>> interface .
>> >
>> > Cant I do the same without using qmicli ?
>> > Is there anything in specific which establishes connection after
>> getting IP
>>
>> Which kernel (i.e. driver) version do you use? A few fixes for known
>> firmware bugs went into v3.9 and the still maintained stable kernels
>> where they could be applied without changes.  I could not make my E392
>> work using AT^NDISDUP without some of these fixes.
>>
>> But I do believe the QMI connection method is more stable on these
>> modems.   The Windows driver/application use it, so that's the mode
>> getting any testing.  The AT command method might work, but I recommend
>> using QMI.  As you have already found out, it is more reliable.  Why
>> don't you want to use it?
>>
>>
>> Bjørn
>>
>
>
>
> --
> Madhan
>



-- 
Madhan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20130822/06a633e0/attachment.html>