Netgear AC327U USB mobile broadband issues

Hi Everyone!
i just purchase **Netgear AC327U ** usb broadband dongle. it is officially supported for Windows and Mac. I am using opensuse 13.1.
when I plugged in the dongle, the device is not detected in network manager, instead one drive with label Netgear USB modem is detected. i am unable to eject it.
in netgear website, i found one article that suggest installing direct ip driver. but the real problem is that they have only drivers upto kernel 3.0.xx. i tried compiling the driver but the make command returned for each line of code returned “Command not found”. i think that is because of code of driver because these are only supported till kernel version 3.0.xx.
i tried google, but did not found any thing useful.
i am sure i will get some help here.
any help is highly appreciated.
thanks

Can you please post which exact model this is?

lsusb

And check whether NetworkManager is actually activated, in YaST->Network Devices->Network Services->Global Options.

Knowing the chipset details is useful here. It is likely that you’ll need to install the latest ‘usb_modeswitch-data’ package to get this device mode-switched properly.

FWIW, have a read of this thread

http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2134&sid=253a6124de677fada76c817531c375ad

thanks for the reply. my NetworkManager is activated.
and output of the command is as follows:

# lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:6321 Microdia 
Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 002 Device 005: ID 2077:a003

Also usb_modswitch is installed and updated.
still the usb modem is not detected.

Well, one thing that your output does show is that the modem device is activated (by usb_modeswitch)

Bus 002 Device 005: ID 2077:a003

so at least you shou;ldn’t be getting the storage device notification any longer.

With the device plugged in, what is returned by the following?

ls -l /dev/ttyUSB*

I’m also curious about which driver is in use

usb-devices

and just in case this device behaves as a network device (some do), observe

/sbin/ifconfig

thanks for reply!

this command returns

ls -l /dev/ttyUSB*
ls: cannot access /dev/ttyUSB*: No such file or directory

this is just after i get the following:

# lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:6321 Microdia 
Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 002 Device 005: ID 2077:a003

it was strange. i manually checked the directory i didn’t find any ttyUSB only ttysXX.
also device is not detected in network manager.

I’m also curious about which driver is in use

usb-devices

this returns:

 # usb-devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.11
S:  Manufacturer=Linux 3.11.10-17-desktop ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1a.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0c45 ProdID=6321 Rev=11.11
S:  Manufacturer=DCPKP01BI2FLN6
S:  Product=HP Webcam-101
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T:  Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#=  5 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=3005 Rev=00.01
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.11
S:  Manufacturer=Linux 3.11.10-17-desktop ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1d.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=2077 ProdID=a003 Rev=00.00
S:  Manufacturer=  
S:  Product=Netgear Aircard 3G USB Modem
S:  SerialNumber=1234567890ABCDEF
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
I:  If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

and just in case this device behaves as a network device (some do), observe

/sbin/ifconfig

This returns,(currently, using wireless network):

# /sbin/ifconfig
eno1      Link encap:Ethernet  HWaddr AC:16:2D:58:F1:1E  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)

wlo1      Link encap:Ethernet  HWaddr 9C:B7:0D:B6:FE:2F  
          inet addr:192.168.43.231  Bcast:192.168.43.255  Mask:255.255.255.0
          inet6 addr: fe80::9eb7:dff:feb6:fe2f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4772 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4298 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3292558 (3.1 Mb)  TX bytes:687998 (671.8 Kb)


Maybe “option” is the most likely candidate driver for this modem, but unfortunately up to kernel 3.17.3

linux-a2yg:/home/etabeta # modinfo option |grep v2077
alias:          usb:v2077p7001d*dc*dsc*dp*ic*isc*ip*in*

“pa003” is not recognized and engaged for “v2077”, so this specific model is “too new” to the kernel?
Maybe it is possible to force, one way or the other, but I don’t know that product.

Okay, so there is no driver binding to the modem. This is the same situation as reported in this Draisberghof thread.

Hard to say. I note that other Netgear AirCard devices are supported by the sierra driver, but of course the chipsets are different.

It is possible to add a chipset temporarily to modules.alias (for experimentation purposes), but there is no guarantee of success. I guess there is no harm in trying.

echo "alias usb:v2077pA003d*dc*dsc*dp*ic*isc*ip*in* option" >> /lib/modules/<your_kernel_version>/modules.alias

