WRT54G3G-AT - Sierra Wireless Aircard 881

I was wondering if the Sierra Wireless Aircard 881 is compatible with the WRT54G3G-AT router.

That is a good question. The Sierra Wireless Aircard 881 is compatible with the AT&T 3G wireless network, however the current firmware for the WRT54G3G-AT doesn't seem to recognize the card. The WRT54G3G-AT does recognize and works well with the Aircard 875. I've been trying to find out from Linksys when they will be releasing a firmware upgrade that will support the 881, but no luck with that question so far.

Similar Messages

Need a router to conect ipad to a telstra 4G usb Sierra wireless "AirCard 320U

need a router to conect ipad to a telstra 4G usb Sierra wireless "AirCard 320U

You need a MiFi. Talk to your cell provider.

Sierra Wireless Aircard - not receiving data while connected to the network

Hello,
Can anyone please help me out here please.
I have a wireless internet connection on the Bigpond 3g network in Australia. It uses the Sierra Wireless Aircard 880U and the Bigpond connection manager software (version 2.10.18) to connect to the internet. This has been running pretty fine since I installed it some 4 months ago.
Now in the last 3 weeks I've been having connection problems, or actually I'm still connected, but data just suddenly stops coming in. The connection manager software states that I'm still connected to the 3g network; and I can see that data is still sent from my mac (the software tracks the data sent and data received); however there's no more data coming in (or very little, as in bytes), and Safari (or any other application like Skype, the widgets or mail) eventually fails (just happened again: "Safari could not open the page “http://discussions.apple.com/post!post.jspa?forumID=1222&reply=false” because the server is not responding" - while I was still connected according to the connection manager).
Also I can't ping anymore. Packets are sent out, but nothing comes back.
Now I've spent the last 3 weeks on the phone with Bigpond support but they can't resolve the problem. We have tried all the resources; including reinstalling the software, de- and reactivating my account, rebooting, removing and reconnecting the device, creating a specific location for the wireless card as to reduce any possible interference from airport, etc. But this hasn't resolved the problem.
The support people are now stating that it is not their device or software that is faulty (as the can see that I'm connected to the network just fine on their side), but something specific to my Mac that is causing the data problem and that I need to contact mac support.
The annoying fact is that the problem is erratic. Usually when I start up my mac in the morning; I can connect and surf the web without a problem, but later in the day, the internet connection will fail. I will restart the mac and bigpond connection manager and sometimes I may be able to get back online, but most of the time there is no more data (or very little data) coming in even though the connection manager tells me I am connected to the network and data is going out and very little coming back in (a few kilobytes at the most). Personally I have the impression that the Bigpond connection manager software is not too stable, but I can't put my finger on it.
Also the connection manger software seems to behave erratic. Sometimes it is connected and I can surf fine, while it states that it is (still) determining the IP adress, other times it will show a valid IP adress but I'm not getting data (or vice versa). Also I've been getting other error messages, like: "unable to initialise the device" and a mac popup message: " a modem error ocurred; cannot negotiate a valid set of ppp...."
Hopefully theres someone who can give me a hand here based on what I've written. I'm at wits end. Just let me know if I need to supply need more info;
thanks

I have just discovered another aspect of this issue.
If I have the Macbook connected to my router which is then connected to the Mac Pro but the router is not connected to the internet then PS on the Macbook starts up with no problem.
If the Mac Pro is not connected to the Router then PS will not start up on the Mac Book.
I suspect that this behavour started after I installed 10.5.7 - however as I cannot recollect starting up PS in standalone mode prior to last week before I installed 10.5.7 via the combo package.
So any clues please
Derek

Will the airport devices and time capsule work with telstras mobile hotspot (Sierra Wireless AirCard 753S Mobile Hotspot)??

will the airport devices and time capsule work with telstras mobile hotspot (Sierra Wireless AirCard® 753S Mobile Hotspot)??

Yes. There are 2 ways you could use these devices:
Wirelessly 'join' the network. This would be slower and doesn't offer extending functionality.
Use an Ethernet cable (through Powerline if you can't run a cable). This is faster and offers extending functionality. I would recommend using Bridge Mode if possible.

WRT54G3G-ST + Sierra Wireless AC597E issue

I've been experiencing some difficulty with my WRT54G3G-ST router in regards to using a Sierra Wireless AC597E. Namely the router fails to recognize the card when plugged in. Everything on the card is still on factory settings, Is there anything particular on the card's setup that needs to be enabled/disabled for the router to recognize it?
The router is using the firmware 2.01.12
Message Edited by Raithgar on 03-04-2008 02:50 PM

Are youusing the a wired broadband router like cable or dsl at the same time using the mobile broadband card? If so, only one service can be used at a time. If the mobile broadband card is enabled, then the wired connection coming from the cable or dsl modem is automatically disabled.

Sierra Wireless USB AirCard Support

I have been evaluating the product for a bit now, and it seems pretty rock solid. I just started testing with some of out cellular broadband devices and have found an issue with one so far. the Sierra Wireless AirCard 875U is not recognized by ESM. It totally ignores and doesn't apply any policy to the adapter. no firewall or otherwize. Is this a known issue?

Originally Posted by dave4nier
When you hover over the ZESM icon, it shows a Sierra Wireless HSDPA Modem. However, the when connected to the BroadBand network, windows see's it using a wireless driver which ZESM doesn't know about. I can send you my policy, but I'm not sure that its relevant. I get this behavior with a stock install and the default policy. I can attach my policy files if you still feel its relevant.
I think this is a fairly huge issue, and could allow a user to totally circumvent the ZESM client and leave the machine fully vulnerable.
Can you try the following:
Create a location called wireless
Select an icon for the location
In Wi-Fi Management click the "Filtered Access Points" tab and enter the SSID of your Wireless AP (it is case sensitive)
Save and publish the policy.
Does the ZESM client change locations?

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)

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)

