Network Manager - wired connection

Hello.
At my dormitory I'm trying to automatize connecting to a local network. So far I've been
connecting to the network using this sequnce of commands:
$ sudo ifconfig eth0 up
$ sudo wpa_supplicant -Dwired -ieth0 -c /etc/kolejnet.conf -B
$ sudo dhcpcd eth0 up
It's kind of anoying.
I'm trying to get my Network Manager working but it seems that somewhere is a problem
but I don't know what it is. This is how is my file "/etc/NetworkManager/system-connections
/kolejnet" supposed to look like:
[802-3-ethernet]
duplex=full
mac-address=f0:de:f1:8:1a:a1
[connection]
id=kolejnet
uuid=3146f80e-9643-4de3-a037-6ef7e8adc888
type=802-3-ethernet
timestamp=1317798337
[ipv6]
method=auto
[802-1x]
eap=ttls;
identity="my username"
anonymous-identity=pizet
ca-cert=/etc/ssl/certs/vpn-sisal.pem
phase2-auth=pap
password="my password"
[ipv4]
method=auto
If everything is in here correct, what could the problem be?

The title says "have internet until ...", so apparently you have something else running to handle the connection. You can hope that NetworkManager will somehow find and kill this other network management tool, but a saner approach is to stop/kill it yourself before you start NM.
Note that I don't know much about steam, so there might be a better solution that allows you to continue to use your current tool (instead of NM).
And you should turn to the journal if you want to see log messages for NM.

