On Fri, 12 Jun 2009, kitepilot@kitepilot.com wrote:

>>> That's "essid", not "eesid"
> Yep...
> I screwed up.
> Imagine that...   :)

I think that was my typo, not yours. In either event the return is:

unknown command "linksys"

> dhclient eth1
> won't work because you haven't associated with anything yet, that's
> analogous to having no wired plugged in to an Ethernet.
> No "link"...

Yeah, I figured that. I tried out of curiosity.

> Try again with "essid" and run iwconfig alone to verify that you are
> associated.
> Again, no point to dhclient if you are not associated.
> Once associated, if dhclient grabs an IP address, your issue most likely
> lies on the GUI configuring the wireless wrong.
> What are you running?
> I forgot if you mentioned it...

wicd

> If it doesn't grab an IP, most likely you have a miss-configured router.
> That's assuming that you are not WEP(ing), which I didn't check for in your
> previous messages.  If you are, just turn it off until you sort this one
> out.

WPA(ing) not WEP(ing). When I first tried setting up wireless I could 
connect with encryption disabled, not enabled. This is no longer true. 
Can't connect either way.

One more thing that has changed from my earlier attempts is that before 
the connection would authenticate O.K. and hang getting the IP address. 
Now hangs trying to authenticate.



-- 
Bob Holtzman
AF9D 8760 0CFA F95A 6C77  E125 BF90 580F 8D54 9279
"If you think you're getting free lunch,
  check the price of the beer"
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss