Network manager vpn kde

I'm having trouble connecting to a VPN through network manager on KDE. I think my biggest problem is understanding the structure of Network Manager, can anyone help me out.
I have Network Manager running and configuring my wireless client perfectly through networkmanager-plasmoid.
I would like to setup a vpn through pptp. I tried to set this up through the plasmiod but it doesn't really do anything. I understand this is still alpha, so it may just not work.
I have installed networkmanager-pptp through aur. But what is this doing? It seems like in gnome this has a gui. Is this purely a gui or a backend as well.
Should I be manually setting up a vpn with pptp? It seems like the point of networkmanager is to configure this for me (or is network manager only going to start this and tell me when it is running).
Thanks for any help.

Currently, the plasmoid is in heavy development, so I recommend to remove it with pacman -R, and use the gnome networkmanager frontend. Use the connection editor, enter the gateway, username, password, domain, use the special button to choose the authentication method (pap, chap, mschap, mschapv2, choose only one, if the login fails, try another). On the ipv4 tab, use the routing button, and enter the routing info, e.g. 192.168.1.0, 255.255.255.0, and disable automatic routing.
Hope that helps.

Similar Messages

[Solved] Can't find a way to run network manager in kde

Struggling a little to get wi-fi set up on an arch machine running kde
I've installed plasma-applet-networkmanagement but I can't get it to run
There isn't any launcher for the applet on the menu anywhere but I have been able to find a .deskop file for it at: /usr/share/kde4/services/plasma-applet-networkmanagement.desktop
When I try to run it though I get a little dialog box showing the following error
The desktop entry of type
Service
is unknown
I've viewed the .desktop file in kwrite and these are the entries which seem relevant to running it
Type=Service
X-KDE-ServiceTypes=Plasma/Applet
Icon=networkmanager
X-KDE-PluginInfo-EnabledByDefault=true
X-Plasma-NotificationArea=true
The last entry seems to be telling it to place the network manager applet in the tray if I'm understanding it correctly, but this doesn't happen
Anyone able to tell me how to get the kde network manager working?
Last edited by Ecky (2011-12-27 17:47:34)

If you add a widget to the panel, or if you add a widget to the desktop -- in the ribbon that lets you select widgets, you should have one called "Network Management"
If you do, drag it to where you want the control.
If you don't, well... Let's see what happens first

Xrdp and Network Manager

Hi all.
I'm fairly new to Arch, been running Debian for a few years before.
I have a problem with Network Manager in KDE when connecting through xrdp to my VPN client machine (running in KVM). The applet is visible, but when I click it it's empty so I can't start/end a VPN session.
If I connect using X2Go, Network Manager displays my connections and I can start/end a VPN session.
If I first connect and logon using X2Go and then connect and logon to a new session with xrdp, I can use Network Manager within the xrdp session.
X2Go does something during logon (Xsession?) that xrdp doesn't. Does anyone know what might be the problem?
I've already updated org.freedesktop.NetworkManager.conf to allow "at_console = false" sessions to use Network Manager.

I've done some more troubleshooting and it looks like it's related to systemd. Logging on with xrdp does not seem to register with systemd, if I run "loginctl list-sessions" there are no sessions.
If I logon with SSH there is a session created and Network Manager works in any xrdp session started after the SSH session.
Unfortunately I'm not getting any further, I've fiddled around with PAM files to try to fix this but have failed so far. There's been a lot of trial and error with dbus, polkit, PAM, systemd and xrdp settings and I'm pretty much lost.
Unless someone with more knowledge than me can point me in the right direction I'm giving up, if anyone else has the same problem I have a simple workaround, just log in with SSH before connecting to xrdp and Network Manager will work (org.freedesktop.NetworkManager.conf has to be edited, see above).
Cheers,
Daniel

Need Suggestions For Network Manager/WICD

