Wpa_supplicant and netcfg

Hi, I just reinstalled Archlinux x86_64 on a new SSD I got. I was setting up the internet connection during installation and I used netcfg.
I create a file using the examples depending on what I need and place it in : /etc/network.d/
Then I use netcfg-menu to connect to the netowork.
My problem is I tried doing this again and I get : Please install 'dialog' to use netcfg-menu
In the beginner guide, I see that you can modify wpa_supplicant to connect to internet, I was wondering if it's just another way of doing it? or are these two working together?
I read the manual on both but it didn't answer my question. I tried to configure my wpa_supplicant but it didn't work, I think because my network is hidden. Then I tried to edit the wpa_supplicant file for hidden network using ssid=1 (if i remember well, I used what was in the man) and it didn't work.
Last edited by trixrabbit (2012-12-02 17:34:41)

trixrabbit wrote:
Then I use netcfg-menu to connect to the netowork.
My problem is I tried doing this again and I get : Please install 'dialog' to use netcfg-menu
You are trying to use netcfg-menu.
The error message is telling you that you need to install the "dialog" package to use netcfg-menu.
Solution: install the "dialog" package (pacman -S dialog).
edit: You can also use netcfg without the dialog package. For example, "netcfg -u <profile>", "netcfg -l". See "netcfg --help" for more options.
10PinkPanther wrote:Wiki says that dialog is needed in some cases.Do you see your network when you run wifi-menu?
Last edited by Xyne (2012-12-02 19:12:18)

Similar Messages

[Fixed...] wpa_supplicant and netcfg stopped working since updates

Hello, I am new to the forums and have run into a problem with wpa_supplicant and netcfg (though I believe the problem resides with wpa_supplicant).
A bit about me - This is my first "intermediate" linux distro (I tried fedora back when it was version 6 but didn't get terribly far with it). I have mostly been using Ubuntu (because it is out of the box and easy), but I ran out of use for an old laptop I had around and chose to install a minimalist distro on it (hence arch). The learning curve was a bit steep, but it is intersting and makes for a nice learning experience at the very least.
The problem:
I updated my system (which I do each time there is an available update on linux because it normally fixes things) on the 11th and everything was working great. However, my ip lease expired over the weekend (apparently) and as I am mostly a windows user (sorry, but it is true) I didn't notice it until today (when I went to check pacman for any updates and no longer had an internet connection).
It appears that the last round of updates I installed included updates for wpa_supplicant in them and changed the way things are supposed to be done in the /etc/wpa_supplicant.conf file. It looked like so beforehand (and still does though I have attempted to rewrite with the new format - sadly that hasn't worked out and I am here as a result):
network={
ssid="zelda"
psk=<... long key here> # note - Like I said, this was working before, I removed the key on purpose.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
And here is what I have attempted with my new wpa_supplicant.conf file:
network={
ssid="zelda"
psk=<... long key here>
scan_ssid=1
priority=1
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
Here are the steps I am taking to attempt and access the internet (manually):
sudo ifconfig wlan0 up
sudo wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
<wait a bit>
sudo dhcpcd wlan0
dhcpcd[2281]: version 5.2.12 starting
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquited
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: boradcasting for a lease
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquired
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: broadcasting for a lease
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquired
dhcpcd[2281]: wlan0: rebinding lease for <IP>
dhcpcd[2281]: timed out
And if I attempt to use netcfg (in code because it uses spaces):
sudo netcfg zelda
:: zelda up [BUSY]
> WPA Authentication/Association Failed
[FAIL]
Here is my /etc/network.d/zelda file (like I said, this used to work. I haven't modified this file though):
CONNECTION='wireless'
DESCRIPTION='Home network'
INTERFACE='wlan0'
SECURITY='wpa-config'
WPA_CONF='/etc/wpa_supplicant.conf'
IP='dhcp'
Any help would be appreciated.
<edit>
Well, this is what I like to see. Apparently it wasn't as difficult as I was making it out to be, and the second wpa_supplicant.conf file I posted (the new one) works. I just had to do a reboot for it to notice the changes (though this does lead me to wonder if a daemon caches the wpa_supplicant entries...). It is all working now.
</edit>
Last edited by BetaWar (2011-05-18 23:55:22)

trixrabbit wrote:
Then I use netcfg-menu to connect to the netowork.
My problem is I tried doing this again and I get : Please install 'dialog' to use netcfg-menu
You are trying to use netcfg-menu.
The error message is telling you that you need to install the "dialog" package to use netcfg-menu.
Solution: install the "dialog" package (pacman -S dialog).
edit: You can also use netcfg without the dialog package. For example, "netcfg -u <profile>", "netcfg -l". See "netcfg --help" for more options.
10PinkPanther wrote:Wiki says that dialog is needed in some cases.Do you see your network when you run wifi-menu?
Last edited by Xyne (2012-12-02 19:12:18)

How does systemd, wpa_supplicant, and dhcpcd work together? rtl8188su

I'm running arch with alarm (done a pacman -Syu to get latest everything) on an original Raspberry Pi model B.
I'm using a Belkin USB adapter which is really a Realtek rtl8188su chip, which is recognized with the r8712u module. I want to do it all from the command line (not running a GUI, as this Pi won't be having a display attached.)
The system recognizes the built-in Ethernet, and dhcpcd assigns it an IP address, so I can SSH into it and try to bring up the wlan0 interface.
I'm an old-school Linux/UNIX hacker, but I haven't had a lot of experience with systemd, nor with wpa_supplicant or even much of udev, so I'm a bit lost in trying to make this work.
I made sure wpa_supplicant and wpa_cli were installed. Then I edited /etc/wpa_supplicant/wpa_supplicant.conf to add my ssid/passphrase, and saved it as /etc/wpa_supplicant/wpa_supplicant.wlan0.conf. I also did "systemctl enable wpa_supplicant," and I've rebooted.
The status of the system is that it does not enable the wlan0 interface. Further, the wpa_cli tool does not work. If I run just "wpa_cli" or with a command like "wpa_cli list" then I get the error:
could not connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
This is weird, because wpa_supplicant is running in dbus listen mode:
[root@alarmpi ~]# ps alx | grep [w]pa
0 0 94 1 20 0 5636 1416 poll_s Ss ? 0:00 /usr/sbin//wpa_supplicant -u
Each time I boot, I get this message in /dev/log/messages.log:
Nov 10 01:40:06 alarmpi kernel: [ 648.082619] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Now, if I insted does "systemctp stop wpa_supplicant" and start it manually, it does bring up the interface:
[root@alarmpi ~]# wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.wlan0.conf
wlan0: Trying to associate with a0:21:b7:63:a1:98 (SSID='jwatte' freq=2462 MHz)
wlan0: Associated with a0:21:b7:63:a1:98
wlan0: WPA: Key negotiation completed with a0:21:b7:63:a1:98 [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to a0:21:b7:63:a1:98 completed (auth) [id=0 id_str=]
[root@alarmpi ~]# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a86:3bff:feb4:c21a prefixlen 64 scopeid 0x20<link>
ether 08:86:3b:b4:c2:1a txqueuelen 1000 (Ethernet)
RX packets 30 bytes 3813 (3.7 KiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 5 bytes 610 (610.0 B)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0
[root@alarmpi ~]#
However, dhcpcd is not auto-launched to provide an IP address to the interface.
So, how is this supposed to work? How am I supposed to configure the system so that all the pieces click together? It should start wpa_supplicant with the right config data, and/or configure it over dbus correctly, and it should make sure dhcpcd is then invoked to obtain an IP address. I have *no idea* how to actually configure this to do the right thing, because all the tutorials and documentation I can find on the web is either very abstract ("services live in /usr/lib/systemd/...") or just claim that things "will magically work" if I have the correct configuration.
Help! Don't know what to do next!

Your manual wpa_supplicant invocation result looks good, so the major hurdle you have taken already.
For wireless you need a management method that acts as interface to wpa_supplicant and dhcp and watches the connection. Before you browse off to archlinuxarm, also read the non-abstract introduction here: https://wiki.archlinux.org/index.php/Wi … management

[SOLVED] WPA_SUPPLICANT and rt2500 chipset cards [SOLVED]

EDIT:
If you want to make an rt2500 chipset wireless card work with wpa_supplicant (and it doesn't already), maybe you have tried to run wpa_supplicant and got a bunch of errors saying nasty things about IOCTRL, this means, most likely, that wpa_supplicant is having trouble communicating with your wireless card. One problem (my problem) was the driver, the old rt2500 driver.
Are you using an old rt2500 driver, or the newer rt2500pci driver? You can probably tell by looking at your rc.conf file, in the section called "MODULES", if you have rt2500 listed, you're
loading the old driver, so you should put an "!" in front to disable it. You also need to make sure you have the rt2500pci drive and (I think) the rt2x00lib and rt2x00pci modules listed. I'm pretty sure these are included with an up to date stock kernel.
I guess another way to look for the driver would be to boot your computer and run "dmesg | more" and parse through the output, or "dmesg | more | grep | rt2500", which should find you any lines that contain text "rt2500".
Now, if you've been using that old rt2500 driver, your wireless card has probably been calling itself "ra0", assuming it's your only card using the rt2500 driver, when you switch to the new driver, it will call itself "wlan?" where ? is some number. It's probably wlan0, unless you have another wireless card, I do (a Broadcom card that has never worked) so mine is actually called wlan1. There are tutorials for making Broadcom cards work, but that's a different kettle of worms and I'm not qualified to talk about it since mine doesn't.
Now it should work with wpa_supplicant using the driver "wext", which should be the default for wpa_supplicant, but just to be safe you can type:
wpa_supplicant -d -iwlan? -Dwext -c/path_to_config_file/your_config_file
| | | |
| | | Config file to use
| | driver to use
| interface to use
|
tell wpa_supplicant to be more verbose, -dd is even more verbose
You probably already read the man pages and wiki for wpa_supplicant, but if you haven't noticed yet the syntax for the options is -oPARAMETER there's no seperation between the option and it's argument.
Now if you did all this, and you're not getting IOCTRL errors, then you're wireless driver and wpa_supplicant are probably communicating just fine. If you're still not able to connect then the problem could be one of:
Unable to associate with access point, possibly because of weak signal or MAC filtering
Errors in your wpa_supplicant config file, maybe a PSK is wrong, maybe you're specifying a protocol wrong? If you have some sort of complex configuration / AP setup, it might be best too try a simpler configuration with an AP you can administer (like a home portal, if you have one), see if you can get that to work, and then figure out why your super complex configuration to work.
If you want too, read tomk's posts below, my other posts are (most likely) not helpful.
_____________________________ORGINAL POST__ORGINAL TOPIC:Can BSD drivers work w/ WPA_SUPPLICANT in Linux?_____________________________________
Hello all,
Recently I installed FreeBSD on a laptap with a rt2500 chipset wireless card and was able, for the first time ever, to use wpa encrypted networking via wpa_supplicant. Then I screwed up my rc.conf file, tried to fix it, and apparently completely broke the system.
So I decided to install arch, because I didn't really want to rebuild the ports I had installed, but then, it appears, I can't get wpa_supplicant to work. Not so, so bad for my home network (I can either use an ethernet connection or switch my router to an open connection), but I'm intrigued enough at the prospect of being able to use the wifi network at my university, that I really want this to work now.
So I messed around with wpa_supplicant, but apparently wpa_supplicant doesn't support the rt2500 driver. But I know the generic BSD driver works (wext does not), so, perhaps naively, I tried to build wpa_supplicant with the BSD driver enabled.
But, when I did this, mkpkg tells me that my config file is bad. Is this because I'm trying to enable the BSD driver?
I realize it might be helpful to look at my config file, but for the moment, I'm too lazy to fiddle with things to get the file of the laptop, but it occurs to me that it might just be downright silly to expect a bsd driver to work with linux. So if I"m being stupid, could someone please tell me?
-thanks!
Last edited by pseudonomous (2008-08-24 21:29:26)

This is the last config file I tried:
# Example wpa_supplicant build time configuration
# This file lists the configuration options that are used when building the
# hostapd binary. All lines starting with # are ignored. Configuration option
# lines must be commented out complete, if they are not to be included, i.e.,
# just setting VARIABLE=n is not disabling that variable.
# This file is included in Makefile, so variables like CFLAGS and LIBS can also
# be modified from here. In most cases, these lines should use += in order not
# to override previous values of the variables.
# Uncomment following two lines and fix the paths if you have installed OpenSSL
# or GnuTLS in non-default location
#CFLAGS += -I/usr/local/openssl/include
#LIBS += -L/usr/local/openssl/lib
# Some Red Hat versions seem to include kerberos header files from OpenSSL, but
# the kerberos files are not in the default include path. Following line can be
# used to fix build issues on such systems (krb5.h not found).
#CFLAGS += -I/usr/include/kerberos
# Example configuration for various cross-compilation platforms
#### sveasoft (e.g., for Linksys WRT54G) ######################################
#CC=mipsel-uclibc-gcc
#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
#CFLAGS += -Os
#CPPFLAGS += -I../src/include -I../../src/router/openssl/include
#LIBS += -L/opt/brcm/hndtools-mipsel-uclibc-0.9.19/lib -lssl
#### openwrt (e.g., for Linksys WRT54G) #######################################
#CC=mipsel-uclibc-gcc
#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
#CFLAGS += -Os
#CPPFLAGS=-I../src/include -I../openssl-0.9.7d/include \
#-I../WRT54GS/release/src/include
#LIBS = -lssl
# Driver interface for Host AP driver
CONFIG_DRIVER_HOSTAP=y
# Driver interface for Agere driver
#CONFIG_DRIVER_HERMES=y
# Change include directories to match with the local setup
#CFLAGS += -I../../hcf -I../../include -I../../include/hcf
#CFLAGS += -I../../include/wireless
# Driver interface for madwifi driver
CONFIG_DRIVER_MADWIFI=y
# Change include directories to match with the local setup
CFLAGS += -I../madwifi
# Driver interface for Prism54 driver
# (Note: Prism54 is not yet supported, i.e., this will not work as-is and is
# for developers only)
#CONFIG_DRIVER_PRISM54=y
# Driver interface for ndiswrapper
CONFIG_DRIVER_NDISWRAPPER=y
# Driver interface for Atmel driver
CONFIG_DRIVER_ATMEL=y
# Driver interface for Broadcom driver
#CONFIG_DRIVER_BROADCOM=y
# Example path for wlioctl.h; change to match your configuration
#CFLAGS += -I/opt/WRT54GS/release/src/include
# Driver interface for Intel ipw2100/2200 driver
#CONFIG_DRIVER_IPW=y
# Driver interface for generic Linux wireless extensions
CONFIG_DRIVER_WEXT=y
# Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
CONFIG_DRIVER_BSD=y
CFLAGS += -I/usr/local/include
LIBS += -L/usr/local/lib
# Driver interface for Windows NDIS
#CONFIG_DRIVER_NDIS=y
#CFLAGS += -I/usr/include/w32api/ddk
#LIBS += -L/usr/local/lib
# For native build using mingw
#CONFIG_NATIVE_WINDOWS=y
# Additional directories for cross-compilation on Linux host for mingw target
#CFLAGS += -I/opt/mingw/mingw32/include/ddk
#LIBS += -L/opt/mingw/mingw32/lib
#CC=mingw32-gcc
# By default, driver_ndis uses WinPcap for low-level operations. This can be
# replaced with the following option which replaces WinPcap calls with NDISUIO.
# However, this requires that WZC is disabled (net stop wzcsvc) before starting
# wpa_supplicant.
# CONFIG_USE_NDISUIO=y
# Driver interface for development testing
#CONFIG_DRIVER_TEST=y
# Driver interface for wired Ethernet drivers
CONFIG_DRIVER_WIRED=y
# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is
# included)
CONFIG_IEEE8021X_EAPOL=y
# EAP-MD5
CONFIG_EAP_MD5=y
# EAP-MSCHAPv2
CONFIG_EAP_MSCHAPV2=y
# EAP-TLS
CONFIG_EAP_TLS=y
# EAL-PEAP
CONFIG_EAP_PEAP=y
# EAP-TTLS
CONFIG_EAP_TTLS=y
# EAP-GTC
CONFIG_EAP_GTC=y
# EAP-OTP
CONFIG_EAP_OTP=y
# EAP-SIM (enable CONFIG_PCSC, if EAP-SIM is used)
#CONFIG_EAP_SIM=y
# EAP-PSK (experimental; this is _not_ needed for WPA-PSK)
#CONFIG_EAP_PSK=y
# EAP-PAX
#CONFIG_EAP_PAX=y
# LEAP
CONFIG_EAP_LEAP=y
# EAP-AKA (enable CONFIG_PCSC, if EAP-AKA is used)
#CONFIG_EAP_AKA=y
# EAP-SAKE
#CONFIG_EAP_SAKE=y
# EAP-GPSK
#CONFIG_EAP_GPSK=y
# Include support for optional SHA256 cipher suite in EAP-GPSK
#CONFIG_EAP_GPSK_SHA256=y
# PKCS#12 (PFX) support (used to read private key and certificate file from
# a file that usually has extension .p12 or .pfx)
CONFIG_PKCS12=y
# Smartcard support (i.e., private key on a smartcard), e.g., with openssl
# engine.
CONFIG_SMARTCARD=y
# PC/SC interface for smartcards (USIM, GSM SIM)
# Enable this if EAP-SIM or EAP-AKA is included
#CONFIG_PCSC=y
# Development testing
#CONFIG_EAPOL_TEST=y
# Replace native Linux implementation of packet sockets with libdnet/libpcap.
# This will be automatically set for non-Linux OS.
#CONFIG_DNET_PCAP=y
# Select control interface backend for external programs, e.g, wpa_cli:
# unix = UNIX domain sockets (default for Linux/*BSD)
# udp = UDP sockets (default for Windows)
# y = use default (backwards compatibility)
# If this option is commented out, control interface is not included in the
# build.
CONFIG_CTRL_IFACE=y
# Include support for GNU Readline and History Libraries in wpa_cli.
# When building a wpa_cli binary for distribution, please note that these
# libraries are licensed under GPL and as such, BSD license may not apply for
# the resulting binary.
#CONFIG_READLINE=y
# Remove debugging code that is printing out debug message to stdout.
# This can be used to reduce the size of the wpa_supplicant considerably
# if debugging code is not needed. The size reduction can be around 35%
# (e.g., 90 kB).
#CONFIG_NO_STDOUT_DEBUG=y
# Remove WPA support, e.g., for wired-only IEEE 802.1X supplicant, to save
# 35-50 kB in code size.
#CONFIG_NO_WPA=y
# Remove WPA2 support. This allows WPA to be used, but removes WPA2 code to
# save about 1 kB in code size when building only WPA-Personal (no EAP support)
# or 6 kB if building for WPA-Enterprise.
#CONFIG_NO_WPA2=y
# Remove AES extra functions. This can be used to reduce code size by about
# 1.5 kB by removing extra AES modes that are not needed for commonly used
# client configurations (they are needed for some EAP types).
#CONFIG_NO_AES_EXTRAS=y
# Select configuration backend:
# file = text file (e.g., wpa_supplicant.conf)
# winreg = Windows registry (see win_example.reg for an example)
CONFIG_BACKEND=file
# Select program entry point implementation:
# main = UNIX/POSIX like main() function (default)
# main_winsvc = Windows service (read parameters from registry)
# main_none = Very basic example (development use only)
#CONFIG_MAIN=main
# Select wrapper for operatins system and C library specific functions
# unix = UNIX/POSIX like systems (default)
# win32 = Windows systems
# none = Empty template
#CONFIG_OS=unix
# Select event loop implementation
# eloop = select() loop (default)
# eloop_win = Windows events and WaitForMultipleObject() loop
# eloop_none = Empty template
#CONFIG_ELOOP=eloop
# Select layer 2 packet implementation
# linux = Linux packet socket (default)
# pcap = libpcap/libdnet/WinPcap
# freebsd = FreeBSD libpcap
# winpcap = WinPcap with receive thread
# ndis = Windows NDISUIO (note: requires CONFIG_USE_NDISUIO=y)
# none = Empty template
#CONFIG_L2_PACKET=linux
# IEEE 802.11i/IEEE 802.11e STAKey negotiation for direct link connection
#CONFIG_STAKEY=y
# Proposed replacement for STAKey negotiation: PeerKey handshake for
# Station to Station Link
CONFIG_PEERKEY=y
# Select TLS implementation
# openssl = OpenSSL (default)
# gnutls = GnuTLS (needed for TLS/IA, see also CONFIG_GNUTLS_EXTRA)
# internal = Internal TLSv1 implementation (experimental)
# none = Empty template
#CONFIG_TLS=openssl
# Whether to enable TLS/IA support, which is required for EAP-TTLSv1.
# You need CONFIG_TLS=gnutls for this to have any effect. Please note that
# even though the core GnuTLS library is released under LGPL, this extra
# library uses GPL and as such, the terms of GPL apply to the combination
# of wpa_supplicant and GnuTLS if this option is enabled. BSD license may not
# apply for distribution of the resulting binary.
#CONFIG_GNUTLS_EXTRA=y
# If CONFIG_TLS=internal is used, additional library and include paths are
# needed for LibTomCrypt and TomsFastMath.
#LTC_PATH=/usr/src/libtomcrypt-1.11
#TFM_PATH=/usr/src/tomsfastmath-0.09
#CFLAGS += -I$(LTC_PATH)/src/headers
#LIBS += -L$(LTC_PATH) -L$(TFM_PATH)
#LIBS_p += -L$(LTC_PATH) -L$(TFM_PATH)
# Integrate ndis_events.exe functionality into wpa_supplicant.
# This is only for Windows builds and requires WMI-related header files and
# WbemUuid.Lib from Platform SDK even when building with MinGW.
#CONFIG_NDIS_EVENTS_INTEGRATED=y
#PLATFORMSDKLIB="/opt/Program Files/Microsoft Platform SDK/Lib"
# Add support for DBus control interface
#CONFIG_CTRL_IFACE_DBUS=y
# Add support for loading EAP methods dynamically as shared libraries.
# When this option is enabled, each EAP method can be either included
# statically (CONFIG_EAP_<method>=y) or dynamically (CONFIG_EAP_<method>=dyn).
# Dynamic EAP methods are build as shared objects (eap_*.so) and they need to
# be loaded in the beginning of the wpa_supplicant configuration file
# (see load_dynamic_eap parameter in the example file) before being used in
# the network blocks.
# Note that some shared parts of EAP methods are included in the main program
# and in order to be able to use dynamic EAP methods using these parts, the
# main program must have been build with the EAP method enabled (=y or =dyn).
# This means that EAP-TLS/PEAP/TTLS/FAST cannot be added as dynamic libraries
# unless at least one of them was included in the main build to force inclusion
# of the shared code. Similarly, at least one of EAP-SIM/AKA must be included
# in the main build to be able to load these methods dynamically.
# Please also note that using dynamic libraries will increase the total binary
# size. Thus, it may not be the best option for targets that have limited
# amount of memory/flash.
CONFIG_DYNAMIC_EAP_METHODS=y
# Include client MLME (management frame processing).
# This can be used to move MLME processing of Devicescape IEEE 802.11 stack
# into user space.
#CONFIG_CLIENT_MLME=y
# Currently, driver_devicescape.c build requires some additional parameters
# to be able to include some of the kernel header files. Following lines can
# be used to set these (WIRELESS_DEV must point to the root directory of the
# wireless-dev.git tree).
WIRELESS_DEV=/lib/modules/2.6.24-ARCH/build
CFLAGS += -I$(WIRELESS_DEV)/net/mac80211
Last edited by pseudonomous (2008-08-24 08:23:23)

Wireless problems with AR5212, wpa_supplicant and dhcpcd. [solved]

Dear friends,
I am currently experiencing problems with getting my AR5212 wireless card to work with wpa_supplicant and the ath5k driver. Everything is set up according to the Arch Wireless Setup Wiki http://wiki.archlinux.org/index.php/Wireless_Setup. First, I do the following:
# ifconfig wlan0 up
# iwconfig wlan0 essid Prairiedog
# wpa_supplicant -B -Dwext -iwlan0 -c /etc/wpa_supplicant.conf
It goes well even up until the point where I wish to request a dhcp lease from my router.
# dhcpcd wlan0
wlan0: dhcpd 4.0.10 starting
wlan0: braodcasting for a lease
wlan0: offered 192.168.0.2 from 192.168.0.1 'm'
wlan0: checking 192.168.0.2 is available on attached networks
wlan0: leased 192.168.0.2 for 86400 seconds
Excerpt from ifconfig:
Link encap:Ethernet HWaddr 00:56:A4:44:DA:1A
inet addr:192.168.0.2 Bcast: 255.255.255.255 Mask 255.255.255.0
My wireless card should then be associated with 192.168.0.2...
What confuses me is that I cannot get the my wireless net card to ping any addresses. It seems that there is no connection to the outer world, despite the fact that an address has been assigned by my router. When I for example do a
# ping www.google.com
I get the response
ping: unknown host www.google.com
What is even more strange is that I cannot ping the router itself:
# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data
From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
Anyone who has had the same problem and actually solved it? I would really like to get this distribution up and running on my IBM X32 laptop. The simpleness and the philosophy behind it is very appealing to me. But without a wireless connection it is pretty pointless. Any pointer or help will be highly appreciated
Last edited by kitabu (2009-12-20 10:37:29)

Hi Ekimino,
I did as you suggested. I requested a dhcp lease and the router gave me 192.168.0.2. But I seems that I am losing connection immediately afterwards. When I ping an external address like www.google.com I get "unknown host" and when I ping my router I get the message that the destination host is unreachable. Perhaps the issue lies with dhcpcd or maybe a combination of the ath5k and dhcpcd?

Using wpa_supplicant and iwconfig to setup wifi during boot.

I have my gnome desktop running. My wireless network at my house is hidden and secured via wpa passkey.
Eitherway, I have two commands that need to be run during boot...
iwconfig eth1 essid xxxxx
wpa_supplicant -Dwext -ieth1 -c/etc/wpa_details.conf
Where would be the best place to stick that?
On the other hand!!!
If there is a better way to do it, please by all means suggest it!
Thanks,
Rich

pacman -S netcfg and you can use either the wpa-config or wpa options for security. Take a look at the provided examples, and the wiki
http://wiki.archlinux.org/index.php/Network_profiles

Wpa_supplicant and networkmanager issues

When I first installed a KDE frontend to networkmanager, it successfully connected to a WPA2-protected WAP but it stopped working, providing an error ("Resource not found" when I tried to connect) and failed to save the WPA2 key when I opened the window. I tried reinstalling it, but these issues continued. I later decided to connect to the network manually. I followed the following instructions: https://wiki.archlinux.org/index.php/Wp … icant.conf but dmesg shows wlan0 authenticating and associating with the WAP, but immediately deassociating and deauthenticating ("by local choice, (reason=3)"). The interface wlan0 is up and successfully scans for WAPs in range.
Any ideas?
I am using ath9k for the card, and -Dwext for wpa_supplicant.
Last edited by rnabioullin (2011-08-04 15:22:28)

Perhaps it's time to simplify your setup. Try using netcfg and see if you can connect; you may consider running your router with only Wep or no security at all to see if that is at fault or not.
If netcfg works (or not), try wicd. The fact that you got it to connect manually tells me that your software issue is with a middle-man (so to speak), IE networkmanager would be my guess.

Systemd and netcfg menu

I am experiencing problem that after switching completely to systemd netcfg service is no longer presenting menu to select network profile.
in other words:
when /etc/conf.d/netcfg contains
NETWORKS=(menu)
profile named main is started (wired dhcp) but no dialog menu is presented and I have no possibility to choose profile I want.
Does anyone see same problem? Did I missed anything?

Yes, so you got your answer: This cannot work with systemd. (This is not entirely true, but implementing a clean solution that supports systemd is overkill for this use case.)
My take on choosing profiles on boot:
If you use a wired connection, you should rely on the site's DHCP server to handle your connection properly (after all, it works for all Mac and Windows users, and for most other Linux users).
If you use a wireless connection, net-auto-wireless is capable of automatically selecting the correct profile for you, no manual intervention required.

Systemd and Netcfg

I am using Arch linux with systemd.
All packages are recent.
And I encountered the following behavour when configuring network:
netcfg.service starts before network interfaces appear in the system (modules are not yet loaded), so I get the following error in syslog:
netcfg-daemon[463]: :: mgmt up Interface eth0 does not exist
netcfg-daemon[463]: [fail]
So I added the following line to "Unit" to /etc/systemd/system/multi-user.target.wants/netcfg.service:
[Unit]
After=sys-class-net-eth0.device
But it didn't help - the netcfg-daemon still starts before the symlink /sys/calss/net/eth0 appears.
Please advise - what can be done to fix the problem with network configuration?

Another suggestion is to put a timeout in netcfg when it's checking the existence of the interface (ex. 'eth0'). Netcfg already does that while waiting for the LINK UP and CARRIER flags right after doing a 'ip link set dev "$INTERFACE" up'.
In the /usr/lib/network/connections/ethernet script of netcfg, it assumes $INTERFACE (ex. 'eth0') is already existing, or else it will fail. I commented the code below #### where the updated code should be placed. There's an example timeout_wait() near the bottom when it waits for 5 secs for the CARRIER signal.
/usr/lib/network/connections/ethernet (part of netcfg).
ethernet_up() {
load_profile "$1"
SYSCTL_INTERFACE="${INTERFACE/.//}"
#### As implemented now is_interface() exits on error when /sys/class/net/$INTERFACE doesn't exist yet.
#### Insert a timeout_wait here (30 sec max?) so netcfg can wait for /sys/class/net/eth0 to show up before failing:
if ! is_interface "$INTERFACE"; then
report_iproute "Interface $INTERFACE does not exist"
fi
# Disable IPv6 before bringing the interface up to prevent SLAAC
if [[ "$IP6" == "no" ]]; then
sysctl -q -w "net.ipv6.conf.$SYSCTL_INTERFACE.disable_ipv6=1"
fi
report_debug ethernet_up bring_interface up "$INTERFACE"
bring_interface up "$INTERFACE"
if ! checkyesno "${SKIPNOCARRIER:-no}"; then
# Some cards are plain slow to come up. Don't fail immediately.
if ! timeout_wait "${CARRIER_TIMEOUT:-5}" '(( $(< "/sys/class/net/$INTERFACE/carrier") ))'; then
report_iproute "No connection"
fi
fi
The is_interface() funtions is in /usr/lib/network/network (also part of netcfg).
/usr/lib/network/network (part of netcfg).
is_interface() {
local INTERFACE="$1"
if [[ ! -e "/sys/class/net/$INTERFACE" ]]; then
if ! echo "$INTERFACE" | grep -F -q ":"; then
return 1
fi
fi
return 0
The timeout_wait() function is in /usr/lib/network/globals (also part of netcfg).
/usr/lib/network/globals (part of netcfg).
## Waits until a statement succeeds or a timeout occurs
# $1: timeout in seconds
# $2...: condition command
function timeout_wait() {
local timeout="$1"
(( timeout *= 10 ))
shift
while ! eval "$*"; do
(( timeout-- > 0 )) || return 1
sleep 0.1
done
return 0
This would be a viable solution until the systemd device dependencies are worked out. I'm not a confident bash coder so I leave others to work this out. Probably takes 2 min for the experienced ones.

Systemd-networkd, wpa_supplicant and multiple USB Wifi adapters

TL;DR:
Is there a way to run a single wpa_supplicant process that handles any kind of USB WiFi adapter in connection with systemd-networkd?
Long version:
I'm running systemd-networkd, which has made networking setup a lot easier for wired interfaces. I'd like to make it just as easy for WiFi interfaces, but it seems there's some kind of wildcard support missing for wpa_supplicant. My question is whether I got this right, or there is some trick somewhere I didn't think of.
Here's my /etc/systemd/network/wifi.network:
[Match]
Name=wlp*
[Network]
DHCP=v4
In addition, I'm running:
systemctl start wpa_supplicant@wlp0s2f1u10
because that's the interface that my current WiFi USB adapter comes up on. This goes with /etc/wpa_supplicant/wpa_supplicant-wlp0s2f1u10.conf:
ctrl_interface=/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="something"
psk="else"
This all works fine, except that:
I have to plug my USB Wifi adapter into this exact USB port, otherwise the interface name changes and wpa_supplicant isn't running there
if I plug in a different USB WiFi adapter (I have a zoo; nothing exceptional I guess, but it's a pain to keep track of which goes with which computer), the interface name may be different and wpa_supplicant isn't running there
systemd-networkd solved that problem nicely with the wildcard in the interface name above (Name=wlp*). (Also, dhcpcd -- which I'm not using in this setup -- can be told to listen to "all interface" which is sort of similar)
My question: can I do something similar with wpa_supplicant, so I don't have to run a separate wpa_supplicant daemon on all possible interface names?
I'm guessing the answer is No (and I'd like confirmation on that).
Secondly, perhaps I can write one or more udev rules that will present all of those possible interfaces as wlan0, wlan1 or such. In which case I could presumably run wpa_supplicant@wlan0 only and be happy (assuming that wpa_supplicant is happy to run even as long as the interface does not exist. Does it?) Anybody have any hints how to go about this, I haven't done that.
Thirdly, if neither of those are viable, is this a reasonable-enough set of requirements so it would make sense to run this by the wpa_supplicant developers as a possible future feature?
Last edited by jernst (2015-01-11 05:54:31)

jernst wrote:
systemd-networkd solved that problem nicely with the wildcard in the interface name above (Name=wlp*). (Also, dhcpcd -- which I'm not using in this setup -- can be told to listen to "all interface" which is sort of similar)
My question: can I do something similar with wpa_supplicant, so I don't have to run a separate wpa_supplicant daemon on all possible interface names?
networkd "solved" nothing here. This is a mere coincidence that the wlp* wildcard works. For instance, you might have an interface called "wls1". Also, wpa_supplicant doesn't "listen" because "listen" applies to the TCP/IP layer. wpa_supplicant works at the frame level, so I'm not sure what you mean. If you want software that _manages_ multiple wifi interfaces, use netctl.
jernst wrote:I'm guessing the answer is No (and I'd like confirmation on that).
Correct.
jernst wrote:Secondly, perhaps I can write one or more udev rules that will present all of those possible interfaces as wlan0, wlan1 or such. In which case I could presumably run wpa_supplicant@wlan0 only and be happy (assuming that wpa_supplicant is happy to run even as long as the interface does not exist. Does it?) Anybody have any hints how to go about this, I haven't done that.
For the udev part, do something like
: cat /etc/udev/rules.d/10-network.rules
SUBSYSTEM=="net", ATTR{address}=="a1:b1:c1:d1:e1:f1", NAME="wl0"
SUBSYSTEM=="net", ATTR{address}=="a2:b2:c2:d2:e2:f2", NAME="wl1"
Then, modify [email protected] as
: diff usr/lib/systemd/system/[email protected]{,.new}
+++ usr/lib/systemd/system/[email protected] 2015-01-12 11:45:10.839852357 -0700
--- usr/lib/systemd/system/[email protected] 2015-01-12 11:44:56.843027430 -0700
@@ -1,5 +1,6 @@
[Unit]
Description=WPA supplicant daemon (interface- and nl80211 driver-specific version)
-Requires=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
# NetworkManager users will probably want the dbus version instead.
so that the unit doesn't fail if the adapter is not plugged. However, this solution is suboptimal (Think what happens if you suddenly remove the adapter)... You can try to use "BindsTo=" instead of "Requires=" but I wonder if you get errors on startup if the adapter is absent...
jernst wrote:Thirdly, if neither of those are viable, is this a reasonable-enough set of requirements so it would make sense to run this by the wpa_supplicant developers as a possible future feature?
No. wpa_supplicant is only supposed to to what it's told. It is not a canned network management solution.

Ath9k and netcfg

Does anyone else find that
QUIRKS=(wpaessid)
Is needed for a WPA2 network with the ath9k driver? If it's not just me I will add it to the wiki.
P.S. using netcfg from testing and wireless-dbus connection, great work iphitus!

Does anyone else find that
QUIRKS=(wpaessid)
Is needed for a WPA2 network with the ath9k driver? If it's not just me I will add it to the wiki.
P.S. using netcfg from testing and wireless-dbus connection, great work iphitus!

Wpa_supplicant and network profiles

I have recently changed from Fedora Core to Archlinux and found it great. I've just managed to also get my laptop on my university wifi with the aid of the Linux Society here (almost all Ubuntu users) as there is no official help for this. However this doesn't work as well as I'd like. I am prompted to change my password every few weeks (and as a security conscious student, I do) but the only way I've got wpa_supplicant to work is to write my username and password into the conf file.
I have already got some network profiles set up as I have a separate network at my flat. I would like to create a separate profile for changing the password in my wpa_supplicant.conf file, Is this possible?
Currently my profiles are set up thus:
Bahamut - Wyrms network downstairs
Falkor - Wyrms network upstairs
none - no network
uni - UAD airconnect
I would like to add another one that would ask for a new password and then overwrite my wpa_supplicant.conf file with a new one, then connecting to the university network, without having to log in, change it manually, then restart networking.
Thanks in advance
Nistur

Might be worth filing a bug report with the intel wireless devs, the ds part sounds like a beta or something.

Wicd And Netcfg not reconnecting from Sleep\Suspend

Hi, I've installed both of these network managers and neither one, after the laptop going to sleep\suspend\hibernate is able to reconnect to my wifi network. I'm using simple WEP encryption. I have to restart the machine in order for them to reconnect again, does anyone have an idea why this is happening?
Thank you

chpln wrote:
Could you post the output of
$ lspci | grep Network
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
What happens after suspending, does it appear to attempt connection? In particular, what is the output of:
iwconfig
Does manually brining the connection down / up with netcfg give any interesting errors?
I get:
lspci | grep Network
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"60O00"
Mode:Managed Frequency:2.412 GHz Access Point: 00:15:05:ED:19:F7
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=59/70 Signal level=-51 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Weird thing is that when I shutdown or restart the system isn't able to stop the daemon and gives a FAILED mark next to it because of python or something, is that normal?

[SOLVED] Wireless connect with username and password

I just recently installed Arch on my computer but have used *buntu for a couple of years so I'm not completely lost in the Linux-world.
Anyway, my college have a wireless setup that requires you to log in with your username and password. I used wicd in *buntu but the reason I installed Arch is because I want to know how to do stuff manually, and not only automagically.
So, the problem I have is that I don't know how to connect to it using wpa_supplicant and netcfg. I've googled about it but haven't seen any good examples, or how-to's.
I've a profile for my home network but I only have a WPA key here so that was easy with the wireless guide, so I know some basics about wpa_supplicant anyway.
This is what "iwlist wlan0 scan" give me:
Address: 0A:06:01:8D:A7:24
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=39/70 Signal level=-71 dBm
Encryption key:on
ESSID:"LangaraSecure"
Bit Rates:2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s; 11 Mb/s
12 Mb/s; 18 Mb/s; 24 Mb/s
Bit Rates:36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=efeeef1c5fdea26f
Extra: Last beacon: 3183ms ago
IE: Unknown: 000D4C616E67617261536563757265
IE: Unknown: 0108040B0C1296182430
IE: Unknown: 030106
IE: Unknown: 2A0100
IE: Unknown: 320348606C
IE: Unknown: 2D1A4C101BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1606001B00000000000000000000000000000000000000
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1x
IE: Unknown: DD180050F2020101030003A4000027A4000042435E0062322F00
IE: Unknown: DD1D000CE600049B0000000106000CE60690D10404010000000504008C0000
Hope this is enough, if it's not just tell me what more you need =)
Last edited by Can0n (2010-01-11 19:56:56)

tavianator wrote:
This works for me here at UW:
Manually in /etc/wpa_supplicant.conf:
network={
ssid="<network>"
key_mgmt=WPA-EAP
identity="<username>"
password="<password>"
Using netcfg (which I recommend strongly): do the above and set WPA_CONF to /etc/wpa_supplicant.conf (or whatever you want).
Using netcfg from testing (which you'll have to upgrade to eventually):
CONFIGSECTION='ssid="<network>"
key_mgmt=WPA-EAP
identity="<username>"
password="<password>"'
That did it
I added an own profile in /etc/network.d that I just connect to now. Excited too see if it works back home as well, got some strange error yesterday when I use WEP.
Thanks !

Intel4965 | Association/DHCP | Status Issue

I can't reliably connect to any network. I have tried just iwconfig, wpa_supplicant, and netcfg with archassistant, and I can't figure out what the problem is.
Generally, to connect I have to run these commands, and this will "usually", but NOT always get me connected to a WEP network.
iwconfig wlan0 essid APNAME
iwconfig wlan0 key 1234567890
dhcpcd wlan0 <times out everytime>
iwlist wlan0 scan <always shows results, although for 2 kernel revisions it didn't>
rm /var/run/dhcpcd-wlan0.pid
dhcpcd wlan0<finally works>
Information/things I have tried.
The 4965 module is in my modules array.
ifconfig wlan0 up
doesn't help.
Putting 'wlan0' in the interfaces array in rc.conf doesn't help.
I was able to connect with wpa_supplicant a few minutes ago. I still had to do that dhcpcd and iwlist stuff, but it worked.
Then I put
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
in my rc.local(command I used to get it working the first time, except the -B) and restarted. Starting up wpa_gui showed that I was associated, but I could not get an IP address. I disconnected, reconnected, did the dhcpcd stuff, and nothing
Netcfg also didn't work. On launching archassistant, and then trying to connect to one of the profiles I set up through archassistant, I get this;
wireless device set in config :
wireless device used : wlan0
profile started : npnwap 1
error issuing netcfg command.
Double clicking the archassistant icon in the tray, or trying to scan in archassistant, I get this error;
error ifconfigUpProcess
Dmesg;
[zack@boxxy ~]$ dmesg | grep 4965
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23k
iwl4965: Copyright(c) 2003-2007 Intel Corporation
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
I appreciate any suggestions.
Zack
Last edited by Sjoden (2008-07-07 21:03:21)

Sorry I didn't post last night, we went to my sister in laws house.
I started up my laptop at work today. Wicd took two tries to connect to my works WAP(s, we have 3 of them, all the same name, for roaming). I do a 'pacman -Syu'. It runs smoothly, only warning I get is about a font-config change. I only have 1 extra font pkg installed so I didn't worry about it.
I reboot, and wicd fails. I can associate, but I can't get an IP address. I try all 3 WAPs, none work. I try different things for about 30 minutes, rebooting, retyping key, restarting the service and the tray.py for wicd, nothing.
Plug in my network cable, Add the testing repo, re sync, and 'pacman -S testing/netcfg'. All runs fine. I make a profile from the default wep.example;
[zack@boxxy ~]$ cat /etc/network.d/???wap
CONNECTION="wireless"
DESCRIPTION="???'s external wireless network."
INTERFACE=wlan0
SCAN="yes"
SECURITY="wep"
ESSID="???WAP"
KEY="1234567890"
IP="dhcp"
I run 'netcfg2 ???wap'. It fails. I run it again, it finishes. I unplug the networking cable. No go. I remove the pid for dhcpcd on eth0, nothing. I kill dhcpcd and dhclient. Retry, nothing. I reboot, retry netcfg2, nothing again. I'm about to try and figure out how to use the quirks.
From /var/log/messages.log;
Jul 7 15:12:16 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:12:16 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:12:16 boxxy dhclient: All rights reserved.
Jul 7 15:12:16 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:12:16 boxxy dhclient:
Jul 7 15:12:17 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:12:17 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:12:17 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:12:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:12:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:12:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jul 7 15:12:51 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Jul 7 15:13:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul 7 15:13:12 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:13:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul 7 15:13:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:13:48 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:13:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:13:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:13:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:14:26 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:14:26 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:14:29 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:14:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:14:29 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 3963
Jul 7 15:14:29 boxxy dhclient: removed stale PID file
Jul 7 15:14:29 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:14:29 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:14:29 boxxy dhclient: All rights reserved.
Jul 7 15:14:29 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:14:29 boxxy dhclient:
Jul 7 15:14:30 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:14:30 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:14:30 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:14:31 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:14:39 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:14:55 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:15:02 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:15:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:15:25 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jul 7 15:15:44 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul 7 15:15:56 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:15:56 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:15:59 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:16:02 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:17:31 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:17:31 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:17:33 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:17:33 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:17:33 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 5007
Jul 7 15:17:33 boxxy dhclient: removed stale PID file
Jul 7 15:17:33 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:17:33 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:17:33 boxxy dhclient: All rights reserved.
Jul 7 15:17:33 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:17:33 boxxy dhclient:
Jul 7 15:17:34 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:17:34 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:17:34 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:17:35 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:17:40 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:17:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 7 15:17:52 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:18:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jul 7 15:18:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jul 7 15:18:30 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:18:48 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:18:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:18:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:18:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:21:39 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:21:40 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:21:59 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:21:59 boxxy r8169: eth0: link down
Jul 7 15:21:59 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:22:01 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:22:01 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:22:02 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 6427
Jul 7 15:22:02 boxxy dhclient: removed stale PID file
Jul 7 15:22:02 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:22:02 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:22:02 boxxy dhclient: All rights reserved.
Jul 7 15:22:02 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:22:02 boxxy dhclient:
Jul 7 15:22:03 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:22:03 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:22:03 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:22:04 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:22:12 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:22:31 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul 7 15:22:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:22:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul 7 15:23:09 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:23:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 7 15:23:32 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:23:32 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:23:35 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:23:38 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:24:58 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:24:58 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:25:00 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:25:00 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:25:01 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 8688
Jul 7 15:25:01 boxxy dhclient: removed stale PID file
Jul 7 15:25:01 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:25:01 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:25:01 boxxy dhclient: All rights reserved.
Jul 7 15:25:01 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:25:01 boxxy dhclient:
Jul 7 15:25:02 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:25:02 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:25:02 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:25:03 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:25:11 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:25:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul 7 15:25:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:25:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:25:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:25:54 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:26:01 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:26:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:26:21 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:26:21 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:26:24 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:26:27 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:29:35 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:29:35 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:29:37 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:29:37 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:29:38 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 9688
Jul 7 15:29:38 boxxy dhclient: removed stale PID file
Jul 7 15:29:38 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:29:38 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:29:38 boxxy dhclient: All rights reserved.
Jul 7 15:29:38 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:29:38 boxxy dhclient:
Jul 7 15:29:39 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:29:39 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:29:39 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:29:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:29:49 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:30:03 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:30:10 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:30:28 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:30:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:30:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul 7 15:31:04 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:31:04 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:31:07 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:31:10 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:31:55 boxxy r8169: eth0: link up
Jul 7 15:31:56 boxxy r8169: eth0: link down
Jul 7 15:31:57 boxxy r8169: eth0: link up
Jul 7 15:32:00 boxxy r8169: eth0: link down
Jul 7 15:32:02 boxxy r8169: eth0: link up
Jul 7 15:32:32 boxxy NET: Registered protocol family 10
Jul 7 15:32:32 boxxy lo: Disabled Privacy Extensions
Jul 7 15:32:38 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: dhcpcd 3.2.1 starting
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: hardware address = 00:13:a9:f1:a0:b7
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: broadcasting for a lease
Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: offered 10.0.1.106 from 10.0.1.200
Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: checking 10.0.1.106 is available on attached networks
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: leased 10.0.1.106 for 86400 seconds
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding IP address 10.0.1.106/16
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding default route via 10.0.1.1 metric 0
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding route to 169.254.0.0/16 metric 0
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: exiting
Jul 7 15:54:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:54:29 boxxy ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 7 15:55:39 boxxy ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:42 boxxy dhclient: DHCPOFFER from 10.0.1.200
Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:55:42 boxxy dhclient: DHCPACK from 10.0.1.200
Jul 7 15:55:42 boxxy dhclient: bound to 10.0.1.106 -- renewal in 32528 seconds.
Jul 7 15:55:43 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:45 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:48 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:50 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:53 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul 7 15:55:59 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
Jul 7 15:56:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:56:00 boxxy r8169: eth0: link down
Jul 7 15:56:06 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 13
Jul 7 15:56:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
Jul 7 15:56:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul 7 15:56:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul 7 15:56:29 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul 7 15:56:39 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:56:44 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:56:44 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:56:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:57:01 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:57:01 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: received SIGTERM, stopping
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing default route via 10.0.1.1 metric 0
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing route to 169.254.0.0/16 metric 0
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing IP address 10.0.1.106/16
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: exiting
Jul 7 15:57:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul 7 15:57:20 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:23 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:24 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:25 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
Jul 7 15:57:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:30 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:40 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 21
Jul 7 15:57:41 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:57:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:45 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:48 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 7 15:57:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:57:53 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 16
Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Jul 7 15:58:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:58:17 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
Jul 7 15:58:20 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:20 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:58:22 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Jul 7 15:58:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:34 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Jul 7 15:58:36 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:36 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:58:39 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:58:42 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:58:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
Jul 7 15:58:43 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:43 boxxy dhclient: Trying recorded lease 10.0.1.106
Jul 7 15:58:46 boxxy dhclient: No working leases in persistent database - sleeping.
[root@boxxy examples]#
From /var/log/pacman.log;
[2008-07-07 13:25] synchronizing package lists
[2008-07-07 13:26] starting full system upgrade
[2008-07-07 14:42] upgraded freetype2 (2.3.6-1 -> 2.3.7-1)
[2008-07-07 14:42] Symlinking new configuration files... done.
[2008-07-07 14:42]
[2008-07-07 14:42] ===> Important Fontconfig configuration change <===
[2008-07-07 14:42]
[2008-07-07 14:42] The way fontconfig is configured has been changed.
[2008-07-07 14:42] Configuration is done via /etc/fonts/conf.avail and conf.d.
[2008-07-07 14:42] Read /etc/fonts/conf.avail/README for more information.
[2008-07-07 14:42]
[2008-07-07 14:42] Configuration via /etc/fonts/local.conf is still possible,
[2008-07-07 14:42] but is no longer recommended for options available in conf.avail.
[2008-07-07 14:42]
[2008-07-07 14:42] Adding missing configuration files... done.
[2008-07-07 14:42] Removing outdated configuration files... done.
[2008-07-07 14:43] updating font cache... done.
[2008-07-07 14:43] upgraded fontconfig (2.5.0-1 -> 2.6.0-2)
[2008-07-07 14:43] upgraded gcc-libs (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded gcc (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded glibmm (2.16.2-1 -> 2.16.4-1)
[2008-07-07 14:43] >>> Updating module dependencies. Please wait ...
[2008-07-07 14:43] >>> MKINITCPIO SETUP
[2008-07-07 14:43] >>> ----------------
[2008-07-07 14:43] >>> If you use LVM2, Encrypted root or software RAID,
[2008-07-07 14:43] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2008-07-07 14:43] >>> More information about mkinitcpio setup can be found here:
[2008-07-07 14:43] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2008-07-07 14:43]
[2008-07-07 14:43] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2008-07-07 14:43] ==> Building image "default"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [autodetect]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:43] :: Parsing hook [keymap]
[2008-07-07 14:43] :: Parsing hook [filesystems]
[2008-07-07 14:43] :: Generating module dependencies
[2008-07-07 14:43] :: Generating image '/boot/kernel26.img'...SUCCESS
[2008-07-07 14:43] ==> SUCCESS
[2008-07-07 14:43] ==> Building image "fallback"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:44] :: Parsing hook [keymap]
[2008-07-07 14:44] :: Parsing hook [filesystems]
[2008-07-07 14:44] :: Generating module dependencies
[2008-07-07 14:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2008-07-07 14:44] ==> SUCCESS
[2008-07-07 14:44] upgraded kernel26 (2.6.25.6-1 -> 2.6.25.10-1)
[2008-07-07 14:44] upgraded lame (3.97-1 -> 3.98-1)
[2008-07-07 14:44] upgraded libpng (1.2.28-1 -> 1.2.29-1)
[2008-07-07 14:44] upgraded libsm (1.0.3-1 -> 1.1.0-1)
[2008-07-07 14:44] upgraded libxfont (1.3.2-1 -> 1.3.3-1)
[2008-07-07 14:44] upgraded libxft (2.1.12-1 -> 2.1.13-1)
[2008-07-07 14:44] upgraded libxp (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded randrproto (1.2.1-1 -> 1.2.2-1)
[2008-07-07 14:44] upgraded libxrandr (1.2.2-1 -> 1.2.3-1)
[2008-07-07 14:44] upgraded libxtrap (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded libxxf86vm (1.0.1-1 -> 1.0.2-1)
[2008-07-07 14:44] upgraded nss (3.12rc4-1 -> 3.12-1)
[2008-07-07 14:44] upgraded xf86-input-mouse (1.2.3-1 -> 1.3.0-1)
[2008-07-07 14:44] upgraded xorg-xauth (1.0.2-1 -> 1.0.3-1)
[2008-07-07 14:44] upgraded xorg-xkb-utils (1.0.2-2 -> 7.3-1)
[2008-07-07 14:44] upgraded xtrans (1.2-1 -> 1.2.1-1)
[2008-07-07 15:33] synchronizing package lists
[2008-07-07 15:33] starting full system upgrade
[2008-07-07 15:34] upgraded pcre (7.7-1 -> 7.7-2)
[2008-07-07 15:35] synchronizing package lists
[2008-07-07 15:47] installed netcfg (2.1.0_B2-1)
This is rediculous.
Zack
/edit
I was able to load the google homepage after adding the preessid quirk, and using the 'netcfg' command instead of 'netcfg2'. I restarted, and it doesn't work(I'm pretty sure my eth cable was unplugged when loaded, could be wrong);
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Wireless association failed. [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# killall wicd
wicd: no process killed
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon [DONE]
[root@boxxy zack]# killall dhcpcd
dhcpcd: no process killed
[root@boxxy zack]# killall dhclient
dhclient: no process killed
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# nano /etc/network.d/npnwap
[root@boxxy zack]# netcfg npnwap
:: npnwap up [DONE]
[root@boxxy zack]# nano /etc/network.d/npnwap
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon [DONE]
[root@boxxy zack]# netcfg npnwap
> npnwap already connected
[root@boxxy zack]#
Last edited by Sjoden (2008-07-07 21:36:17)

Wpa_supplicant and netcfg

Similar Messages

Maybe you are looking for