I am using the intel 2200 wireless card with the in-kernel driver and the firmware from portage, as well as wpa_supplicant. When I run the init script to start the network interface, it reports normally: lappy786 ~ # /etc/init.d/net.eth1 start * Starting eth1 * Starting wpa_supplicant on eth1 ... [ ok ] * Starting wpa_cli on eth1 ... [ ok ] * Backgrounding ... However, it seems to get stuck somewhere in the backgrounded stage because the interface doesn't come up and I don't get an IP address. lappy786 ~ # /etc/init.d/net.eth1 status * status: inactive lappy786 ~ # /etc/init.d/net.eth1 start * WARNING: net.eth1 has already been started. lappy786 ~ # ifconfig eth1 Link encap:Ethernet HWaddr 00:0E:35:13:2B:A0 inet6 addr: fe80::20e:35ff:fe13:2ba0/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:8 collisions:0 txqueuelen:1000 RX bytes:10960814 (10.4 Mb) TX bytes:393094968 (374.8 Mb) Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff Strangely, it seems to aquire an ipv6 address. /var/log/messages just contains: May 31 15:37:27 lappy786 ADDRCONF(NETDEV_UP): eth1: link is not ready May 31 15:37:28 lappy786 ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready May 31 15:37:38 lappy786 eth1: no IPv6 routers present It does correctly associate with my AP, and I can manually run dhcpcd eth1 to get an IP address and use the network (how I am writing this bug report!) However, other services (such as sshd) that depend on the network will not start since the init script doesn't think it finished. My /etc/conf.d/net contains: modules=( "wpa_supplicant" ) wpa_supplicant_eth1="-Dwext" And my /etc/wpa_supplicant/wpa_supplicant.conf contains: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel ap_scan=1 network={ ssid="youThink" psk="wouldntYouLikeToKnow" priority=5 } network={ ssid="ncsu" key_mgmt=NONE } I am using baselayout version 1.12.9-r2 and wpa_supplicant version 0.5.7. I have found a lot of bug reports similar to this, but they are all for different versions of baselayout or wpa_supplicant, and the fixes specified by them haven't seemed to work. I do apologize if this turns out to be a duplicate, but I promise that I spent a fair amount of time reading the related reports and trying things! Let me know if there is any additional information I can offer! Reproducible: Always Steps to Reproduce: Portage 2.1.2.7 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.5-r2, 2.6.20-gentoo-r8 i686) ================================================================= System uname: 2.6.20-gentoo-r8 i686 Intel(R) Pentium(R) M processor 1.60GHz Gentoo Base System release 1.12.9 Timestamp of tree: Mon, 21 May 2007 04:20:01 +0000 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=pentium-m -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O3 -march=pentium-m -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://www.gtlib.gatech.edu/pub/gentoo ftp://mirror.iawnet.sandia.gov/pub/gentoo/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo " MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X acl acpi alsa apache2 arts audiofile bash-completion berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread eds emboss encode esd evo fam firefox fortran gdbm gif gpm gstreamer hal iconv isdnlog jpeg kde kerberos libg++ mad midi mikmod mp3 mpeg mudflap mysql ncurses nls nptl nptlonly ogg opengl openmp oss pam pcre pdf perl png pppd python qt3 qt3support qt4 quicktime readline reflection sdl session spell spl ssl svg symlink tcpd tiff truetype truetype-fonts type1-fonts unicode vorbis wifi win32codecs x86 xml xorg xscreensaver xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="i810" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
*** Bug 180489 has been marked as a duplicate of this bug. ***
Maybe you can add to your /etc/conf.d/net this line to enable dhcp on startup : config_eth1=( "dhcp" ) I think this can solve the problem...
Thanks for the suggestion, but it doesn't work unfortunately. The problem doesn't seem to be that it is not configured to use dhcp (that should be the default if you don't specify anything by my understanding) but that the init script doesn't seem to even finish. The evidence is that other init scripts that depend on the network believe it to not be activated, and that when I call its init script with status is says that it is inactive. Any other ideas?
Someone has pointed out to me that the high number of packet RX errors reported by ifconfig may indicate a driver problem. I intend to try turning off encryption to see if that eliminates these packet errors. I will post back the results!
Wow, I just realized that I never posted back the results! Well, I ended up using wireless tools instead with WEP encryption and the system works perfectly. I really want to use WPA, but it just doesn't seem to work...
If you try wpa again, post more output like wpa_cli status and we'll work from there. Until then, closing.