| 1 |
On Thursday 31 May 2007 12:05, Randy Barlow wrote: |
| 2 |
> Howdy all! I'm having a tough time getting DHCP to work on my wireless |
| 3 |
> card. It's the intel 2200, and I am using wpa_supplicant with it. The |
| 4 |
> contents of my /etc/conf.d/net are: |
| 5 |
|
| 6 |
I've filed a bug report about this problem with a few more details at |
| 7 |
http://bugs.gentoo.org/show_bug.cgi?id=180487 I'll repeat the text I posted |
| 8 |
there here so if anyone can help I would be very grateful! |
| 9 |
|
| 10 |
I am using the intel 2200 wireless card with the in-kernel driver and the |
| 11 |
firmware from portage, as well as wpa_supplicant. When I run the init script |
| 12 |
to start the network interface, it reports normally: |
| 13 |
|
| 14 |
lappy786 ~ # /etc/init.d/net.eth1 start |
| 15 |
* Starting eth1 |
| 16 |
* Starting wpa_supplicant on eth1 ... [ok] |
| 17 |
* Starting wpa_cli on eth1 ... [ok] |
| 18 |
* Backgrounding ... |
| 19 |
|
| 20 |
However, it seems to get stuck somewhere in the backgrounded stage because the |
| 21 |
interface doesn't come up and I don't get an IP address. |
| 22 |
|
| 23 |
lappy786 ~ # /etc/init.d/net.eth1 status |
| 24 |
* status: inactive |
| 25 |
lappy786 ~ # /etc/init.d/net.eth1 start |
| 26 |
* WARNING: net.eth1 has already been started. |
| 27 |
lappy786 ~ # ifconfig |
| 28 |
eth1 Link encap:Ethernet HWaddr 00:0E:35:13:2B:A0 |
| 29 |
inet6 addr: fe80::20e:35ff:fe13:2ba0/64 Scope:Link |
| 30 |
UP BROADCAST MULTICAST MTU:1500 Metric:1 |
| 31 |
RX packets:4 errors:1188 dropped:1488 overruns:0 frame:0 |
| 32 |
TX packets:3 errors:0 dropped:0 overruns:0 carrier:8 |
| 33 |
collisions:0 txqueuelen:1000 |
| 34 |
RX bytes:10960814 (10.4 Mb) TX bytes:393094968 (374.8 Mb) |
| 35 |
Interrupt:11 Base address:0x6000 Memory:cffff000-cfffffff |
| 36 |
|
| 37 |
Strangely, it seems to aquire an ipv6 address. /var/log/messages just |
| 38 |
contains: |
| 39 |
|
| 40 |
May 31 15:37:27 lappy786 ADDRCONF(NETDEV_UP): eth1: link is not ready |
| 41 |
May 31 15:37:28 lappy786 ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready |
| 42 |
May 31 15:37:38 lappy786 eth1: no IPv6 routers present |
| 43 |
|
| 44 |
It does correctly associate with my AP, and I can manually run dhcpcd eth1 to |
| 45 |
get an IP address and use the network (how I am writing this bug report!) |
| 46 |
However, other services (such as sshd) that depend on the network will not |
| 47 |
start since the init script doesn't think it finished. |
| 48 |
|
| 49 |
My /etc/conf.d/net contains: |
| 50 |
|
| 51 |
modules=( "wpa_supplicant" ) |
| 52 |
wpa_supplicant_eth1="-Dwext" |
| 53 |
|
| 54 |
And my /etc/wpa_supplicant/wpa_supplicant.conf contains: |
| 55 |
|
| 56 |
ctrl_interface=/var/run/wpa_supplicant |
| 57 |
ctrl_interface_group=wheel |
| 58 |
|
| 59 |
ap_scan=1 |
| 60 |
|
| 61 |
network={ |
| 62 |
ssid="youThink" |
| 63 |
psk="wouldntYouLikeToKnow" |
| 64 |
priority=5 |
| 65 |
} |
| 66 |
|
| 67 |
network={ |
| 68 |
ssid="ncsu" |
| 69 |
key_mgmt=NONE |
| 70 |
} |
| 71 |
|
| 72 |
I am using baselayout version 1.12.9-r2 and wpa_supplicant version 0.5.7. I |
| 73 |
have found a lot of bug reports similar to this, but they are all for |
| 74 |
different |
| 75 |
versions of baselayout or wpa_supplicant, and the fixes specified by them |
| 76 |
haven't seemed to work. I do apologize if this turns out to be a duplicate, |
| 77 |
but I promise that I spent a fair amount of time reading the related reports |
| 78 |
and trying things! Let me know if there is any additional information I can |
| 79 |
offer! |
| 80 |
|
| 81 |
Reproducible: Always |
| 82 |
|
| 83 |
-- |
| 84 |
Randy Barlow |
| 85 |
http://www.electronsweatshop.com |
| 86 |
"Oh me of little faith..." |
| 87 |
-- |
| 88 |
gentoo-user@g.o mailing list |
Archives