You are not logged in.

#1 2013-08-22 14:07:54

Shocker
Member
From: Europe
Registered: 2013-08-22
Posts: 8

Network Manager fails to connect with Sierra Wireless 3G/4G modem

Hi,

I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.

  • Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.

  • Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.

I would be grateful for any help.


Sierra Wireless AirCard 310U (USB 3G Modem) log:

...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info>  Simple connect started...
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info>  Simple connect state (3/8): Enable
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn>  (ttyUSB2): port attributes not fully set
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info>  Simple connect state (4/8): Wait to get fully enabled
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info>  Simple connect state (5/8): Register
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info>  (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info>  Simple connect state (6/8): Bearer
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
...

Sierra Wireless AirCard 320U (3G/4G Modem) log:

...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info>  Simple connect started...
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info>  Simple connect state (3/8): Enable
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn>  (ttyUSB3): port attributes not fully set
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn>  (ttyUSB4): port attributes not fully set
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Simple connect state (4/8): Wait to get fully enabled
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Simple connect state (5/8): Register
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Simple connect state (6/8): Bearer
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Simple connect state (7/8): Connect
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info>  Simple connect state (8/8): All done
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
aug 22 13:48:09 AsusN56VZ dhclient[2351]: 
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on   LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on   Socket/fallback
aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info>  Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
...

Last edited by Shocker (2013-09-14 20:08:08)

Offline

#2 2013-09-11 00:04:09

qnm
Member
Registered: 2013-09-11
Posts: 2

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

Hi,

I have this same problem on Fedora 19. Interestingly, it works fine on my F19 live boot which uses a different kernel.

Which kernel version are you using?

/tmp  ᐅ uname -r
3.10.10-200.fc19.x86_64

- Rob

Offline

#3 2013-09-14 20:45:07

Shocker
Member
From: Europe
Registered: 2013-08-22
Posts: 8

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

qnm wrote:

Hi,

I have this same problem on Fedora 19. Interestingly, it works fine on my F19 live boot which uses a different kernel.

Which kernel version are you using?

/tmp  ᐅ uname -r
3.10.10-200.fc19.x86_64

- Rob

I run an update at least once a week. Now I have 3.10.10 kernel, but in older version is the same bug (since > 3.6.10, all 3.7.X, all 3.8.X and 3.9.X).
I haven't tested only linux-lts kernel (3.0.X).
I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...

Fresh log from syslog Linux Mint 15 Cinnamon 64 bit (Sierra AirCard 320U connection successfully):

Sep 14 22:32:10 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) starting connection 'Orange Standard access - with image compression'
Sep 14 22:32:10 acer-aspire NetworkManager[1114]: <info> (wwan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 14 22:32:10 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 14 22:32:10 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) started...
Sep 14 22:32:10 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) complete.
Sep 14 22:32:10 acer-aspire modem-manager[2376]: <info>  (ttyUSB3) opening serial port...
Sep 14 22:32:10 acer-aspire modem-manager[2376]: <warn>  (ttyUSB3): port attributes not fully set
Sep 14 22:32:10 acer-aspire modem-manager[2376]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
Sep 14 22:32:11 acer-aspire modem-manager[2376]: <info>  (ttyUSB3): using PDU mode for SMS
Sep 14 22:32:11 acer-aspire modem-manager[2376]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled)
Sep 14 22:32:11 acer-aspire NetworkManager[1114]: <info> WWAN now enabled by management service
Sep 14 22:32:11 acer-aspire modem-manager[2376]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled -> registered)
Sep 14 22:32:11 acer-aspire modem-manager[2376]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting)
Sep 14 22:32:13 acer-aspire modem-manager[2376]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) starting...
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> (wwan0): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> (wwan0): bringing up device.
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) successful.
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) complete.
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) started...
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> (wwan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 14 22:32:13 acer-aspire kernel: [  203.133621] IPv6: ADDRCONF(NETDEV_UP): wwan0: link is not ready
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> dhclient started with pid 2614
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) complete.
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 14 22:32:13 acer-aspire dhclient: Internet Systems Consortium DHCP Client 4.2.4
Sep 14 22:32:13 acer-aspire dhclient: Copyright 2004-2012 Internet Systems Consortium.
Sep 14 22:32:13 acer-aspire dhclient: All rights reserved.
Sep 14 22:32:13 acer-aspire dhclient: For info, please visit https://www.isc.org/software/dhcp/
Sep 14 22:32:13 acer-aspire dhclient: 
Sep 14 22:32:13 acer-aspire NetworkManager[1114]: <info> (wwan0): DHCPv4 state changed nbi -> preinit
Sep 14 22:32:13 acer-aspire dhclient: Listening on LPF/wwan0/9a:25:9a:9a:02:07
Sep 14 22:32:13 acer-aspire dhclient: Sending on   LPF/wwan0/9a:25:9a:9a:02:07
Sep 14 22:32:13 acer-aspire dhclient: Sending on   Socket/fallback
Sep 14 22:32:13 acer-aspire dhclient: DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 3 (xid=0x572aa046)
Sep 14 22:32:13 acer-aspire avahi-daemon[1080]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::9825:9aff:fe9a:207.
Sep 14 22:32:13 acer-aspire avahi-daemon[1080]: New relevant interface wwan0.IPv6 for mDNS.
Sep 14 22:32:13 acer-aspire avahi-daemon[1080]: Registering new address record for fe80::9825:9aff:fe9a:207 on wwan0.*.
Sep 14 22:32:13 acer-aspire kernel: [  203.331173] IPv6: ADDRCONF(NETDEV_CHANGE): wwan0: link becomes ready
Sep 14 22:32:16 acer-aspire dhclient: DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 4 (xid=0x572aa046)
Sep 14 22:32:16 acer-aspire dhclient: DHCPREQUEST of 10.208.149.238 on wwan0 to 255.255.255.255 port 67 (xid=0x572aa046)
Sep 14 22:32:16 acer-aspire dhclient: DHCPOFFER of 10.208.149.238 from 10.208.149.253
Sep 14 22:32:16 acer-aspire dhclient: DHCPACK of 10.208.149.238 from 10.208.149.253
Sep 14 22:32:16 acer-aspire dhclient: bound to 10.208.149.238 -- renewal in 103869 seconds.
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info> (wwan0): DHCPv4 state changed preinit -> bound
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   address 10.208.149.238
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   prefix 24 (255.255.255.0)
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   gateway 10.208.149.238
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   nameserver '208.67.220.220'
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   nameserver '208.67.222.222'
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   wins '0.0.0.0'
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info>   wins '0.0.0.0'
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 14 22:32:16 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Commit) started...
Sep 14 22:32:16 acer-aspire avahi-daemon[1080]: Joining mDNS multicast group on interface wwan0.IPv4 with address 10.208.149.238.
Sep 14 22:32:16 acer-aspire avahi-daemon[1080]: New relevant interface wwan0.IPv4 for mDNS.
Sep 14 22:32:16 acer-aspire avahi-daemon[1080]: Registering new address record for 10.208.149.238 on wwan0.IPv4.
Sep 14 22:32:17 acer-aspire NetworkManager[1114]: <info> (wwan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 14 22:32:17 acer-aspire NetworkManager[1114]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Commit) complete.
Sep 14 22:32:17 acer-aspire NetworkManager[1114]: <info> (wwan0): device state change: secondaries -> activated (reason 'none') [90 100 0]

