[SOLVED] Network Manager - authentication failure

pizet · 2011-07-15 18:45:23

Hello,

I'm trying to get Network Manager working. Actually I suppose it's working, but every time I try to connect to my wireless network I get an authentication failure. Let's assume, that my key is correct. Is there any other reason, why I might get an the authentication failure? I do this through GUI, I've installed network-manager-applet package.

If it helps, here is my rc.conf, but I think, there should be nothing wrong with it:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged.
# 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
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
#
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Bratislava"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MOD_AUTOLOAD="yes"
MODULES=(loop)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# 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="arch"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=
address=
netmask=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 requires the netcfg package
#
NETWORKS=(!eth0 !wlan0)
#WIRELESS_INTERFACE="wlan0"

# -----------------------------------------------------------------------
# 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
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng dbus networkmanager netfs crond gdm)

Thanks for your help and time.

-pizet

Last edited by pizet (2011-07-16 07:54:55)

joseperezc · 2011-07-15 19:25:36

open a terminal and write ifconfig, if the output said wlan0 you have correctly configurated your wireless device and your problem can be:

1._ It also can be a poor signal reception, because you are so far or it's raining
also your modem can be between a steel (or lead) sky. So you can try to get closer and get out as many obstacles as you can between your computer and your modem

2._ In some versions of networkmanager the password files becomes corrupt because an encription "bug", in this case you could try 3 things:
-delete all connection profiles in nm applet dialog, reboot and point the network do you want (this to avoid corrupted files problem)
-pacman -Syu
-pacman -R networkmanager && pacman -S wicd (and in your rc.conf change networkmanager to wicd)

3._ in remote cases can be a memory corruption when you don't have the sufficent memory to carry all of your applications (ej. 128mb of ram and 4gb hdd) in that case you should use lighter apps or put more RAM.

- I alway use and recomend wicd https://wiki.archlinux.org/index.php/Wicd
- some lighter apps ( they always are good choices) https://wiki.archlinux.org/index.php/Li … plications

Last edited by joseperezc (2011-07-15 19:28:01)

pizet · 2011-07-15 20:37:04

Yes, I have correctly configured my wireless device. I've been connecting to my network using:

$ sudo netcfg myessid

I've tried wicd streightly away and it looks well. If I will have any problem I will write here.

Thanks for your advices and time.

Last edited by pizet (2011-07-15 20:37:35)

joseperezc · 2011-07-15 22:16:15

so... if it is solved using wicd

why not write (SOLVED) in the title?

Arch Linux

#1 2011-07-15 18:45:23

[SOLVED] Network Manager - authentication failure

#2 2011-07-15 19:25:36

Re: [SOLVED] Network Manager - authentication failure

#3 2011-07-15 20:37:04

Re: [SOLVED] Network Manager - authentication failure

#4 2011-07-15 22:16:15

Re: [SOLVED] Network Manager - authentication failure

Board footer