Hello again everyone. I seem to be full of issues today. Anyway, I'm a KDE guy and I've been using WICD to manage my network connections since around the time that KDE 4.x premiered, because as far as I know KDE does not have a viable network manager.
WICD works great, it connects before I even finish logging in, it connects to my networks without me having to interact at all, until now. Now, it's just acting strange, and I didn't change anything except whatever is changed during the normal updating of packages.
It started off not connecting to wired connections at all and only wireless at home. If I plugged in a network cable, it would try and try and try and then tell me that it couldn't get an IP address. Sometimes after restarting it would work but not every time. After a few more days, it started to connect to wireless connections only 50% of the time. A reboot would usually clear it up.
Now, as of today, it won't connect to anything. I took it to work as I usually do so I can use it in the lunch room (where there are three wireless AP's in range) and it wouldn't connect at all, and I tried rebooting five times. One of my coworkers had no problem connecting to the same wireless AP on her laptop that I could not connect to.
I've never known WICD to be problematic like this. I didn't change anything and I don't think it's been updated recently.
If there is a network manager for KDE that works more reliably, I'm open to suggestions. I prefer WICD because it (used to) worked so well. At the very least, I prefer having some sort of wireless manager. The one that shipped with Kubuntu in 9.04 is completely terrible so whatever that is I don't know if I want that unless it got drastically improved.

mcsaba77 wrote:
Unfortunately wicd has lots of issues with latest kernel. I've been following and posting in these two threads:
http://bbs.archlinux.org/viewtopic.php? … 33#p695433
http://bbs.archlinux.org/viewtopic.php? … 11#p694311
As for now, I switched to networkmanager. I use the default nm-applet, it works well, but I agree, it's not nearly as neat as wicd, and the icon is an eyesore Maybe a kernel/wicd update in the future will solve these issues, but as of now, too many people (on various hardware) seem to have issues with wicd + kernel 2.32.x.
EDIT>
Knetworkmanager unfortunately depends on kde3, while the plasmoid is completely broken at the moment. Hopefully they'll get it working (or they might have some sort of solution) in 4.4 release...
I also have this issue, really thank you for your threads.

KDE network management backend changed on update.

The last couple of KDE updates have caused the network management backend to be changed to wicd. I use NetworkManager 0.9 -- I don't even have wicd installed (but I used to). The network backends listed in System Settings / Information Sources are NetworkManager 0.9, Wicd and Fake Net, but after updating Wicd is moved to the top of the list and NM0.9 to the bottom.
The first time this happened, my wireless stopped working until I worked out what had changed, but when I updated today (KDE 4.6.3-1 to 4.6.3-2), KDE Daemon and Plasma Desktop would crash when I logged in. I was able to start programs from krunner, so ran plasma-desktop from konsole and saw wicd mentioned in the output before it crashed. I changed the network management backend back to NM in systemsettings and now it works.
Can anyone tell me why the backend is changed when I update? Should Wicd even be listed, since it isn't installed?
I also noticed a couple of other weird things after updating today. I'm not sure they are related, but I'll mention them just in case. The arch logo that appears at the start when I boot has changed to a picture of tux, and a modprobe usage message appears just before the line "INIT: version 2.88 starting" (or something like that).

i thought they were the same thing... Tried knetworkmanager and it works fine, thank you very much.

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 kde

I have an intel 3945abg card. And I am running kde 4.3
Network-Manager and the plasmoid dont seem to recognize my wireless
but I can join wireless via the command line.
Any thoughts or suggestions?

Check this link
http://wiki.archlinux.org/index.php/Wireless_Setup

MPPE VPN for Network Manager

Has anyone build a package for this...
http://www.students.ncl.ac.uk/a.j.mee/b … tp-plugin/
It's a plugin for Network Manager giving pptp/ppp support.
As I need to connect to Microsoft Servers at work this would help me
EDIT: I know I also need the pptp-linux package but there is already a package for that
BR
Thomas
Last edited by thool (2007-04-26 19:19:20)

mcsaba77 wrote:
Unfortunately wicd has lots of issues with latest kernel. I've been following and posting in these two threads:
http://bbs.archlinux.org/viewtopic.php? … 33#p695433
http://bbs.archlinux.org/viewtopic.php? … 11#p694311
As for now, I switched to networkmanager. I use the default nm-applet, it works well, but I agree, it's not nearly as neat as wicd, and the icon is an eyesore Maybe a kernel/wicd update in the future will solve these issues, but as of now, too many people (on various hardware) seem to have issues with wicd + kernel 2.32.x.
EDIT>
Knetworkmanager unfortunately depends on kde3, while the plasmoid is completely broken at the moment. Hopefully they'll get it working (or they might have some sort of solution) in 4.4 release...
I also have this issue, really thank you for your threads.