Offline

#4 2013-09-14 23:47:48

qnm
Member
Registered: 2013-09-11
Posts: 2

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

Shocker wrote:

I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...

To test, I downgraded my kernel

~  ᐅ uname -r
3.9.5-301.fc19.x86_64.debug

And now I see in messages

Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
Sep 15 09:46:17 localhost modem-manager[757]: <info>  (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost modem-manager[757]: <warn>  (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info>  (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn>  (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info>  (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost modem-manager[757]: <info>  (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost modem-manager[757]: <info>  Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
Sep 15 09:46:19 localhost dhclient[10376]: 
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on   LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on   Socket/fallback
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   address 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   prefix 24 (255.255.255.0)
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   gateway 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   nameserver '10.4.81.103'
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   nameserver '10.4.182.20'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info>   wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.

I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.

Last edited by qnm (2013-09-14 23:48:05)

Offline

#5 2013-09-15 18:38:10

Shocker
Member
From: Europe
Registered: 2013-08-22
Posts: 8

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

qnm wrote:

To test, I downgraded my kernel

~  ᐅ uname -r
3.9.5-301.fc19.x86_64.debug

I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.


You were right... I have found in old mirror of Arch kernel version 3.9.5 and after downgrading the kernel, I can connect, but only with AirCard 320U (obtain dhcp address). AirCard 310U still reboot itself. However signal strength indicator (nm-applet) doesn't work (all the bars are grey). Does it work in Fedora?

Unfortunately I have returned to 3.10.10 kernel version because I have Atheros AR8161 LAN and this work only with the >3.10.2 kernel update, and the latest version of nvidia driver/bbswitch (I have laptop with Optimus technology) require kernel >3.10 too.
For now, back to wvdial sad If you learn something more about this issue let me know...

Offline

#6 2013-09-17 07:17:56

herdus
Member
Registered: 2013-09-17
Posts: 1

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

Shocker,

I had the same problem the other day on kernel 3.10 and it appears the problem is now gone for me on both 3.10 as well as 3.11, which is rather strange. Unfortunately, I cannot exact comment what the fix was as I've made a lot of different config changes moving to not only the latest kernel, but also to i3-wm big_smile

The one thing though I would not mind asking you is - I've noticed that you have the 80-net-name-slot.rules set in you udev (by the whole long line of your wireless device). Think this was introduced in systemd (197) where a rename of the device was done to match your pci, device number, etc... from what I understand.

I'm not entirely sure how you have your configuration, etc... but one thing I would suggest is to bring back your wwan0.
1. run "ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules" as root. This will skip the entire renaming of your wireless device, so you're back to the normal eth0, wlan0, wwan0, etc...
2. Try and use NetworkManager to dhcp against wwan0 again and see if it works.
3. If it doesn't, also try the AT commands options:
    - systemctl stop NetworkManager
    - (optional) - systemctl start dhcpcd?
    - minicom to use /dev/ttyUSB2
    - AT+CFUN=1 to turn on radio
    - AT!SCACT=1,<profile> to start the wireless link.
    - dhclient wwan0
    - Then check your /var/log/messages to see if you've gotten the correct route, etc...
    - Ping - and it should work

Again, I'm not sure if this will fix your issue, but that was one of the things I've done whilst trying to fix the symlink issue for the wpa_supplicant@.service for my wifi, and I only remembered today (whilst out in a cafe) to test and see if skipping the rename of interfaces would fix my USB 4G modem problem - and interesting, it worked for me and now testing on 3.10, it works well as well.

Believe the whole rename stuff is a small problem as per some of the bug reports I've seen (although I'm already on 204, so not sure if I've got a fixed version, or not).

Hope this helps. Would be good to see / confirm the exact workaround.

Offline

#7 2013-09-21 11:55:49

Shocker
Member
From: Europe
Registered: 2013-08-22
Posts: 8

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

herdus wrote:

Shocker,

I had the same problem the other day on kernel 3.10 and it appears the problem is now gone for me on both 3.10 as well as 3.11, which is rather strange. Unfortunately, I cannot exact comment what the fix was as I've made a lot of different config changes moving to not only the latest kernel, but also to i3-wm big_smile

The one thing though I would not mind asking you is - I've noticed that you have the 80-net-name-slot.rules set in you udev (by the whole long line of your wireless device). Think this was introduced in systemd (197) where a rename of the device was done to match your pci, device number, etc... from what I understand.

...

Hope this helps. Would be good to see / confirm the exact workaround.


I did everything as you wrote, but unfortunately it didn't help (with Sierra AirCard 320U modem).
1. Back to the normal names (wwan0 etc.) didn't help - still in journalctl "dhcpcd: timed out"... sad
2. Installing minicom and run the AT commands - I'm able to run the modem (modem blue LED is light up), but the command: dhclient wwan0 (or dhcpcd wwan0) gives a magical result: dhcpcd request timed out... sad

Still, thanks for the reply...

Offline

#8 2013-11-20 04:46:51

Eugene
Member
From: Adelaide, AU
Registered: 2012-11-02
Posts: 12

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

Just the same story here - Telstra's modem.

ati5
Manufacturer: Sierra Wireless, Incorporated
Model: AirCard 320U
Revision: X1_2_2_0AP R2839 CNSZXD00000128 2011/08/05 15:52:41
IMEI: xxxxxxxxxxxxxxxx
IMEI SV: 1
FSN: CCCCCCCCCCCCC
3GPP Release 8
+GCAP: +CGSM

With minicom I can get modem connected, i.e. power led on the modem is blue and data led is green. I can see in minicom that IP address is assigned

at+cgdcont?
+CGDCONT: 1,"IP","telstra.internet","0.0.0.0",0,0
+CGDCONT: 2,"IP","telstra.datapack","0.0.0.0",0,0
+CGDCONT: 3,"IP","telstra.pcpack","0.0.0.0",0,0
+CGDCONT: 4,"IP","telstra.bigpond","0.0.0.0",0,0

OK
AT!SCACT=1,1

OK
at!scpaddr=1
!SCPADDR: 1,"10.109.41.249" 

OK

I can see wwan0 interface but it is not responding to dhclient

[root@arch ~]# ethtool wwan0
Settings for wwan0:
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no
[root@arch]# ifconfig wwan0
wwan0: flags=4227<UP,BROADCAST,NOARP,MULTICAST>  mtu 1500
        ether  6e:cc:e4:32:05:07 txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@arch ~]#

Any advice where to dig?
Thanks.

Offline

#9 2014-01-06 00:18:26

xmd
Member
Registered: 2014-01-06
Posts: 1

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

I had exactly the same problem: Modem (sierrawireless aircard 312u) fully functional, I could see the IP address using AT commands etc, but I couldn't get wwan0 to automagically or manually configure. dhclient wwan0 would timeout without receiving addresses.

My searching led me to the conclusion that there is something odd going on with the driver. I saw references on some BSD forums to a sierra driver 'faking' a DHCP server for example. In some ways this makes sense as the modem itself has clearly already negotiated an IP address, and presumably in doing so picked up DNS addresses also. I couldn't get my device to communicate on the net even when I manually set up the interface with the address given through the AT command interface. This was because I couldn't work out how to get the correct gateway or DNS addresses (using a windows box I could see these addresses being dynamically assigned). If anyone ever works out how to get these addresses using AT commands or similar I'd really like to know - especially as being able to manually set up the interface would be useful in the event you run into this issue and don't have other means of internet access...

In the end I ran an upgrade and then 'sudo dhclient wwan0' just started working. For reference I am running debian sid. I can see this is not exactly the right forum for posting solutions from a debian box, but perhaps the same principal will help others. It was just too frustrating coming across this thread that described exactly what I was running into but didn't have any suggestions or solutions...

for reference - kernel version is 3.12-1 and i'm running i3wm. (linux mint handled networks so badly I went back to debian)

Last edited by xmd (2014-01-06 00:28:42)

Offline

#10 2014-06-03 22:29:44

Eugene
Member
From: Adelaide, AU
Registered: 2012-11-02
Posts: 12

Re: Network Manager fails to connect with Sierra Wireless 3G/4G modem

Had access to the modem about a month ago.
All works with NetworkManager.
It was shown under "Broadband" and connected without any problem.

Offline

Board footer

Powered by FluxBB