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?

Similar Messages

Xfce4 and gnome-network-manager [solved]

I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
Last edited by anarxi (2009-01-14 00:22:42)

quoted from a previous thread
I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
en_US.UTF8 UTF-8
en_US ISO-8859-1
After you've enabled the necessary locales, you have to run locale-gen as root to update them:
# sudo locale-gen
Generating locales...
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.

Network Manager SOLVED!

So, I just installed Arch last night, and I'm really proud of myself for getting almost everything working on my first try.
However, there is still one thing that I'm still having problems with, NetworkManager. I installed both it and the NetworkManager-applet using Pacman, however whenever I try to run either of them I get the following error.
** (nm-applet:1951): WARNING **: <WARN> request_name(): Could not acquire the session service as it is already taken. Return: 3
**(nm-applet:1951): WARNING **: <WARN> constructor(): Couldn't initialize the D-Bus manager.
Help would be greatly appreciated.
Last edited by nothinggoespast (2009-12-21 16:42:33)

nevermind, fixed it, I had a typo in /etc/rc.conf
... a @ instead of a !

[SOLVED]Network Manager dispatcher unexpected unmounting davfs folders

I have used Network Manager dispatcher to configure automatic mount of cloud storage using webdav. i have used davfs2 to perform mounting and wrote a script for NM dispatcher.
If i run /etc/NetworkManager/dispatcher.d/10-YandexDisk.sh manualy all works perfect.
If this script will be executed by NM-dispatcher all will fine(YandexDisk mounts successfully, sycronization - successfully), but after ~10 seconds mount.davfs gets signal 15.
sudo systemctl status NetworkManager-dispatcher
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
Active: inactive (dead) since Wed 2013-07-31 23:12:55 EEST; 11s ago
Process: 12132 ExecStart=/usr/lib/networkmanager/nm-dispatcher.action (code=exited, status=0/SUCCESS)
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: --- yandex.ru ping statistics ---
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: rtt min/avg/max/mdev = 36.570/37.776/38.983/1.222 ms
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: davfs2 1.4.7
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=users,_netdev,rw,uid=lexa https://webdav.yandex.ru/ /home/lexa/.../YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >mounted https://webdav.yandex.ru/ to /home/lexa/Data/YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >exiting!!
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: pid 12140, got signal 15
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting /home/lexa/Data/YandexDisk
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting failed
Why does this happen? Who send this signal ?
/etc/NetworkManager/dispatcher.d/10-YandexDisk.sh
#!/bin/bash
#this script will mount WebDav folder
# by pirat9600q
#given arguments are
#$1 is interface name
#$2 is state "up" or "down"
eth="enp7s0" #ethernet interface
wlan="wlp8s0" #wireless interface
ignore_connections="Pirat9600q" #WiFi SSIDs that must be ignored
mount_dir="/home/lexa/Data/YandexDisk" #mount point directory
remote_server="https://webdav.yandex.ru/" #server address
#local acces options
local_user="lexa" #files owner user
local_group="users" #files owner group
echo "<<<started with '$1' and '$2' arguments>>>"
echo "> our mount dir is '$mount_dir'"
echo "> and remote server is '$remote_server'"
case "$2" in
up)
#first of all we need to check internet connection
if (ping -c 2 -q yandex.ru); then
#we are online
if [ "$1" = "$wlan" ]; then
#Does this network is ignored ?
SSID=$(iwgetid -r)
for x in $ignore_connections; do
if [ "$x" = "$SSID" ]; then
echo "> WiFi SSID '$SSID' is in ignore list, exiting"
exit
fi
done
fi
if [ ! -d "$mount_dir" ]; then
fusermount -u "$mount_dir"
fi
if(mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=$local_group,_netdev,rw,uid=$local_user "$remote_server" "$mount_dir"); then
echo ">mounted $remote_server to $mount_dir"
echo ">invoking syncronization script"
/home/lexa/.scripts/SyncYandexDisk.sh
else
echo ">error mounting $remote_server to $mount_dir !!!"
fi
else
echo ">network down";
exit
fi;;
down)
echo ">unmounting '$mount_dir'"
fusermount -u "$mount_dir"
echo ">removing $mount_dir"
rmdir $mount_dir
echo ">finished";;
esac
echo ">exiting!!"
exit
/home/lexa/.scripts/SyncYandexDisk.sh
#!/bin/bash
#this script will synchronize local storage
#with mounted Yandex Disk folder
# by pirat9600q
source_dir="/home/lexa/Data/YandexDisk/" #mount point directory
dest_dir="/home/lexa/Data/ARC/CloudSync/" #local storage location
echo "<<<started with:"
echo " source folder '$source_dir'"
echo " and destination folder '$dest_dir'"
if [ ! -L ${source_dir}Foto ]; then #if not link
echo ">invoking syncronization from '$source_dir' to '$dest_dir'"
echo ">syncronizing 'Foto' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Foto/ ${dest_dir}Foto/); then
echo ">>error"
else
echo ">>success"
fi
echo ">syncronizing 'Documents' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Documents/ ${dest_dir}Documents/); then
echo ">>error"
else
echo ">>success"
fi
else
echo ">syncronization will not be made, because source is fake"
fi
echo ">exiting"
exit 0
P.S. sorry for my English
Last edited by pirat9600q (2013-08-02 08:14:44)

I solved the problem. Here is a little explanation.
After NetworkManager establishes network connection, NetworkManager-dispatcher service is started( for ~10 seconds). This service execute /usr/lib/networkmanager/nm-dispatcher.action, which execute scripts in /etc/NetworkManager/dispatcher.d. After exiting nm-dispatcher.action mount.davfs process appears in NetworkManager-dispatcher`s CGroup. By default all processes in CGroup must be killed when service stops. To change this behavior I have added KillMode=process to [Service] section of NetworkManager-dispatcher.service file.
sudo nano /usr/lib/systemd/system/NetworkManager-dispatcher.service
Here is it`s code now.
[Unit]
Description=Network Manager Script Dispatcher Service
[Service]
Type=dbus
BusName=org.freedesktop.nm_dispatcher
ExecStart=/usr/lib/networkmanager/nm-dispatcher.action
KillMode=process
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.nm-dispatcher.service

[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.

[SOLVED]Modem-manager won't start with Network manager

Hi,
I have a problem with getting modem-manager work under gnome. After first Arch install to this laptop, Network manager didn't show my 3G-modem, so I installed modem-manager and usb_modeswitch. Modem is Huawei E367 and it works well with wvdial. Only problem is to get it working with Network manager.
From output of dmesg I see that there is an error, when Network manager is trying to start modem-manager:
[ 3224.705193] do_trap: 322 callbacks suppressed
[ 3224.705198] modem-manager[3112] trap int3 ip:7ff7baab4143 sp:7fff996e62b0 error:0
[ 3224.719275] modem-manager[3114] trap int3 ip:7f58f4c5e143 sp:7fffc82b2400 error:0
[ 3224.733880] modem-manager[3116] trap int3 ip:7f579dda4143 sp:7fff77910850 error:0
[ 3224.748789] modem-manager[3118] trap int3 ip:7ff752c6f143 sp:7fff8ae42e20 error:0
[ 3224.763501] modem-manager[3120] trap int3 ip:7fb4db83f143 sp:7fff3023cbf0 error:0
[ 3224.777865] modem-manager[3122] trap int3 ip:7fa17a33a143 sp:7fffc1628260 error:0
[ 3224.792165] modem-manager[3124] trap int3 ip:7f00a39fb143 sp:7fff075a0fb0 error:0
[ 3224.806603] modem-manager[3126] trap int3 ip:7f9a62e23143 sp:7fffc2ccfed0 error:0
[ 3224.820736] modem-manager[3128] trap int3 ip:7f3d2994d143 sp:7ffff2581340 error:0
[ 3224.834985] modem-manager[3130] trap int3 ip:7f5adda9a143 sp:7fff8a70a4a0 error:0
From /var/log/messages.log I found also something:
Apr 14 16:02:14 localhost NetworkManager[713]: <info> trying to start the modem manager...
Apr 14 16:02:14 localhost dbus[651]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 14 16:02:14 localhost dbus[651]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Apr 14 16:02:14 localhost NetworkManager[713]: <info> modem-manager is now available
Apr 14 16:02:14 localhost modem-manager: libhal_ctx_init() failed: (null)
Apr 14 16:02:14 localhost NetworkManager[713]: <info> the modem manager disappeared
If I try to run modem-manager manually with debug:
$ sudo modem-manager --debug
** ERROR **: libhal_ctx_init() failed: (null)
Make sure the hal daemon is running?
So it seems to be because of hal isn't running, if I try to start hal daemon it fails:
$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
I also tried to start hal at boot by putting it to DAEMONS in rc.conf. but didn't start either.
The laptop is Asus X61SL with x86_64 version of ArchLinux.
Kernel: 3.3.1-1-ARCH
Would be cool if anyone can solve this.
Last edited by Jompu (2012-04-14 20:42:20)

Thanks for your quick reply Strike0!
I ran lsusb and usb_modeswitch as you instructed:
[louis@Louis-Laptop ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 002 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 003 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 001 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
[louis@Louis-Laptop ~]$ sudo usb_modeswitch -v 12d1 -p 1506 -M '55534243123456780000000000000011062000000100000000000000000000'
Password:
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x82 (in)
Not a storage device, skipping SCSI inquiry
USB description data (for identification)
Manufacturer: Huawei Technologies
Product: HUAWEI Mobile
Serial No.: not provided
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x82
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.
It didn't help. Network manager doesn't show anything related 3G.
I don't think it's usb_modeswitch since 3G stick works great with wvdial on same system. Could it be a bug on modem-manager?
I start only the Network manager on boot, but while Network manager tries to start modem-manager, it throws error continuously in dmesg. Error is the same as in first post.

[SOLVED] Network manager only works as root

Hello everyone,
I am brand new to arch and have been quite impressed over the past few days over all it has to offer. Everything has been running quite smoothly and I am now in the process of setting up wireless. I installed network manager and was able to connect to a wireless network as root. For my regular user, however, I am running into some issues. First one was that the nm-applet could not be opened in fluxbox. I received the following error:
** (nm-applet:1576): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.27" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
I "fixed" this by adding the following to /etc/dbus-1/system.d/nm-applet.conf. Original credit goes to the user in this thread (I only slightly modified his code): https://bbs.archlinux.org/viewtopic.php?id=63576

<policy user="myusername">
<allow own="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_interface="org.freedesktop.NetworkManagerUserSettings"/>
<deny send_interface="org.freedesktop.NetworkManagerSetting.Secrets"/>
</policy>

Now the applet shows up for my regular user, the problem being that it doesn't connect to the wireless networks (only wired). Whenever I try to connect to wireless, nothing happens (the symbol doesn't change in any way, i.e. the green spheres should start circling); I am still able to succesfully connect to wireless using root. Does anyone know what the source of this issue may be? Thank you very much in advance.
Last edited by Ipozya (2011-01-20 04:49:55)

Solved: Had to install consolekit and add "ck-launch-session" to my .xinitrc file when starting fluxbox.
Edit: Please note that this also allowed me to remove the previous change to nm-applet.conf (no longer necessary)!
Last edited by Ipozya (2011-01-20 04:54:20)

[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

[Solved] Can't get gnome network manager running

Alright this one is a head scratcher. I've folowed the wiki for network manager to a T except I can't get the network manager icon to show up (I have notification addon already running). I don't have any network loss though.
Here's my rc.conf
# /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="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Pacific"
KEYMAP="dvorak/dvorak"
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=(powernow-k8 cpufreq_ondemand cpufreq_powersave forcedeth snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# 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="myhost"
# 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
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo !eth0)
# 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 netfs crond laptop-mode dhcdbd networkmanager @alsa @hal @fam @gdm)
Last edited by dr/owned (2009-01-09 05:16:43)

I assume you're running nm-applet --sm-disable once you get a window manager session up?
Try starting networkmanager after hal. From the wiki:
You must also "disable" the default network daemon, and add the hal, dhcdbd and networkmanager daemons in this order:
DAEMONS=( ... !network hal dhcdbd networkmanager ... )

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

[SOLVED]Network Manager Applet and nmcli failing after GCC upgrade

Hi All,
So I went to update my system today and there were only like 8 or 9 updates. Like many other people I had an issue with gcc and pacman. To fix this I ran
pacman -S gcc
Then I ran:
pacman -Su
which updated pacman itself. On reboot though I noticed network manager applet was unable to find any of my network devices despite the fact that network manager was running and I had an IP address. I killed nm-applet and re-ran it and it spewed errors about not being able to connect to network manager. I tried running nmcli and it did the same thing. However, when I run nmcli as root it works. Looking at the arch wiki they suggest you be a part of the wheel and network group which I made sure I was. Everything was working up until I ran those two updates though. Anyone else have this happen or have any idea what is wrong?
Thanks,
Hemmar
EDIT: Never mind - a patch was released for consolekit which fixes the problem.
Last edited by hemmar (2012-04-13 00:36:49)

Hi guz46
I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.
Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!
Thanks for you help anyways,
Scott
EDIT:
I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:
#Static IP example
#eth0="dhcp"
ppp0="dhcp"
wlan0="dhcp"
eth0="dhcp"
INTERFACES=(ppp0 wlan0 eth0)
Thus ensuring that I can connect in order of preference.
Last edited by ScottArch (2009-11-03 18:48:47)

[SOLVED][GNOME 3] After install - no Network Manager?

Installed Arch for the first time yesterday, so I put GNOME 2 on it first to make sure everything worked before moving onto the unstable stuff. Installed GNOME 3, installed Gnome Shell, bootup, everything seems perfect, except that I have no Network Manager. No applet in the top-right corner. Clicking on the Network application under activities did nothing and neither did trying to access it from System Settings. I did a little Googling, figured that I needed to actually install networkmanager and network-manager-applet. So I did so from pacman:
pacman -S networkmanager network-manager-applet
and now I can get into the application but I'm getting an error, "The system network services are not compatible with this version," which gives me a minimal-use window with a network proxy entry and the ability to add a VPN entry.
I know my WiFi works (Intel Wireless-N 1000) because it shows up as wlan0 in iwconfig and I can connect to an unsecured network with wicd. Anyone know how I can get Gnome's Network Manager back?
Last edited by solatic (2011-04-10 20:49:41)

solatic wrote:
ah, the stupid daemon. Of course. /knockheadonwood. Might be good to link that kind of stuff to the GNOME 3 wiki entry.
Thanks for your time!
Um, did Wonder help you solve the problem ? If so, please add [SOLVED] to the thread title by editing the original post.
As to the wiki links, feel free

[SOLVED] network-manager-applet not found

Hi, I'm quite noob here, and I'm trying to install network-manager-applet with no luck;
So far I've done
# pacman -S network-manager-applet
and I got
resolving dependencies...
looking for inter-conflicts...
Targets (1): network-manager-applet-0.8-1
Total Download Size: 1.01 MB
Total Installed Size: 4.35 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from mi.mirror.garr.it : Not Found
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.nluug.nl : Not Found
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.hosteurope.de : Not Found
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp-stud.hs-esslingen.de : Not Found
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from archlinux.puzzle.ch : Not Found
error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.surfnet.nl : Not Found
warning: failed to retrieve some files from extra
error: failed to commit transaction (Not Found)
Errors occurred, no packages were upgraded.
so I tried to download the package itself and install it with
pacman -U network-manager-applet-0.8-2-x86_64.pkg.tar.xz
and the answer was
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: network-manager-applet: requires mobile-broadband-provider-info
what to do?
i cannot find in the repos the package mobile-broadband-provider-info
thank you in advance
Last edited by lsk (2010-03-10 10:15:21)

Update your system - "pacman -Syu". The clue is that the file you manually downloaded is different to the one pacman is trying to get.

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

No interfaces shown in network manager [SOLVED]

Similar Messages

Maybe you are looking for