No interfaces shown in network manager [SOLVED]

Hi All,
I have just done a fresh install of Arch on my new Sony Vaio VGN-FW53GF, all goes well, except for Network Manager.
I can use my wired connection ok as eth0 shows up as active when I hover over the kde applet in the task bar. However when I go to "Manage Connections"
I do not see any Wireless networks or even my "working" wired connection in any list.
Wireless seems to be working as iwconfig shows an interface.
wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But a scan gives this:
iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
This machine is using the Intel driver "iwlagn" supplied by the kernel (2.6.31).
My /etc/rc.conf is:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Pacific/Auckland"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Laptop2"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal networkmanager netfs crond)
Can anyone offer some suggestion on how to get network manager going, I would like to use it. In the past
I have used Wicd, but it has some limitations.
Cheers,
Bernie
Last edited by bmentink (2009-12-24 04:19:49)

bmentink wrote:
Ok, I found the issue. I was missing the firmware for the card. I downloaded firmware from the intel site as per the wiki on wireless and
my interface comes up (shown with ifconfig) and I can see all the networks.
However, I cannot seem to connect to my network with WPA. When I go to connect I get network manager thinking the access point is WEP and asking for pass phrase.
If I select WPA(personal) and fill in a password, nothing happens .... just says unavailable.
Can anyone give some idea's here. I have not used network manager before for WPA.
Cheers,
Bernie
I use WPA2 with network manager without a problem. It should "just work", im not sure why you have issues, can you switch your router to a different security protocol to test?

[SOLVED] Network Manager with iPhone 3G S

OK, so work got me a shiny new iPhone 3G S today. When I'm being paid to play with it, I'll give it a shot
Anyway, I've successfully paired the iPhone over bluetooth with Arch on my laptop, which creates the bnep0 network interface. If I run dhcpcd on this interface, the iPhone gives me a DHCP lease in the 192.168.20.x subnet, and after configuring the opendns nameservers, I'm successfully tethered to the iPhone with full network connectivity
Is there a way I can get Network Manager to do the 'dhcp' and 'nameserver' parts for me? In the nm-applet GUI, there's no option for specifying interfaces or anything just "wired" (eth0) and "wireless" (wlan0) as well as the VPN, 3G etc tabs.
Also (I know someone wants to mention this), I am already aware that bluetooth is going to be speed limiting, but this connection will generally only be used for SSH sessions back to the office, so I don't really care about that. I'm happy to use bluetooth to reduce the number of cables required - already have external mouse, external hard drive, power supply and serial cable when I'm at a client site, I don't really want a USB cable to the iPhone as well. Unless Network Manager can't do this over bluetooth, but it can over USB, then I'll concede on the extra cable.
Last edited by fukawi2 (2009-10-01 02:38:02)

