the infamous linux wifi monster strikes-wirechief, Leonard, and marc

[Nils Kassube]

Robert Holtzman wrote:
> On Mon, 20 Apr 2009, Nils Kassube wrote:
> > Robert Holtzman wrote:
> >> Initially I tried "jUCEmss4WGhQ" for a pass phrase which didn't
> >> work. Later I tried letting the configuration utility do it
> >> automatically. Also no luck. Could this be a hardware problem?
> >> Firmware?
> >
> > Which configuration utility? I don't think there is a configuration
> > utility that can guess the pass phrase.
>
> The web configuration utility (192.168.1.1) has an option to
> automatically enable encryption, including generation of a key
> (pass phrase?). I have been told on another list that this only works
> with Windows. I won't dispute that but it does populate the router
> with the key (pass phrase?). Moot point however. I still couldn't
> connect.

Ah, _that_ configuration utility. Sorry, I didn't remember it exists 
because it is Windows only and I never even tried to use it. For me it 
is just a pretty icon on the config page :)

> >  If you can connect the router
> > to your machine using the ethernet cable, you could copy the pass
> > phrase from the router configuration to the wicd or network manager
> > configuration like this (this is from memory because I don't have
> > the laptop in front of me):
>
> The point, unless I'm mistaken, is to assure that the router and
> client machine are using the same pass phrase. 

Yes. While I supposed that you had already tried to make the pass 
phrases the same, I gave the instructions anyway just to make sure 
there was no misunderstanding.

> This is one of the 
> first things I did, although it didn't occur to me to connect with
> ethernet cable. What I did was to put the pass phrase into my
> encrypted passwords file, reset the router to be able to connect, and
> paste the p/w into wicd (the client) and also into the configuration
> utility. In any event, the pass phrases match. And.......no
> connection after reboot.

Well, using the encrypted passwords file is just another method to do 
the same thing. Therefore I would assume you did it right and you 
should be able to connect on the wireless link. Now there are 2 
remaining questions. You wrote "And.......no connection after reboot". 
Does that mean that you had a connection before reboot? And did you 
tell wicd to automatically connect to your network?

Finally, I just installed Wicd and made the connection to the WRT54GL 
with my laptop which has a 2200BG wireless card. It worked without a 
problem.

> Again, any chance this could be a hardware or firmware problem.

Yes, that is possible. But I can't tell you on which side the problem 
is.


Nils