Similar Messages

  • [SOLVED] Network Manager cannot connect to wifi after suspend

    Hi,
    There appears to be similar threads recently, but they relate to no wifi at all. I did some updates today, and now if I suspend or hibernate, network manager cannot reconnect to my wifi. It will (after a while) ask me to authenticate, but still fails. Nothing works except a reboot where it connects without issue.
    It was fine yesterday, has only started today. Here is my pacman log for today's updates:
    [2012-04-11 17:13] upgraded libpciaccess (0.13-1 -> 0.13.1-1)
    [2012-04-11 17:13] upgraded lib32-libpciaccess (0.13-1 -> 0.13.1-1)
    [2012-04-11 17:13] upgraded mpd (0.16.7-3 -> 0.16.8-2)
    [2012-04-11 17:13] upgraded xorg-server-common (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server-devel (1.12.0.901-1 -> 1.12.0.902-1)
    [2012-04-11 17:13] upgraded xorg-server-xephyr (1.12.0.901-1 -> 1.12.0.902-1)
    Here is my messages log:
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Auto-activating connection 'Padfoot'.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) starting connection 'Padfoot'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0/wireless): connection 'Padfoot' has security, and secrets exist. No new secrets needed.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'ssid' value 'Padfoot'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'scan_ssid' value '1'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'psk' value '<omitted>'
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: set interface ap_scan to 1
    Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: disconnected -> scanning
    Apr 11 18:38:29 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: scanning -> authenticating
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): association took too long.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): asking for new secrets
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> No agents were available for this request.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed for access point (Padfoot)
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> Marking connection 'Padfoot' invalid.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed.
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): deactivating device (reason 'none') [0]
    Last edited by Padfoot (2012-04-13 23:47:55)

    heiko wrote:linux-3.3.2 is released on www.kernel.org and reverts the patch that introduced this problem.
    For those using the arch repo kernel the next release will solve this issue. So I suggest waiting for this (no more than a few days) and use the LTS kernel in the meantime (or using a fixed ath9k module if already built).
    Thanks for that heiko. I thought that would be the case, hence I just waited.
    Will mark this as solved.
    Cheers.

  • Extending and airport extreme network with wired connection to a express

    I am getting fed up of deadspots in my house that now seem to have become much worse recently. After giving up on configuring my extreme router to avoid issues I now want to extend the network.
    If I put in a network cable from the extreme router to an airport express on the other side of the house can this be configured to be the same wireless network?
    I know express routers have an option of extending the network is this for wired or wireless or both and if I do this will it show up as one wireless network with no interference issues?. At the moment I am planning on getting an express airport and using some of those power cable ethernet adapters to link the two routers up should this work okay?
    Many thanks
    Andy

    Welcome to the discussions, Andy!
    If I put in a network cable from the extreme router to an airport express on the other side of the house can this be configured to be the same wireless network?
    Yes, post back if you need more details about this.
    and if I do this will it show up as one wireless network with no interference issues?
    There will be no interference issues between the AirPort Extreme and AirPort Express. However, if you live in an area with a number of other wireless networks around you, or you have cordless phones, there may well be some interference issues to tackle.
    I am planning on getting an express airport and using some of those power cable ethernet adapters to link the two routers up
    That should work assuming that both ethernet powerline adapters will be on the same master electrical circuit. I would suggest that you get a clear understanding of the store's return policy though...just in case.
    Message was edited by: Bob Timmons

  • Gnome-network-manager problems

    Hello all,
    I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
    I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
    However, when I reboot under those settings, I can't connect to anything, including ethernet.
    Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
    Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
    Thank you very much for any help.
    Matt

    [matt@myhost ~]$ iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11g ESSID:"3KR98"
    Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
    Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
    Retry limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:76 Missed beacon:31
    [matt@myhost ~]$ ifconfig
    eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
    inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
    TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
    Interrupt:22 Base address:0x6800
    eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
    inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:309 errors:0 dropped:76 overruns:0 frame:0
    TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
    Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
    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:16436 Metric:1
    RX packets:232 errors:0 dropped:0 overruns:0 frame:0
    TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
    ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
    also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific?

  • KDE. network manager "No agents were available for this request"

    I think there might be a bug with the networkmanagement plasmoid.
    Not sure if this is the right place to post it, or if maybe I should take this to the KDE forms¿??
    Anyway, took me quite a while to reproduce this, but it seems that with WPA wireless connections, when setting the "store connection secrets" to: "in secure storage (encrypted)", and then trying to edit the connection, an error is displayed with the following:
    "No agents were available for this request"
    im running kdeplasma-applets-networkmanagement 1:0.9.0.5-1 with its marked dependencies.
    Can anyone explain why this is happening?
    Am I missing something (agent??) in order to be able to store secrets in an encrypted file?
    Cheers.

    Use net-profiles.  arch linux wiki recommended that i think. Anyways, kde network manager lose connection every 1 minutes( in 2 machines i have tested ubuntu and arch linux).

  • Network manager in xfce doesn't connect but wifi-menu does?

    I may be misunderstanding how to use this since I've never done wireless from the command line before, but here is my situation:
    I just installed arch on my Acer Aspire One and used both the wired and wireless from the command line. I had never done wireless from the command line before and just followed the Beginners Guide and used wifi-menu to select the network to connect to. It was very very smooth and connected me in seconds. After installing xfce I decided I wanted a tray icon for selecting wireless stuff and so I installed networkmanager and network-manager-applet. After starting nm-applet it reported my wireless as disconnected (even though it was connected) and when I asked it to connect to my network it was unable to connect. I restarted the computer and still no success. While I can get by with wifi-menu, it would be awfully nice if I could get network manager to work with xfce. Does anyone have any thoughts on this?
    Thanks in advance.

    I switched to using wicd and after a little while of using it it seems to work pretty well. It works significantly better than NetworkManager and doesn't drop connections very often so long as the signal is good.
    My one complaint is that every so often a process called wicd-monitor likes to start using 100% cpu on one of my cores. Since this is a netbook and power is critical, I usually end up killing the process or restarting wicd so that it stops draining my battery.

  • Can I use the Airport Express to connect to a Linksys Wireless Network and then use the Ethernet port on the Airport for a wired connection to a device for internet access?  Would I be able to then also use that Ethernet pt to a Ntwk Hub for more wired c

    Thanks for the help.  Looked but not clear on what I am trying to do as being possible.  Can I use an Airport Express to connect wireless to a Linksys Wireless Router, such that I can then use the Ethernet ports on the Airport to either connected to a PC wired, or even use a hub off the Airport Express to allow multiple wired connections to it? 
    I am not looking to have the Airport Express extend my wireless network, just connect to it and provide me wired connections in a different location from where my Linksys Route is located.  Would prefer to replace Linksys with all Apple, but just not possible financially yet.  Thanks for the help.

    If the AirPort Express Base Station (AX) is an 802.11n model, then yes, you can reconfigure it as a wireless Ethernet bridge. In this configuration, the AX would join the wireless network provided by the Linksys router and its Ethernet port would be enabled for either a single wired device or for an Ethernet hub or switch for multiple devices.

  • [SOLVED] Network Manager: Connecting...

    Hello Arch Community!
    After three months wihout any Arch System I have switched from Ubuntu back to Arch.
    It seems that everything is working without any issues.
    One of my little problem is the program NetworkManager. Under GNOME 3.8, MATE and all other desktop environment using it, it only shows "Connecting". It seems to be connected because I can access the internet over my WPA2 encrypted wireless network. I have activated it with systemctl enable NetworkManager.service and installed the applet with pacman -S network-manager-applet. Under Ubuntu it worked without any problems but under my three Arch systems (Raspberry Pi, Sony Vaio VPCF13E4E and Acer Aspire One 725) it only shows connecting. If I run an Arch based distro from a live USB it works there too so there could be something wrong configured. If I start the network manager applet via the terminal it shows no errors.
    If you need more information please ask for it (it would be nice if you could tell me the Terminal command because I have forgotten many terminal commands while using Ubuntu ).
    Thanks in advance!
    To98
    EDIT: I have switched to Debian unstable (and stable on my Netbook) because next week school starts and I have no time to fix all my problems with Arch (I have no clue why I have those problems, because Arch worked always "out of the box" on my devices...).
    Thanks for the great time with Arch and the great Arch community. I think Debian is also a good choice and with backports I can have the newest software on Debian stable.
    Last edited by To98 (2013-09-07 16:38:53)

    Hello Arch Community!
    After three months wihout any Arch System I have switched from Ubuntu back to Arch.
    It seems that everything is working without any issues.
    One of my little problem is the program NetworkManager. Under GNOME 3.8, MATE and all other desktop environment using it, it only shows "Connecting". It seems to be connected because I can access the internet over my WPA2 encrypted wireless network. I have activated it with systemctl enable NetworkManager.service and installed the applet with pacman -S network-manager-applet. Under Ubuntu it worked without any problems but under my three Arch systems (Raspberry Pi, Sony Vaio VPCF13E4E and Acer Aspire One 725) it only shows connecting. If I run an Arch based distro from a live USB it works there too so there could be something wrong configured. If I start the network manager applet via the terminal it shows no errors.
    If you need more information please ask for it (it would be nice if you could tell me the Terminal command because I have forgotten many terminal commands while using Ubuntu ).
    Thanks in advance!
    To98
    EDIT: I have switched to Debian unstable (and stable on my Netbook) because next week school starts and I have no time to fix all my problems with Arch (I have no clue why I have those problems, because Arch worked always "out of the box" on my devices...).
    Thanks for the great time with Arch and the great Arch community. I think Debian is also a good choice and with backports I can have the newest software on Debian stable.
    Last edited by To98 (2013-09-07 16:38:53)

  • Network manager won't save connection password

    Hi there.
    I am installing new notebook and I am stuggling with an issue for couple of days already.
    I am on Cinnamon and I am using Network Manager.
    Before installing that, I had net-auto-wireless daemon in rc.conf which did the job and wifi was working.
    After switch to NM, I can search and see networks around me, but connection fails.
    Here is the log:
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) starting connection 'Auto RaquaNET'
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0/wireless): access point 'Auto RaquaNET' has security, but secrets are required.
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Sep 18 00:12:24 Phenom NetworkManager[822]: <warn> No agents were available for this request.
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> Marking connection 'Auto RaquaNET' invalid.
    Sep 18 00:12:24 Phenom NetworkManager[822]: <warn> Activation (wlan0) failed for connection 'Auto RaquaNET'
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Sep 18 00:12:24 Phenom NetworkManager[822]: <info> (wlan0): deactivating device (reason 'none') [0]
    I have searched forum here, but haven't found any solution so far.
    When I select my network from NM applet, I never get asked for password. However, if I start nm-connection-editor from the command line, edit connection and password there, then all starts to work and there is no problem anymore. So the issue appears to be that NM never asks for password and therefore no connection can be stored.
    I have read the wiki and have created org.freedesktop.NetworkManager.pkla in /etc/polkit-1/localauthority/50-local.d directory.
    Some remarks:
    - please do not suggest to switch to wicd, I know about it, but I prefer to fix NM instead
    - I tried to remove my other computer's saved wifi and it exhibits the same behavior. It worked once, 100% sure about it.
    - It does not work also under regular Gnome 3 session, so it is not Cinnamon's fault.

    Fixed!!!  Went back into the  dir: swtools/apps/fingerprint  and noticed a second file named updater.  Ran, rebooted.
    Works.  Never would have seen unless I went back.

  • Network Manager Can't Connect Wirelessly

    Hi everyone,
    I'm trying to migrate from Connman to Network Manager for my network needs (as well as from e17 to xmonad) and I'm seeing some strange behavior. I can get the network manager applet running, but it won't connect to any wireless networks. I see a bunch of networks floating around in the connections list, but if I click on one, nothing happens. Furthermore, if I try to connect by command line, I get the following weirdness
    Input:
    nmcli con up uuid f767eb89-ccbc-4dbe-bf12-af216ab8f9ff ap A0:21:B7:72:A3:CE
    (the uuid is for my wlan0 interface and the ap is the BSSID of my network).
    Output:
    Active connection state: activating
    Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/0
    ** (process:2012): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/0: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
    state: unknown
    Error: Connection activation failed.
    I'm fairly sure that I have my policy kit working correctly. I have dbus and network manager as daemons and I logged in to an xmonad session using GDM, which should do my policy management for me, right?
    I think its the wrong error message for a policy kit error anyways.
    Any ideas?
    Thanks in advance!
    Last edited by Yurlungur (2012-04-16 04:29:32)

    I switched to wicd, so this isn't an issue anymore, I guess... still not sure what was going wrong, though.

  • Network Manager Applet Cannot Edit Options/Connections As Normal User

    Today I installed Network Manager, and Network Manager Applet in XFCE as a normal user. I followed the instructions on the Arch Network Manager Wiki to the best of my knowlage. The NM-Applet connects to my ethernet, and everything is fine. Untill that is, when I right click the NM Applet.
    Once right clicked as a normal user, 'Enable Networking', and 'Enable Wireless' are greyed out and unselectable. Also, when I right click the applet and select 'Edit Connections' 90% of the clickable options are greyed out, including the options to 'Edit' or 'Delete' connections. The only clickable option not greyed out is 'Add' button.
    Clicking Add brings up the 'Add New Connection Window', but again everything is greyed out. 'Available To All Users' is checked, but is greyed out also. But, starting XFCE as root, allows me to use the NM Applet with no restrictions, AKA none of the greyed out options. Everything works fine.This is my second day using Arch, so I am not sure where to go now.
    It also may be of help ito say I haven't gotten a display manager, such as lightdm or gdm.
    My guess is that root is listed under a group the 'jesse' isn't. Or maybe it has something to do with PolicyKit. I'm not sure. If someone could give me a set of clear instructions on how to fix this annoyance, it would be greatly appreciated. Thank You.
    My Current Normal User Groups wrote: disk lp wheel uucp games network video audio optical storage scanner power users
    My /etc/hosts file wrote:
    # /etc/hosts: static lookup table for host names
    #<ip-address>   <hostname.domain.org>           <hostname>
    127.0.0.1              localhost.localdomain localhost jesse
    ::1                         localhost.localdomain localhost jesse
    # End of file
    My /etc/rc.conf wrote:
    # /etc/rc.conf - configuration file for initscripts
    # Most of rc.conf has been replaced by various other configuration
    # files. See archlinux(7) for details.
    # For more details on rc.conf see rc.conf(5).
    DAEMONS=(alsa dbus syslog-ng crond ifplugd networkmanager bluetooth avahi-daemon acahi-dnsconfd avahi-dnsconfd fa$
    # Storage
    # USEDMRAID="no"
    # USELVM="no"
    # Network
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    My /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla wrote:Identity=unix-group:network
    Action=org.freedesktop.NetworkManager.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes
    Last edited by TriforceLZG (2012-09-02 13:43:23)

    I found the solution, I had to install a Display Manager. Now everything is fine.

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • 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)

  • Connect to Win (wired) network from MacBook connecting via AirPort Express

    Hi,
    I have a MacBook (OS 10.4.10) that I was connecting to my Windows network via a Linksys WRK54G Wireless router (configured as a WAP), which in turn was connected to a Netgear FVS318 VPN Firewall Router. The FVS318 connects to my cable modem and 2 Windows XP Pro PCs. The Linksys WRK54G has been flaking out, so I replaced it with an Airport Express. My MacBook and a Windows XP Pro laptop are both able to connect to the internet via the airport express, and they are both able to ping the IP addresses of my (wired network connected) Win XP Pro PCs. However, the PCs no longer show up under "Network" on the MacBook, nor can I connect to the shared directories on the (wired) Windows PCs from the Win XP Pro laptop (via Start Menu => Run => enter IP address). I have not found any answers so far either using Google or Apple Support website. Surely this is possible -- what am I missing? Thanks.
    - Scott

    Hello sborisch. Welcome to the Apple Discussions!
    If I understand your network configuration, you just need to configure the AirPort Express Base Station (AX) as a bridge...
    To set up the AirPort Express Base Station (AX) as a bridge, either connect to the AX's wireless network or temporarily connect your computer directly (using an Ethernet cable) to the Ethernet port of the AX, and then, using the AirPort Admin Utility (located in the \Applications\Utilities folder), make these settings:
    Network tab
    o Distribute IP addresses (unchecked)
    o Apply the new setting.

  • Does an Airport Express require a wired connection to boost a Wi-Fi signal if I already have a wired Airport Time Capsule on the Network?

    I want to boost the Wi-Fi signal around my house. I have a 3TB Airport Time Capsule connected to my Virgin Media modem via a WLAN connection but wonder if an Airport Express device can be used at a remote location purely wirelessly - apart from a power connection obviously?

    Does AirPort Express require a wired connection.......if I already have a wired AirPort Time Capsule on the Network?
    No, but you will have much better network performance if you do wire the AirPort Express.
    The reason for this is that when you try to extend a network using wireless, you will typically lose about a half of the potential speed capability on the network.
    There is no network speed loss when you wire the Express.
    Here is what Apple's support document says about this:
    In the case of a wirelessly extended network, throughput may be reduced to less than 60 percent of that of a single device. The general rule is to keep the Wi-Fi network as simple as possible. You can accomplish this by using the minimum number of Wi-Fi base stations required to service the physical network area and by using Ethernet wherever possible.
    Extending the range of your Wi-Fi network by connecting Wi-Fi base stations together using Ethernet is always the best option, and will provide the best throughput