Here's instructions for Ubuntu, I doubt there will be many discrepancies between Ubuntu and Arch though. Just translate the apt-get crap with the appropriate yaourt or pacman command.
http://undulynoted.net/2009/06/tether-i … -required/
Ubuntu:
Why oh why does apple hardware suck so hard with linux. You will get constant disconnects if your phone is more than a few feet away from the computer. But alas, it is still faster than pdanet or iphonemodem2.
If you are not on a mac congratulations, you have had fewer headaches.
Open the terminal and type:
sudo apt-get install blueman bluez-compat
This will remove wcid which hopefully isn't a problem for most of you.
It will ask you to restart, please do.
Once Ubuntu is back up click on your bluetooth icon in the upper right (which is now managed by blueman)
IMPORTANT: Right click on the bluetooth icon and choose local services. Make sure to click the radio box that says "Network manager" instead of "blueman" under the network pane. This will allow Network Manager to take over the controlling of your connection (which is good). REBOOT AFTER THIS STEP!
Go to the bluetooth settings in your iphone (Settings > General > Bluetooth) and make sure they are on.
Hit the search button in blueman and you should see your iphone after a few seconds.
WARNING: This is where it gets flaky on the macbook pro. Best results I have has is to highlight the phone in blueman and hit "Bond"
Choose to auto generate a pass on the next option. Next. Now wait for the iPhone to ask you to type in the passphrase. Type in the 4 digit one that blueman gives you. VERY IMPORTANT. While they are joining eachother keep you eye on the computer. It will ask you if you always want to trust the iPhone (device name). Hit Always or else you will have trouble.
Always initiate the connection from the iPhone. In the bluetooth settings on the iphone you will now see your computer name listed and the words "not conencted" next to it. Click it. Wait a few and it will hopefully say connected. Look back to blueman and you will now see status bars on the iphone. Right click on your iphone in blueman. Choose "Setup". Network access point is click by default so just hit "Next".
Now head over to Network Manager and you should see "Auto benp0″. Click it to connect and give it a few to generate an IP. DONE enjoy surfing the internet through your data plan without jailbreaking. I have noticed quite a few speed gains over pdanet. Also, i noticed I got better results when i used openDNS's servers (208.67.220.220 and 208.67.222.222).
If you have done everything correctly and Network Manager won't take over the connection of you can see it and it says "not managed" or something of the sort you need to check out the following:
Open terminal and type: sudo gedit /etc/network/interfaces
see if you have bnep0 located there. if you do, comment out or delete that line. and reboot your machine.

[SOLVED] Network Manager confusion on reading WiKi