For example, I did that (using kernel 3.11.10-21-desktop), then check with

cat /lib/modules/3.11.10-21-desktop/modules.alias|grep 2077
alias usb:v2077p7001d*dc*dsc*dp*ic*isc*ip*in* option
alias usb:v2077pA003d*dc*dsc*dp*ic*isc*ip*in* option

The next step would to try plugging in the device and noting whether driver is loaded and /dev/ttyUSB* is present.

after performing

 echo "alias usb:v2077pa003d*dc*dsc*dp*ic*isc*ip*in* option" >> /lib/modules/3.11.10-17-desktop/modules.alias

and checking

# cat /lib/modules/3.11.10-17-desktop/modules.alias|grep 2077
alias usb:v2077p7001d*dc*dsc*dp*ic*isc*ip*in* option
alias usb:v2077pA003d*dc*dsc*dp*ic*isc*ip*in* option
alias usb:v2077pA003d*dc*dsc*dp*ic*isc*ip*in* option

but after plugging device

# ls -l /dev/ttyUSB*
ls: cannot access /dev/ttyUSB*: No such file or directory

Well, that’s about as far as I can go with offering any advice. Either the manufacturer will need to provide a driver, or you could try contacting the author of the option GSM modem driver for advice

modinfo option

You can search for developer contact details here too (Matthias Uriichs)
http://www.kernelhub.org/?p=7&dev=1486&mbox_type=2

According to this link the AC327U is using the Qualcomm MSM6290 chipset that has been around since 2007 and is used in a number of sticks, including e.g. Huawei E1762 according to this or, apparently, even the E173 I’m using to write this.
The Qualcomm datasheet is available over the net. My E173 gives (pre and post-switching):

etabeta@linux-a2yg:~> dmesg |grep 12d1
    8.628855] usb 2-3: New USB device found, idVendor=12d1, idProduct=1c0b
   24.333465] usb 2-3: New USB device found, idVendor=12d1, idProduct=1c07

but usb_modeswitch-2.2.0-7.1. (or newer) is needed because of bug903753.
Hope this may help.

thanks!
my version is usb_modeswitch-2.2.0-7.1.
but nothing returns in

dmesg |grep 12d1

of course, this is the dmesg for a Huawei (v12d1) stick. This was only to point out that the chipset in the AC327U is very common, and usually binds to the “option” driver…

Hi,
I am able to switch and connect to the modem with the help of sakis3g, though it seems that sakis3g is not maintained anymore.
After switching ttyusbxx were generated.
But even after connecting I am not able to use Internet.
Any idea?

If you are getting connected, the next step is to find out what the routing table looks like, and check that you have a name server assigned

netstat -r
grep -i name /etc/resolv.conf

Can you ping an internet server by IP address? (For example, the primary google DNS server at 8.8.8.8)

ping 8.8.8.8

Then try pinging by domain name

ping google.com

thanks, it seems to be problem with resolve.conf, but not sure how to fix this

netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         10.64.64.64     0.0.0.0         UG        0 0          0 ppp0
10.64.64.64     *               255.255.255.255 UH        0 0          0 ppp0

but nothing returne on

 grep -i name /etc/resolv.conf
I checked it manually, and found nameserver 192.168.43.1 there, I tried adding nameserver 127.0.0.1 as well. but all other commands returned same before and after adding nameserver.
now it is like this

grep -i name /etc/resolv.conf
nameserver 192.168.43.1
nameserver 127.0.0.1



yes, i was able to ping 8.8.8.8

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=677 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=828 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=1458 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=1348 ms
^Z
[1]+ Stopped ping 8.8.8.8



but not google.com


ping google.com
ping: unknown host google.com

The usual trick is to remove the file completely, and let the network manager regenerate, but since you’re using a script, I’m not sure how it will behave. No harm trying I guess. When you next connect, your mobile broadband provider’s nameserver should be listed.

Alternatively, you could just manually add a publically avaialble one eg 8.8.8.8, or one of these perhaps

https://www.grc.com/dns/alternatives.htm

echo "nameserver 8.8.8.8" > /etc/resolv.conf

Then names should be resolved ok.

Thanks for the help.
This resolves the issue.