� wrote:
Hi all!Yeah A number of things, some of which you may know: 1) Don't add net.eth1 to runlevel. The ipw3945 module loading (/etc/modprobe.conf) runs ipw3945d init script which brings up net.eth1 which is managed by wpa_supplicant. If you try and manage net.eth1 yourself (with rc-update, or with something like ifplugd then things will get confused). I do have netplug configed for eth* but I think it knows how to get out of the way of wpa_supplicant. All you need to do is emerge ipw3945 - no rc-updating needed. 2) If you ever need to restart net.eth1, restart ipw3945d instead. 3) My wpa_supplicant.conf just as comparision: # Intel PRO/Wireless 3945 :: wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant # DO NOT remove this line! ctrl_interface_group=0 # Only allow root to read config. ap_scan=1 # Allows wpa_supplicant to handle AP scanning. # The following configures wpa_supplicant for a WPA network={ ssid="foo" scan_ssid=1 # Use if SSID broadcast is disabled. psk="bar" # Your key here. } -- [EMAIL PROTECTED] mailing list |
- Re: [gentoo-user] ipw3945 and wpa_supplicant issues Will Briggs
- Re: [gentoo-user] ipw3945 and wpa_supplicant issues Brian Johnson
- Re: [gentoo-user] ipw3945 and wpa_supplicant issues Dan Farrell
- Re: [gentoo-user] ipw3945 and wpa_supplicant is... Mike Mazur
- Re: [gentoo-user] ipw3945 and wpa_supplican... Will Briggs