On Thursday 31 May 2007 12:05, Randy Barlow wrote: > Howdy all! I'm having a tough time getting DHCP to work on my wireless > card. It's the intel 2200, and I am using wpa_supplicant with it. The > contents of my /etc/conf.d/net are:
I've filed a bug report about this problem with a few more details at http://bugs.gentoo.org/show_bug.cgi?id=180487 I'll repeat the text I posted there here so if anyone can help I would be very grateful! 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 -- Randy Barlow http://www.electronsweatshop.com "Oh me of little faith..." -- [EMAIL PROTECTED] mailing list
