my router hates me

[kitepilot at kitepilot.com]

Try:
iwconfig eth1 essid lynksys
That should work... 

Then type:
iwconfig
Alone. 

You should see something like: 


root at travelair:~# iwconfig
lo        no wireless extensions. 

eth0      no wireless extensions. 

wmaster0  no wireless extensions. 

wlan0     IEEE 802.11bg  ESSID:"visionwisp11"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:19:3B:80:19:EF
          Bit Rate=11 Mb/s   Tx-Power=20 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality=53/100  Signal level:-65 dBm  Noise level=-73 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0 

pan0      no wireless extensions. 

tun0      no wireless extensions. 

root at travelair:~# 

BTW:
Be root or "sudo" 

The "Association" is:
wlan0     IEEE 802.11bg  ESSID:"visionwisp11"
ET 

PS: If everything else fails:
iwconfig --help
:) 

 

 

Robert Holtzman writes: 

> On Fri, 12 Jun 2009, kitepilot at 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 at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss