Network Manager & Keyring password

This question has probably been asked "ad nauseam" but I'm trying to get Network Manager (in GNOME) to stop asking me for my keyring password. I searched in the forums and I found out there used to be a pam_keyring package that took care of this but it's not available anymore. Strangely this can be done with other distros so surely, it is also doable in Arch, right? TIA.

Allan wrote:Is this possible without logging in using gdm? I use networkmanager in XFCE with slim login manager and can't manage to get this to work.
I was able to disable the annoying 'feature' whereby the Gnome Keyring keeps asking for a password at login by editing /etc/pam.d/login in addition to the other edits suggested to /etc/pam.d/gdm (http://wiki.archlinux.org/index.php/Net … Kit_issues). I also deleted ~/.gnome2/keyrings. This is especially useful since I don't use gdm to login, rather loggin straight from the shell. YMMV if you use kde or another DE.

Similar Messages

I need a keyring (that works with network-manager)

Hi there,
I'm new to Arch linux (coming from Ubuntu) and I'm wondering how to set up a keyring that works with that gnome-network-manager applet and ssh(fs). I previously used GNOME and the gnome keyring, and all out of the box.
I couldn't find any manuals on how to set up the gnome-keyring in Arch linux, neither regarding ssh(fs) nor network-manager. I read people are complaining about network-manager asking for the keyring-unlocking-password, but this doesn't happen for me.
How do I set up the gnome-keyring propertly?

siriusb wrote:moljac024:
https://bugs.launchpad.net/wicd/+bug/377471
From this bug page:
The /etc/wicd/wireless-settings.conf file is made root-readable only. This means that any malicious users must have root access or physical access to the machine. In either of these cases, you have far more problems than worrying about the wireless network key.
Please see http://developer.pidgin.im/wiki/PlainTextPasswords for a very good explanation as to why the passwords are not encrypted.
It may be plain text, but only root can read/write.

[xfce4] network-manager-applet not asking for Wifi password

I am running XFCE with the gnome network-manager-applet and kwallet as password storage and I do not want to use the gnome keyring because it is making many problems with my current setup.
There are multiple ways to store passwords in NetworkManager. To save them plain in the config files is not an option for me. So I can put them in a password store or hack them in every time I want to connect.
While the gnome network-manager-applet does not work with kwallet I accepted to do all the hackery every time.
Problem: I even can not hack in the passwords.
If I try to connect the connection is disconnected immediately. The logs say, that "The name org.freedesktop.secrets was not provided by any .service files".
Long story short:
- NetworkManager needs the dbus service "org.freedesktop.secrets" to read passwords (via password store or via prompt)
- kwallet does not announce "org.freedesktop.secrets" - this is done by the nm-plasma applet (which I can not run without hacking XFCE)
- gnome-keyring announces itself as a secret agent but does not work with my setup
Do I need to write my own secret agent which only shows a password prompt and parses the input to NM or is there any option/tool/patch/hack/miracle that I have missed to use kwallet with gnome network-manager-applet or to get a password prompt without installing gnome-keyring?
Thanks in advance
Last edited by frederik (2015-04-14 15:30:24)

add this to your start-up: gnome-keyring-daemon --components=gpg
Edit: and install gnome-keyring ofc
Last edited by MakeTheGOD (2015-04-28 05:24:33)

Network manager won't store my WIFI password

hi everyone,
i seem to have a problem with my network manager (tried both the KDE network connection manager as well as the gnome nm-applet).
Whenever i want to connect to my wifi it asks for my WIFI password, although it's correctly stored in the network manager already and it won't accept it, the password prompt pops up over and over again.
I'm desperate, i don't know what else to do, or what's causing this problem.
I also started the nm-applet from the terminal and got this error message:
m-applet-Message: No keyring secrets found for SSID/802-11-wireless-security; asking user.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
does anyone have any ideas?
many thanks in advance,
theresa

Try to connect manually, open the terminal and issue the following:
ip link set <interface's name> down
ip link set <interface's name> up
Select your AP:
iwlist <interface's name> scan | grep ESSID
Connect to it:
wpa_supplicant -B -i <interface's name> -c /etc/wpa_supplicant/test.conf
Then print the status:
systemctl status dhcpcd@<interface's name>.service
or
systemctl status dhcpcd.service

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.

[solved] Network manager error

I installed network manager as the wiki says, added myself to the network group and added the policy kit file. When I did this process on my main box, it worked perfectly, but on my laptop running largely the same things (except 32 bit not 64) I'm getting a little authentication box whenever my network interface comes up, asking for root's password. I put it in, and it instantly says it disconnected. If I run nm-applet from a terminal, I get this error after typing in root's password:
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
I'm using xfce if that makes any difference. Anyone got anything I can try?
Oh and the only reason I'm using NM is because I'm sick of wicd deciding HERP DERP IMA DISCONNECT RIGHT NOW and then not connecting again afterwards. Though since NM isn't working I have to use wpa_supplicant and dhcpcd directly myself.
EDIT: Ooops, this is the wrong section Could a mod please move it to Networking?
Last edited by biltong (2011-09-12 12:58:28)

Now I find gnome-keyring is not installed. That should be made a dependancy for network manager. I also (thanks to that thread) double checked I had the file the wiki said I needed to create, and it turns out I made a typo with my extension. It had .plka instead of .pkla XD Mah bad! So now I just need to get wpa_supplicant to connect one more time and I should be good to go

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.

[Solved] NetworkManager asks for "default Keyring" password...

Hi there,
when I try to connect to the Wireless Network at my girlfriend's place, I have to set up the network connection myself, as it uses a WEP encyption. After entering the horribly long passphrase, I'm asked to enter another password. The box popping up sais:
"Network Manager wants to access the deafault keyring, but it is locked".
Being new to Linux in general I don't even know what that keyring is, where I can find/set it's password or what to enter. I found a solution for gnome desktops but I'm running xfce4 on a x86_64 architecture. Connecting at my place or at the university is no problem and I'm not asked to enter the password.
Thanks for taking the time to help me.
Neuneck
Last edited by Neuneck (2009-05-25 17:12:34)

I was able to disable the annoying 'feature' whereby the Gnome Keyring keeps asking for a password at login by editing /etc/pam.d/login in addition to the other edits suggested to /etc/pam.d/gdm (http://wiki.archlinux.org/index.php/Net … Kit_issues). I also deleted ~/.gnome2/keyrings. This is especially useful since I don't use gdm to login, rather loggin straight from the shell. YMMV if you use kde or another DE.

[Gnome 3] Network Manager can only create system connections

Hello,
Coming from ubuntu, I installed Arch with Gnome 3 (didn't like unity). I have a small annoyance with Network manager from [testing]. When I select a wireless network, it asks for my sudo password and creates a system connection under /etc/NetworkManager/system-connections. Even when unchecking "Available for all users" in nm-connection-editor afterwards, the settings are kept in /etc instead of gconf/dconf and gnome-keyring as was the case in ubuntu (don't know if that was also the case in arch with gnome 2).
Of course, I can instruct PolicyKit to not ask for a password when modifying the connections, but I'd prefer to keep my keys in gnome-keyring instead of unencrypted files. As the single user of the system, I do not need system connections.
Any ideas?

Seems like this is an upstream change in nm 0.9, and no workaround that I know existed for it.

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?

Wireless, Network-manager, dbus problem

Hey, I'm trying to connect to wireless network at school using dhcdbd, gnome-network-manager, nm-applet... and it works but get disconnected constantly. Don't know much about networking so could use some help. Here's some output with lots of dbus errors...any ideas? Thanks.
** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2
** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2

When I configure a Wep key to my wireless internet
sharing network, my windows installed notebook can't
connect to my iMac. But when I set up it free the
notebook connects easily.
There does seem to be a known issue with a WEP encrypted software base station and Windows clients.
As far as I am aware there is no way to get a Windows client to connect to a WEP encrypted software base station (sharing internet via Airport on a Mac).
I tried both with ASCII and
HEX keys and generated them from:
You could try a ASCII key of
1234567123456
which will be a HEX key of
31323334353637313233343536
However if this doesn't work then nothing will.
I don't know what to do and I don't want to set a
wireless network free for security problems. Does
anyone know a solution?
Yes, get a wireless router and use that, it really is the only suitable solution.
iFelix

Network Manager keeps asking for WPA passphrase

Hi, I finally managed to install arch on my netbook, everything seems to be in working order apart from my wireless connection..
I've installed and configured the broadcom drivers for my card from the AUR and both the access points I usually connect to (under windows/ubuntu) are visible.
firstly I tried to connect to my access point using wicd, it appears to work until it trys to validate the connection and eventually returns the error:
'Connection Failed: Bad Password'
im 100% certain i have entered the passphrase correctly.
I googled around, to find some people are having similar problems - i couldnt find a complete solution to my problem but a lot of people were linking to wicd-bzr. I have the same problem using wicd-curses..
next i decided to try NetworkManager, I uninstalled wicd and installed networkmanager 'pacman -S network-manager-applet'
again, the manager displays all available access points, i try to connect to my router and it repeatedly asks for my passphrase and never manages to connect.
does anyone has any ideas?
im using xfce4 (i also tried in gnome), the broadcom device is B4312, and the network security is WPA. Cheers.

Same problem here, tested with Wicd (also wicd-bzr), Netcfg and NetworkManager.
Tried wpa_gui, the event history keep saying:
WPS-AP-AVAILABLE
Trying to associate with [MAC-ADDRESS] (SSID)
Authentication with [MAC-ADDRESS] timed out
CTRL-EVENT-SCAN-RESULTS
Edit: sorry, i forgot to paste wpa_supplicant output with -d flag:
[root@hydra log]# wpa_supplicant -ddd -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='network'
update_config=1
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=21):
46 41 53 54 57 45 42 2d 31 2d 50 41 32 37 32 39 FASTWEB-1-PA2729
30 31 35 4d 41 015MA
PSK (ASCII passphrase) - hexdump_ascii(len=21): [REMOVED]
proto: 0x2
key_mgmt: 0x2
pairwise: 0x8
auth_alg: 0x1
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line 12: removed CCMP from group cipher list since it was not allowed for pairwise cipher
Priority group 0
id=0 ssid='FASTWEB-1-PA2729015MA'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:13:02:10:34:2e
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): a6 20 a7 e6 1e b5 58 c3 92 4f 1e 08 8d 27 ba 7a
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=90 (from group name 'network')
Added interface wlan0
Daemonize..
My wireless card is a Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Router is a Linksys WRT320N, configured with WPA2 Personal, Encryption AES or TKIP
Last edited by morgenstern (2010-11-19 18:41:58)