Power Mac G5 won't connect to Sierra Wireless 318u

The Wireless Aircard will not work properly on my Power Mac G5. It installs fine and application opens but it will only say No device detected even though it's plugged into the USB port and the light on the Aircard is light up. I have tryed uninstalling and reinstalling the application whilst rebooting the computer inbetween but to no solution. Sierra Wireless Aircard model is 318U. Note on the other two macs i have (iMac and Macbook Pro) the Aircard works fine.

"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
Reboot.

Sierra Wireless 881 USB Connect. Airport Extreme

I have Been told that you could plug the Sierra Wireless 881 USB Connect into the back of the Airport Extreme OR iMac because it has the same Airport Extreme Capabilities. Your supposed to be able to just plug it it go to your airport settings and create a network, when you do this its just supposed to show up says the Best Buy and Apple Store Employee's!
I have tried this and it did not work for me.
I want to be able to send out a signal from the Sierra Wireless 881 USB and be able to use all 3 computers on the same network!
The Sierra Wireless 881 USB is just a simple and portable USB connect that you would get at the AT&T store!
If anybody has ANY information I would REALLLLY appreciate some feedback.
Thank You So Much,
CGair

The USB device in question appears to be a mobile broadband modem. That is, wireless broadband through a mobile telephone network. This is not the same as a "local" wireless network (Wi-Fi).
I want to be able to send out a signal from the Sierra Wireless 881 USB and be able to use all 3 computers on the same network!
In order to do this, you would typically need a dedicated mobile broadband router with Wi-Fi capabilities (available from a number of manufacturers), and with specific support for the USB modem used.
Alternatively, it may be possible to use a special adapter (such as this example) between the USB modem and the (Ethernet WAN port of an) AirPort Extreme base station. I have not tested this, though.
Jan

Sierra 881U aircard no WWAN icon in menu bar

I am running a Sierra 881U aircard with AT&T 3G service and it is fast--works fine; BUT--there is no WWAN icon in my menu bar like there should be. I have installed the Sierrra's "Install Switch Driver" to enable native support but I have to open network prefs to connect each time. I can go back to "Wireless Watcher Lite" but would like to just keep using the native support for this AirCard. 10.5.4 is supposed to have built-in support for this aircard--I thought. Any ideas on this?

William, I'm having the same issue on the PBG4. I didn't realize that you could go into the network prefs to get it to connect. Anything special you are doing when you open network prefs?

Sierra Wireless USB card will not connect

I have purchased a Sierra Wireless USB card (AT&T USB Connect 881) to use with a iBook G4. The green power lites are solid green. However, I can not get a signal from AT&T. No one has been able to help solve this problem. I am ready to return it to AT&T for a refund.

