From mboxrd@z Thu Jan 1 00:00:00 1970 From: Enrico Mioso Subject: Re: Is this 32-bit NCM? Date: Sun, 30 Nov 2014 11:39:53 +0100 (CET) Message-ID: References: <87ppc957h1.fsf@nemi.mork.no> <874mtl55ar.fsf@nemi.mork.no> <54781523.6030600@audiocodes.com> <54783443.50700@audiocodes.com> <54783A1D.3090607@audiocodes.com> <54783F84.20105@audiocodes.com> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1832256474-1417343995=:1972" Cc: Eli Britstein , linux-usb@vger.kernel.org, "youtux@gmail.com" , Midge Shaojun Tan , "netdev@vger.kernel.org" , Kevin Zhu , =?ISO-8859-15?Q?Bj=F8rn_Mork?= To: Alex Strizhevsky Return-path: Received: from mail-wi0-f169.google.com ([209.85.212.169]:41912 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751051AbaK3Kj0 (ORCPT ); Sun, 30 Nov 2014 05:39:26 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1832256474-1417343995=:1972 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT My impression guys is that this is not cdc_ncm protocol. Look how many short packets you can see in there. Without any ncm signature. right? On Sun, 30 Nov 2014, Alex Strizhevsky wrote: ==Date: Sun, 30 Nov 2014 05:22:20 ==From: Alex Strizhevsky ==To: Mrkiko Rs ==Cc: Eli Britstein , linux-usb@vger.kernel.org, == "youtux@gmail.com" , == Midge Shaojun Tan , == "netdev@vger.kernel.org" , == Kevin Zhu , Bjørn Mork ==Subject: Re: Is this 32-bit NCM? == == ==Hi Enrico, == ==Actually I have two dongles with different firmwares (23.128.00.00.00 & ==21.286.03.01.209). ==Probably have sent to you the USB  capture with the first one. == ==In fact we have to make work the second one, this dongle has relevant SW. == ==On Nov 30, 2014 3:13 AM, "Enrico Mioso" wrote: == Hi guys. == Sorry for the late our but ... I was trying to figure out == something new about == this dongle. == I also searched for it in my city shops without finding it == actually. == But then I came back and ... tried to look at some things. == == Alex, Kevin: in the Windows USB captures you sent me (and that I == sent on the == List), I can notiche something very strange. == with a shell on a computer connected to a test device I can see == the following: == at+gmr == 21.286.03.01.209 == OK == and so why in the Windows sniff the dongle answers to the same == question == something like == 23.128.00.00.00 == ? == Alex - was it the same dongle? == Kevin or anyone: can you use putty to interact with the dongle == under Windows == and type some commands, like: == at+gmr == and other similar commands? == If the dongle reports different firmware versions under Linux == and Windows, then == guys... we need to figure out the Windows switch message. == Overmore - in the device installation sh*t, you can see there is == a firmware == updater... Why? == == Alex: I used the == at^reset == command to get the modem back to normal state once; and so it == restored the == nvram to default or something. == If you reconnect it to windows ... i hope it gets re-setup as == before. == But - nothing harmful to the device, only to it's settings, == sorry. == I restored the relevant settings and it connects again, but no == dhcp. But - be == peaceful: other modems out there seems to not get dhcp anyway. == this is the state the modem arrives when you buy it, so windows == should know == Wwhat To Say To The Modem (TM). == Another thing - note that: == [14170.048693] cdc_ncm 1-2:1.2: GET_MAX_DATAGRAM_SIZE failed == == Any ideas, comments, suggestions are highly appreciated guys. == Of any type. == == Bjorn - unfortunately it seems this problem is related to E3727 == and E3276 == sticks; they can get IP from DHCP but not go ahead. == == == --8323328-1832256474-1417343995=:1972--