[SOLVED] Network Manager Applet

One of the things I got used to from Ubuntu is the network manager applet, which allows managing connections with ease. As instructed in the Wiki, I tried installing it with the following commands:
pacman -S networkmanager
pacman -S network-manager-applet
And then launched it by typing
nm-applet
But this comes up in the terminal:
(nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_red_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
(nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_green_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
(nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_blue_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
** Message: applet now removed from the notification area
(nm-applet:1518): libnotify-WARNING **: Failed to connect to proxy
** (nm-applet:1518): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
** (nm-applet:1518): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
** (nm-applet:1518): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
** Message: applet now embedded in the notification area
** Message: applet now removed from the notification area
In the notification area the icon looked like it was going to show up, but it's removed immediately.
I'm not even sure if I can connect to a wireless connection without this, can I? I wouldn't mind using a different method for connecting to my wireless connection, just as long as it works and it automatically connects when I login. So if anyone has got a better idea, please share it with me. In the mean time, what would I need to do to fix this and have the network manager applet working?
Last edited by faviouz (2011-09-15 15:52:50)

faviouz wrote:
Thanks for the quick reply dodo3773!
It worked excellently! I also added networkmanager to the daemons array and it loads on boot now, which is great.
No problem. Glad to help. As karol said the wiki has many tips and tricks for almost anything that you need to get your system up and running. Make sure to read through the rest of the networkmanager one in regards to gnome-keyring, groups, etc.. Take care and welcome to Arch Linux Forums.

Cisco Network Management software options

Hi,
I wanted to see if anyone can give me a quick breakdown on the differences between some Network Management software titles. I dont know when you would use each one or what the limitations are of each.
CNA - Cisco Network Assistant
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps5931/product_data_sheet0900aecd8068820a.html
http://www.cisco.com/en/US/docs/net_mgmt/cisco_network_assistant/version5_0/release/notes/OL12210a.html
CCP - Cisco Config Professional
http://www.cisco.com/en/US/prod/collateral/routers/ps9422/data_sheet_c78_462210.html
http://www.cisco.com/en/US/docs/net_mgmt/cisco_configuration_professional/v2_7/rlsnts/ccp_v27_rel_notes.html
CCA - Cisco Config Assistant
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps7256/ps7287/data_sheet_c78-682273.html
http://www.cisco.com/en/US/docs/net_mgmt/cisco_configuration_assistant/version3_2_1/release/Notes/cca_3_2_1_relnotes.html
Cisco Prime LMS (are their different versions or products here?)
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps11200/data_sheet_c78-697479.html
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2.3/release/notes/lms4_2_3_release_notes.html
CiscoWorks (depreciated? Now Prime?)
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps2425/data_sheet_c78-534877.html
I have been looking over the realease notes for each product trying to draw some conclusion on which titles support or dont support certain products.
Has anyone used these and can give a quick answer for when you would use each and if there are any gotchas or limits to watch out for?
It looks like Prime is a paid for product but will any of the free solutions (CNA, CCP, CCA) work with all enterprise level products (2950, 2960, 3560, 3750, 4948, 4900 4500 switches and 1800, 1900, 2800, 2900, 3800, 3900 routers) or do you have to use Prime to get a product that will mange these devices?
Thank you in advance.

Hi Marvin,
i am currently try to explore cisco prime Infra 1.3 and facing some problem.
1 : i have set the admin password at startup config but this password is not working(i am pretty sure that i have enter the same password)
2: Can i change the prime lan infra clock setting from it,s GUI
3: i am not able to see the end client assosiate to a cisco switch(C3750 )
4: i want to know can i use cisco infra to monitor broadcast on a switch port level.(suppose switch 1's port 10 client making broadcast ,can i monitor that)
is there is any videos avialable for cisco prime infra 1.2/1.3 .
Thanks,
Prashant

Gnome-network-manager shouldn't require Gnome?

According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
Maybe it would be a good idea to include a version that isn't compiled for Gnome in Extra, so that people using E17 or XFCE or whatever can easily use networkmanager? If people think this is practical I'll file a feature request...

Gullible Jones wrote:According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
It does need gnome deps. Requires libgnomegui and gnome-keyring... in turn it also uses gconf and other things. These can't be disabled.
James

Network Manager & Keyring password

Similar Messages

Maybe you are looking for