Thx for ur reply. I just checked the model of the USB adapter is Belkin Basic N150.
The xp is able to see and identify the iphone wireless network and shows it in available networks with full signal strength. Once I click on connect then an alert message says that it is detecting network type pls wait. Then another message appears stating that "selected network may be no longer in range. Pls refresh the list and connect again"
As suggested by you I will try it on windows 7.

Sierra wireless 875u compatible with 10.5.2 leopard?

I'm thinking of signing up the AT&T unlimited broadband package and get a free sierra wireless 875u aircard. I have an imac running 10.5.2 at home. WIll it be compatible with it?

I can't speak to the 875u but my Sierra 597e Express card works well.
See my post here:
http://discussions.apple.com/message.jspa?messageID=6664354#6664354
The major issue I had was with activation of the card.
Message was edited by: lethal

Sierra Wireless AT&T WWAN issue

Hi - I've got a Lenovo Thinkpad X300 with an OEM Sierra Wireles MC8775 HSDPA card, driver 2.0.9.0, 1/11/2007. It has worked fine except in two instances: first when traveling from the US to Switzerland, upon arrival it "failed to initialize" the device as I tried to run the dialer. This was true despite cold restarts. About a day later it started working, and working consistently, in Switzerland. Upon return to the US exactly the same phenomenon: unable to initialize for about a day. Then, working fine.Lenovo is ready to replace the card, but does anyone know if this is a software or other glitch for which I shouldn't trouble them? Something having to do with switching countries? (And do I appear to be running the latest firmware/drivers? Firmware is H1_1_9_3MCAP.)
Thanks,JZ

To follow up for any that come later: the card was replaced, but experienced the same phenomenon in going to the Netherlands and back again to the US. This time I downloaded and ran the "Sierra Wireless Watcher." After the wireless radio was turned on it sat at "searching..." for about five minutes, then found the new band. Once found it sticks, so the regular Lenovo dialer can then be used. So it's not a hardware problem, and there's a solution. ...JZ

Windows 8.1 Ent. Helix - Sierra Wireless EM7700 device error code 43

System:
Helix 3701XXX
Windows 8.1 Enterprise 64-bit
Third Apps installed
Latest Lenovo Drivers installed
Problem:
Sierra Wireless EM7700 device experiences device code error 43 or not “USB device not recognized.” There are also times where there are two or more instances of the same device in Device Manager.
When the problem occurs, users are unable to see the mobile broadband device under Network connections menu (Charms menu->Settings->Network Connections). Installed drivers on system: Sierra Wireless QMI Lenovo Driver Package 2.6.1.209.0. Experienced this issue with the Lenovo pre-load image and corporate image. The problem has been reported by 10+ users/systems;
When it occurs:
The problem is intermittent; it often occurs after waking the system up from sleep or starting the system from a cold boot. As a workaround, the user has to restart the system a couple to several times in order for the device to be recognized.
Wondering if anyone else has been experiencing this on the Helix 3701XXX Windows 8.1 Enterprise? Any advice is appreciated.

I get similar problems with the Ericsson C5621 wireless card.
To be honest, almost every 3G\4G internal card I've experienced (in Dell, Toshiba and now Lenovo) have suffered from the same two problems (when used against UK mobile providers):
i) issues resuming from sleep - typically the card not responding or not found until doing another sleep\resume or power cycle
ii) issues when moving quickly between cells (e.g. if using the device on a train etc.), when the card will stop transmitting traffic although claims to be connected, and then will become unresponsive attempted a disconnect and reconnect. Again power cycling the card (via sleep\resume, reboot, or occasionally disabling\renabling or uninstalling\reinstalling the driver) will resolve this.
Given that these cards are typically used in mobile devices where sleep\hibernate and being on the move are pretty common scenarios, it is frustrating that the 3G\4G hardware companies still can't get them to work reliable.
Matthew

After I loaded Mac OS lion, it won't let me install my Sierra Wireless telstra. It keeps telling me to install it even though i already have. help please?

After I loaded Mac OS lion, it won't let me install my Sierra Wireless telstra. It keeps telling me to install it even though i already have. help please?

Check for new 64 bit software for the modem, other wise you I'll probably have to boot your Mac in 32 bit mode first.. And then every time you want to go online.
I have the Sierra wireless 306 and have their 64 bit lion software installed. Works well.
Best.

WRT54G3G-AT - Sierra Wireless Aircard 881

Similar Messages

Maybe you are looking for