Maybe you are looking for

  • Posting Key

    Error message is displaying while posting vendor payment transaction through F-53, that message is Posting key not defined. Message no is F5817 Diagnosis is Service Financial accounting: posting keyl "" was not found in the posting key table I checke

  • Windows 8.1 compatibility with WLC

    Hi, We are running WLC on version 7.0.240.0. Windows 8 clients are able to connect to the WiFi, whereas Windows 8.1 clients are not able to connect. Is there any bug reported for this issue. And also Please suggest a WLC version which will resolve th

  • WRT54GS Problems

    I'm having a few problems with my WRT54GS router. I'm sure the problem isn't with my DSL modem, since when I tried my connection without the router, it worked perfectly. Anyway, the problem is that there are times that the router would suddenly get d

  • Bought a Flash 8 Template

    I bought a Flash 8 template for one of my customers.  Getting help is like pulling teeth. I make changes by modifying a .txt file and I observe by clicking index.html. The expressions in the .txt file look like: &menu1=Home Page &menu2=About Us etc..

  • My key sounds and lock sounds no longer working, have tried everything!! Please help?

    I have only had my iphone 4s for two months. The key sounds and lock sounds not working, happened after plugging it in for charging. It's all switched on in settings. Now it only vibrates when a message comes, or new mail etc, even though I have tone