[gentoo-user] wireless failure after madwifi-ng upgrade

[gentoo-user] wireless failure after madwifi-ng upgrade

[John Blinka]

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

Hi, all,

I have been using wireless successfully for about a month, until I
upgraded madwifi-ng last night.   Since then wireless has not
worked.   I have a netgear wireless router which supplies the
wireless signal, and the configuration of this router has not
changed.  And  wireless works fine from the same box when I
boot Windows.  So, the problem seems to be related to the
madwifi-ng upgrade.

No configuration files were changed - at least etc-update didn't
report any.

In /var/log/messages,, I find the following:

rc-scripts: WEP key is not set for "NETGEAR" - not connecting

Well... of course it isn't - my router uses WPA encryption,
and always has.  My /etc/conf.d/net and
/etc/wpa_supplicant/wpa_supplicant.conf files are straight from
the gentoo handbook:

/etc/conf.d/net:

modules=( "wpa_supplicant" )
wpa_supplicant_ath0="-Dmadwifi"
modules=( "dhcpcd" )
config_ath0=( "dhcp" )
dhcpcd_ath0="-t 10 -s 192.168.1.101"
dhcp_ath0="release nodns nontp nonis"
nis_domain_ath-=" mydomain.org"

/etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
     ssid="NETGEAR"
     psk="xxx"
     priority=5
}


So, why does the rc-script suddenly think I'm using WEP encryption
?

Thanks for any and all ideas.

John Blinka

[-- Attachment #2: Type: text/html, Size: 1923 bytes --]

Re: [gentoo-user] wireless failure after madwifi-ng upgrade

[Naga]

On Friday 01 June 2007 14:08:16 John Blinka wrote:
> Hi, all,
>
> I have been using wireless successfully for about a month, until I
> upgraded madwifi-ng last night. 
[...] 
> Thanks for any and all ideas.

reemerge wpa_supplicant

It's in that ebuild...
elog save or mail is a good thing (tm) :)

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wireless failure after madwifi-ng upgrade

[John Blinka]

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

On 6/1/07, Naga <nagatoro@gmail.com> wrote:
>
> On Friday 01 June 2007 14:08:16 John Blinka wrote:
> > Hi, all,
> >
> > I have been using wireless successfully for about a month, until I
> > upgraded madwifi-ng last night.
> [...]
> > Thanks for any and all ideas.
>
> reemerge wpa_supplicant



I did that.  It didn't help.


It's in that ebuild...
> elog save or mail is a good thing (tm) :)


Yes. it is!


John

[-- Attachment #2: Type: text/html, Size: 925 bytes --]

Re: [gentoo-user] wireless failure after madwifi-ng upgrade

[Naga]

On Friday 01 June 2007 14:08:16 John Blinka wrote:

> rc-scripts: WEP key is not set for "NETGEAR" - not connecting

Just a sugestion change the name. There might be other NETGEAR units in the 
area.

> /etc/wpa_supplicant/wpa_supplicant.conf:
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> ap_scan=1
> network={
>      ssid="NETGEAR"
>      psk="xxx"
>      priority=5
> }
> So, why does the rc-script suddenly think I'm using WEP encryption

Try and add 
proto=WPA
or do a scan and add from the gui with
update_config=1
in the config file.

else try looking in /usr/share/doc/wpa_supplicant-xxx/wpa_supplicant.conf.bz2

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wireless failure after madwifi-ng upgrade

[John Blinka]

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On 6/1/07, Naga <nagatoro@gmail.com> wrote:
>
> On Friday 01 June 2007 14:08:16 John Blinka wrote:
>
> > rc-scripts: WEP key is not set for "NETGEAR" - not connecting
>
> Just a sugestion change the name. There might be other NETGEAR units in
> the
> area.


Excellent idea.


> Try and add
> proto=WPA
> or do a scan and add from the gui with
> update_config=1
> in the config file.
>
> else try looking in
> /usr/share/doc/wpa_supplicant-xxx/wpa_supplicant.conf.bz2



Thanks for all the tips.  I just followed your original suggestion to
re-emerge
wpa_supplicant (repeating what  I did already after upgrading madwifi-ng)
and now everything works.  A mystery.

Thanks for all your help!

John

[-- Attachment #2: Type: text/html, Size: 1277 bytes --]