From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Mrkiko Rs <mrkiko.rs@gmail.com>
Cc: "Dan Williams" <dcbw@redhat.com>, "Bjørn Mork" <bjorn@mork.no>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Oliver Neukum" <oliver@neukum.org>
Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
Date: Fri, 14 Mar 2014 10:01:35 +0200 [thread overview]
Message-ID: <20140314080135.GY3200@reaktio.net> (raw)
In-Reply-To: <-6080561389566060558@unknownmsgid>
On Fri, Mar 14, 2014 at 08:58:03AM +0100, Mrkiko Rs wrote:
> Which dhcp client are you using?
>
"dhclient" in fedora 20..
-- Pasi
> Inviato da iPhone
>
> > Il giorno 14/mar/2014, alle ore 08:55, "Pasi Kärkkäinen" <pasik@iki.fi> ha scritto:
> >
> >> On Fri, Mar 14, 2014 at 12:08:12AM +0200, Pasi Kärkkäinen wrote:
> >>> On Thu, Mar 13, 2014 at 04:41:47PM -0500, Dan Williams wrote:
> >>>> On Thu, 2014-03-13 at 22:25 +0200, Pasi Kärkkäinen wrote:
> >>>>> On Mon, Nov 04, 2013 at 09:50:46AM +0100, Bjørn Mork wrote:
> >>>>>
> >>>>> [quote Enrico Mioso]
> >>>>>
> >>>>> So this is a new, revised, edition of the huawei_cdc_ncm.c driver, which
> >>>>> supports devices resembling the NCM standard, but using it also as a mean
> >>>>> to encapsulate other protocols, as is the case for the Huawei E3131 and
> >>>>> E3251 modem devices.
> >>>>
> >>>> Hello,
> >>>>
> >>>> I'm trying to use Huawei E3276 4G/LTE USB dongle with Linux 3.13.6 kernel,
> >>>> and thus i'm using the new huawei_cdc_ncm driver.
> >>>>
> >>>> I'm using the /dev/cdc-wdm0 device to send AT commands to it, and that seems to work,
> >>>> so the dongle seems like it's connected (also the LED on the dongle suggests it's connected).
> >>>>
> >>>> .. the problem is the wwan0 interface (well, udev renames it to wwp0s26u1u5i1) doesn't work.
> >>>> Launching a dhcp client on the wwp0s26u1u5i1 doesn't get any IP address.
> >>>>
> >>>> Any tips how to troubleshoot this?
> >>
> >> Hi,
> >>
> >>> Which AT commands are you using to start the data connection?
> >>
> >> I've been using:
> >>
> >> ATQ0 V1 E1 S0=0
> >> AT^NDISDUP=1,1,"internet"
> >> AT^DHCP?
> >
> > Oh, I forgot to mention.. after I send AT^NDISDUP=1,1,"internet" I get this:
> >
> > ^NDISSTAT:1,,,"IPV4"
> >
> > .. which to my understanding means it's connected (1==connected).
> > Also sending AT^NDISSTATQRY? results in:
> >
> > ^NDISSTATQRY: 1,,,"IPV4"
> >
> >
> > But I can't get an IP with dhcp client on the wwan0 interface..
> >
> >
> > -- Pasi
> >
> >
> >>
> >>> I believe Huawei says that DHCP on the network port is only supported if
> >>> network port's USB interface has Class 0x2 + SubClass [0x6 | 0xd] +
> >>> Protocol 0x0.
> >>
> >> # lsusb | grep -i huawei
> >> Bus 001 Device 010: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard
> >>
> >> # lsusb -t
> >> ..
> >> |__ Port 5: Dev 10, If 0, Class=Vendor Specific Class, Driver=option, 480M
> >> |__ Port 5: Dev 10, If 1, Class=Vendor Specific Class, Driver=huawei_cdc_ncm, 480M
> >> |__ Port 5: Dev 10, If 2, Class=Mass Storage, Driver=usb-storage, 480M
> >> |__ Port 5: Dev 10, If 3, Class=Mass Storage, Driver=usb-storage, 480M
> >>
> >> Bus 001 Device 010: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard
> >> Device Descriptor:
> >> bLength 18
> >> bDescriptorType 1
> >> bcdUSB 2.00
> >> bDeviceClass 0 (Defined at Interface level)
> >> bDeviceSubClass 0
> >> bDeviceProtocol 0
> >> bMaxPacketSize0 64
> >> idVendor 0x12d1 Huawei Technologies Co., Ltd.
> >> idProduct 0x1506 Modem/Networkcard
> >> bcdDevice 1.02
> >> iManufacturer 2 HUAWEI Technology
> >> iProduct 1 HUAWEI Mobile
> >> iSerial 0
> >> bNumConfigurations 1
> >> Configuration Descriptor:
> >> bLength 9
> >> bDescriptorType 2
> >> wTotalLength 173
> >> bNumInterfaces 4
> >> bConfigurationValue 1
> >> iConfiguration 3 Huawei Configuration
> >> bmAttributes 0x80
> >> (Bus Powered)
> >> MaxPower 500mA
> >> Interface Descriptor:
> >> bLength 9
> >> bDescriptorType 4
> >> bInterfaceNumber 0
> >> bAlternateSetting 0
> >> bNumEndpoints 2
> >> bInterfaceClass 255 Vendor Specific Class
> >> bInterfaceSubClass 2
> >> bInterfaceProtocol 18
> >> iInterface 0
> >> ** UNRECOGNIZED: 05 24 00 10 01
> >> ** UNRECOGNIZED: 04 24 02 02
> >> ** UNRECOGNIZED: 05 24 01 00 00
> >> ** UNRECOGNIZED: 06 24 06 00 00 00
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x81 EP 1 IN
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 32
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x01 EP 1 OUT
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 32
> >> Interface Descriptor:
> >> bLength 9
> >> bDescriptorType 4
> >> bInterfaceNumber 1
> >> bAlternateSetting 0
> >> bNumEndpoints 1
> >> bInterfaceClass 255 Vendor Specific Class
> >> bInterfaceSubClass 2
> >> bInterfaceProtocol 22
> >> iInterface 0
> >> ** UNRECOGNIZED: 05 24 00 10 01
> >> ** UNRECOGNIZED: 06 24 1a 00 01 1f
> >> ** UNRECOGNIZED: 0d 24 0f 04 0f 00 00 00 ea 05 03 00 01
> >> ** UNRECOGNIZED: 05 24 06 01 01
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x82 EP 2 IN
> >> bmAttributes 3
> >> Transfer Type Interrupt
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0040 1x 64 bytes
> >> bInterval 5
> >> Interface Descriptor:
> >> bLength 9
> >> bDescriptorType 4
> >> bInterfaceNumber 1
> >> bAlternateSetting 1
> >> bNumEndpoints 3
> >> bInterfaceClass 255 Vendor Specific Class
> >> bInterfaceSubClass 2
> >> bInterfaceProtocol 22
> >> iInterface 0
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x82 EP 2 IN
> >> bmAttributes 3
> >> Transfer Type Interrupt
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0040 1x 64 bytes
> >> bInterval 5
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x83 EP 3 IN
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 32
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x02 EP 2 OUT
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 32
> >> Interface Descriptor:
> >> bLength 9
> >> bDescriptorType 4
> >> bInterfaceNumber 2
> >> bAlternateSetting 0
> >> bNumEndpoints 2
> >> bInterfaceClass 8 Mass Storage
> >> bInterfaceSubClass 6 SCSI
> >> bInterfaceProtocol 80 Bulk-Only
> >> iInterface 0
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x03 EP 3 OUT
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 0
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x84 EP 4 IN
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 0
> >> Interface Descriptor:
> >> bLength 9
> >> bDescriptorType 4
> >> bInterfaceNumber 3
> >> bAlternateSetting 0
> >> bNumEndpoints 2
> >> bInterfaceClass 8 Mass Storage
> >> bInterfaceSubClass 6 SCSI
> >> bInterfaceProtocol 80 Bulk-Only
> >> iInterface 0
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x04 EP 4 OUT
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 0
> >> Endpoint Descriptor:
> >> bLength 7
> >> bDescriptorType 5
> >> bEndpointAddress 0x85 EP 5 IN
> >> bmAttributes 2
> >> Transfer Type Bulk
> >> Synch Type None
> >> Usage Type Data
> >> wMaxPacketSize 0x0200 1x 512 bytes
> >> bInterval 0
> >> Device Qualifier (for other device speed):
> >> bLength 10
> >> bDescriptorType 6
> >> bcdUSB 2.00
> >> bDeviceClass 0 (Defined at Interface level)
> >> bDeviceSubClass 0
> >> bDeviceProtocol 0
> >> bMaxPacketSize0 64
> >> bNumConfigurations 1
> >> Device Status: 0x0000
> >> (Bus Powered)
> >>
> >>
> >>> Lastly, I think the E3276 has a couple of different "modes" that it can
> >>> switch into with usb_modeswitch too, and only some modes expose the
> >>> right network interface. What modeswitch command is getting sent to the
> >>> device?
> >>
> >> This is on Fedora 20.
> >>
> >> Mar 13 23:56:36 localhost logger: usb_modeswitch: using overriding config file /etc/usb_modeswitch.d/12d1:14fe; make sure this is intended
> >> Mar 13 23:56:36 localhost logger: usb_modeswitch: please report any new or corrected settings; otherwise, check for outdated files
> >> Mar 13 23:56:36 localhost usb_modeswitch: switching device 12d1:14fe on 001/009
> >> Mar 13 23:56:37 localhost logger: usb_modeswitch: switched to 12d1:1506 on 001/010
> >>
> >> # cat /etc/usb_modeswitch.d/12d1:14fe
> >>
> >> # T-Mobile NL (Huawei E352)
> >>
> >> TargetVendor= 0x12d1
> >> TargetProductList="1506,150f,151d"
> >>
> >> MessageContent="55534243123456780000000000000011062000000100000000000000000000"
> >>
> >>
> >> # grep -i e3276 /etc/usb_modeswitch.d/*
> >> /etc/usb_modeswitch.d/12d1:156a:# Huawei E3276s-151 and E3251
> >>
> >>
> >> # cat /etc/usb_modeswitch.d/12d1:156a
> >>
> >> # Huawei E3276s-151 and E3251
> >>
> >> TargetVendor= 0x12d1
> >> TargetProductList="156b,156c"
> >>
> >> MessageContent="55534243123456780000000000000011062000000100000000000000000000"
> >>
> >>
> >>
> >> Hopefully that was enough information..
> >>
> >> Thanks!
> >>
> >> -- Pasi
> >>
> >>
> >>> Dan
> >>>
> >>>> I'm seeing "RX errors" listed for the interface in "ifconfig -a" output.. is that normal?
> >>>>
> >>>> The device in question is (ATI command output):
> >>>>
> >>>> Manufacturer: huawei
> >>>> Model: E3276
> >>>> Revision: 21.263.03.00.07
> >>>> IMEI: 863XYZXYZXYZXYZ
> >>>> +GCAP: +CGSM,+DS,+ES
> >>>>
> >>>> Thanks!
> >>>>
> >>>> -- Pasi
> >>>>
> >>>>
> >>>>> Some precisations are needed however - and I encourage discussion on this: and
> >>>>> that's why I'm sending this message with a broader CC.
> >>>>> Merging those patches might change:
> >>>>> - the way Modem Manager interacts with those devices
> >>>>> - some regressions might be possible if there are some unknown firmware
> >>>>> variants around (Franko?)
> >>>>>
> >>>>> First of all: I observed the behaviours of two devices.
> >>>>> Huawei E3131: this device doesn't accept NDIS setup requests unless they're
> >>>>> sent via the embedded AT channel exposed by this driver.
> >>>>> So actually we gain funcionality in this case!
> >>>>>
> >>>>> The second case, is the Huawei E3251: which works with standard NCM driver,
> >>>>> still exposing an AT embedded channel. Whith this patch set applied, you gain
> >>>>> some funcionality, loosing the ability to catch standard NCM events for now.
> >>>>> The device will work in both ways with no problems, but this has to be
> >>>>> acknowledged and discussed. Might be we can develop this driver further to
> >>>>> change this, when more devices are tested.
> >>>>>
> >>>>> We where thinking Huawei changed their interfaces on new devices - but probably
> >>>>> this driver only works around a nice firmware bug present in E3131, which
> >>>>> prevented the modem from being used in NDIS mode.
> >>>>>
> >>>>> I think committing this is definitely wortth-while, since it will allow for
> >>>>> more Huawei devices to be used without serial connection. Some devices like the
> >>>>> E3251 also, reports some status information only via the embedded AT channel,
> >>>>> at least in my case.
> >>>>> Note: I'm not subscribed to any list except the Modem Manager's one, so please
> >>>>> CC me, thanks!!
> >>>>>
> >>>>> [/quote]
> >>>>>
> >>>>> Enrico Mioso (3):
> >>>>> net: cdc_ncm: Export cdc_ncm_{tx,rx}_fixup functions for re-use
> >>>>> net: huawei_cdc_ncm: Introduce the huawei_cdc_ncm driver
> >>>>> net: cdc_ncm: remove non-standard NCM device IDs
> >>>>>
> >>>>> drivers/net/usb/Kconfig | 15 +++
> >>>>> drivers/net/usb/Makefile | 1 +
> >>>>> drivers/net/usb/cdc_ncm.c | 17 +--
> >>>>> drivers/net/usb/huawei_cdc_ncm.c | 230 ++++++++++++++++++++++++++++++++++++++
> >>>>> include/linux/usb/cdc_ncm.h | 3 +
> >>>>> 5 files changed, 253 insertions(+), 13 deletions(-)
> >>>>> create mode 100644 drivers/net/usb/huawei_cdc_ncm.c
> >>>>>
> >>>>> --
> >>>>> 1.7.10.4
> >>>>>
> >>>>> --
> >>>>> To unsubscribe from this list: send the line "unsubscribe netdev" in
> >>>>> the body of a message to majordomo@vger.kernel.org
> >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>>> --
> >>>> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> >>>> the body of a message to majordomo@vger.kernel.org
> >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>>
> >>>
prev parent reply other threads:[~2014-03-14 8:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 8:50 [PATCH net-next v6 0/3] The huawei_cdc_ncm driver Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 1/3] net: cdc_ncm: Export cdc_ncm_{tx,rx}_fixup functions for re-use Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 2/3] net: huawei_cdc_ncm: Introduce the huawei_cdc_ncm driver Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 3/3] net: cdc_ncm: remove non-standard NCM device IDs Bjørn Mork
2013-11-05 20:22 ` [PATCH net-next v6 0/3] The huawei_cdc_ncm driver David Miller
2014-03-13 20:25 ` [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem Pasi Kärkkäinen
2014-03-13 21:41 ` Dan Williams
2014-03-13 22:08 ` Pasi Kärkkäinen
2014-03-14 7:55 ` Pasi Kärkkäinen
[not found] ` <20140314075548.GX3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-14 8:34 ` Bjørn Mork
2014-03-14 8:41 ` Pasi Kärkkäinen
2014-03-14 8:58 ` Bjørn Mork
2014-03-14 9:05 ` Pasi Kärkkäinen
2014-03-14 9:24 ` Enrico Mioso
2014-03-14 9:24 ` Bjørn Mork
[not found] ` <87ob19nndo.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-14 9:37 ` Enrico Mioso
2014-03-14 12:59 ` Pasi Kärkkäinen
2014-03-14 13:33 ` Bjørn Mork
2014-03-14 14:25 ` Pasi Kärkkäinen
2014-03-14 17:16 ` Dan Williams
[not found] ` <1394817415.5829.6.camel-ZWpNTBV2bRGs1BDpvl8NfQ@public.gmane.org>
2014-03-14 17:33 ` Pasi Kärkkäinen
[not found] ` <20140314142559.GD3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 11:31 ` Bjørn Mork
2014-03-17 11:59 ` Pasi Kärkkäinen
[not found] ` <20140317115919.GK3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 12:45 ` Pasi Kärkkäinen
2014-03-17 13:15 ` Bjørn Mork
2014-03-17 13:17 ` Pasi Kärkkäinen
[not found] ` <20140317131731.GM3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 14:23 ` Bjørn Mork
[not found] ` <87txawlx9h.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-17 14:46 ` Enrico Mioso
2014-03-17 15:05 ` Pasi Kärkkäinen
2014-03-17 15:07 ` Bjørn Mork
[not found] ` <87k3btm57a.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-17 12:56 ` Bjørn Mork
2014-03-17 13:10 ` Bjørn Mork
[not found] ` <385896107.16855.1394783754007.JavaMail.mobile-sync@vcpd12>
2014-03-14 7:58 ` Mrkiko Rs
2014-03-14 8:01 ` Pasi Kärkkäinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140314080135.GY3200@reaktio.net \
--to=pasik@iki.fi \
--cc=bjorn@mork.no \
--cc=dcbw@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=mrkiko.rs@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).