I have installed KDE DE...I am unable to start the network through NM...
On going thru Arch Wiki , https://wiki.archlinux.org/index.php/NetworkManager
I understand that there are 2 NMs available..One is for GNOME but works in all DE (backend), Other is "Knetworkmanager" which is for KDE.(backend)...
The frontend GUI is Gnome- applet and KDEplasme-applet
It is stated under KDE 3.5 , that Knetworkmanager is not supported but available in AUR...
My doubt is as follows
1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
2. For Frontend should I install the Plasma widget or the GNOME applet?
3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
I had installed WIcd to test my settings...It was working initially after typing
modprobe b43 <for bcm chipset>
/etc/rc.d/network start
/etc/rc.d/dbus restart
/etc/rc.d/wicd start
ifconfig wlan0 up
dhcpcd wlan0
wicd-curses
Then I typed the network pwd and booted my interface.
i wanted to go in for network manager as it would save me the typing time..(Currently I installed pacman -S networkmanager (GNOME version) and KDE plasma "the one with the icon similar to "m")But on selecting the interface it goes thru Activating Interface and then says "Network Connection failed"
Now I am also not able to get wicd up
Any pointers?
EDIT ---The title says Graphical Front end managers, So I guess there is only one backend....In that case , why is my Network not working??All the wireless are detected ,so there is no problem with firmware....I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
Last edited by vikrang (2011-04-29 10:11:02)

vikrang wrote:1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
2. For Frontend should I install the Plasma widget or the GNOME applet?
3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
1. there is just one, networkmanager. network-manager-applet and kdeplasma-applets-networkmanagement are just front-ends to networkmanager.
2. https://wiki.archlinux.org/index.php/Ne … nager#KDE4 , but https://wiki.archlinux.org/index.php/Ne … ager#GNOME will work too. I use network-manager-applet on KDE 'cause the KDE front-end can't set a system connection.
3. I won't even bother to answer to this.
4. networkmanager!!!
vikrang wrote:I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
if you are using networkmanager you must the networkmanager daemon, not network. replace network with networkmanager in rc.conf in DAEMONS array.
Last edited by JokerBoy (2011-04-27 08:59:42)

Network Manager and Wireless

I have a Broadcom 1390 mini wireless on a Compaq v3000 series laptop with AMD Turion64 processor.
I have been trying to activate it for some time now. bcm43xx did not work. i compiled ndiswrapper, blacklisted bcm43xx and managed to get wireless detected. I used wifi-radar to connect, but strangely the gnome network applet and wireless network manager showed as no network though wireless was connected and working. I had enabled wlan0 in rc.conf and all details entered as per the wiki.
I removed networkmanager from rc.conf daemons and added network. Now wireless connects at boot without a hitch. No need for wifi-radar. This is after so many reboots that this occurred to me, so I thought i should share this and perhaps find out if there is something wrong in my approach. I am new to Arch (about a few months) though I have been with Ubuntu, CentOS etc for a few years now

Coinago:
Your enc idea did not work...
How does one enter WEP key 10 digit hexadecimal in rc.conf etc. I tried it straight, then XXXX-XXXX-XX both as key and as enc. It did not work. Do I have to insert an "=" somewhere. I am a bit at sea. I got the wireless going thru wifi-radar. I use gnome, no KDE for me.
I would like to crack this so i have wireless at boot in my office. It was working fine with entries in rc.conf when there was no key. So it is obviously about entering the WEP key in the right format and place..

Network Manager driving me crazy (3 issues)

Hey guys I'm new here, hope you can help me
nm-applet is driving me crazy!
First issue: when I boot nm-applet doesn't appear in my tint2 eventhough I'm connected. This don't appear all the time, it's random. I have to kill it and restart it to be able to see it.
I use openbox and I have this in .config/openbox/autostart
(sleep 3 && /usr/bin/nm-applet --sm-disable) &
Second issue:
I selected the save option for the password of my vpn but it won't save it... Or wait, yes it will.. But not all the time. It asks me for the pass sometimes, and sometimes not
Third issue:
I thicked the "automatically connect to vpn for this connection" but guess what... It won't
Any idea about how to troubleshot this. I'm seriously considering pacman -R network-manager and pacman -S something else
Thank you
Last edited by Truc (2014-03-06 21:17:51)

1st issue: run nm-applet from the command line (take it out of openbox's start file wherever that is) after you log in to see what's going on.
2nd issue: do you have gnome-keyring installed? I believe it should be started with by networkmanager when it's needed, but you may need to figure out how to start it on your own. I don't know how.
3rd issue: I believe the automatic connection to vpn on a specific network is triggered by networkmanager-dispatcher which is just part of the networkmanager package, but is its own separate service. When you enable/start NetworkManager via systemctl, it should enable/start 3 services - the dispatcher is one of them. Do you have that running?
I may be wrong about some of this; it's been a while since i've used NetworkManager.

No Network Manager Applet

So I just installed Arch on my desktop, I am wireless, but I have made sure my wireless card is properly configured. I have gone into the settings menu and looked at my applets and it says the applet is there but it never works or shows up. For whatever reason, no matter how many desktop environments I try I never have a network manager. I've tried KDE, Gnome, XFCE, and Cinnamon and none of them have it. Ordinarily I wouldn't mind connecting to wifi through the terminal, but when I go back to school, the network there requires a username to log in which according to my experience is not possible through the terminal. If it is please correct me and/or offer me a suggestion. Thanks in advance

TheNeXus84 wrote:
I am using an Intel Centrino Advanced N6205 wireless card.
the output of my systemctl status NetworkManager command is as follows:
[root@ArchLinux cj]# systemctl status NetworkManager
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
Active: active (running) since Sun 2013-12-22 20:42:57 EST; 23s ago
Main PID: 645 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─645 /usr/bin/NetworkManager --no-daemon
Dec 22 20:43:11 ArchLinux NetworkManager[645]: <info> Config: set interface ...1
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:14 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
Dec 22 20:43:17 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Hint: Some lines were ellipsized, use -l to show in full.
UPDATE: I fixed the problem. I had to enable DHCPCD. sorry to be a bother to you all but thanks for the help and support.
EDIT: upon rebooting my previous problem has occurred again.
Make sure that you have done
systemctl enable NetworkManager
as well as
systemctl start NetworkManager
- also when you ran dhcpcd how did you do it? Your network interface is wlp5s0 so you need to have dhcp running for that interface -
systemctl start [email protected]
will start it if it is not started, and
systemctl enable [email protected]
will ensure it starts after booting up. However I never needed to start dhcpcd at all when using NetworkManager.
There are occasions when the relative timing of different services does not allow some services to start properly - and then occasionally you need to add in some items to the NetworkManager service file to tell it to wait until the network is up first, if there are delays in the network starting at boot time but that can be sorted out once the basic services are set to start at boot.
Last edited by mcloaked (2013-12-23 18:01:46)

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 vpn kde

Similar Messages

Maybe you are looking for