You are not logged in.
Pages: 1
Hello I tried to connect to the WEP Acess point of the flat where I just arrived.
I typed :
iwconfig eth1 mode managed channel 11 key s:42 essid "Network - name"
or
iwconfig eth1 mode managed channel 11 key 42 essid "Network - name"
With the 10 digit key they give me instead of "42" and the true network name which contain " " and "-".
I ran dhclient eth1 and dhcpcd eth1 but they both failed.
Did I forget anything?
Offline
run iwconfig to see available wireless devices. eth0/1 is probably not one of them.
oh, and ommiting your essid does nothing
even the default wireless tools "iwlist device_name scan" command can see access points that aren't broadcasting.
e: last time I checked iwconfig still didn't support the passcode for wep. that's not the case with wpa, though.
Last edited by verve (2008-09-18 13:22:18)
Offline
I'm pretty sure that I use WEP at home (I have a Linksys 802.11b wireless router) and my commands looks like this:
# ifconfig wlan0 up
# iwconfig wlan0 essid Screwball key XXXXXXXXXX
# dhcpcd wlan0
Last edited by Cosay (2008-09-18 16:30:46)
Offline
Yes it the right interface here is what iwconfig answer me :
eth1 unassociated ESSID:"xxx - xxxx"
Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:xxx-xxxx-xxxx Security mode:open
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Offline
If you run:
iwlist eth1 scan
what happens?
Other questions, that might be relevent: what chipset is your card using? have you succesfully connect to ANY network before? How about any WEP - key protected network?
last time I checked iwconfig still didn't support the passcode for wep. that's not the case with wpa, though.
I think it's the other way around, WEP you can do with iwconfig, for WPA you need to use iwpriv, wpa_supplicant (or a frontend thereof) or network manager.
Offline
^ iwconfig supports both wpa and wep. but the passcode (iwconfig s: passcode) doesn't work for wep. he's got to use a regular key instead, without the s: prefix.
Last edited by verve (2008-09-19 05:22:41)
Offline
Verve's comment sounds right to me, based on what I have read on the Arch Wiki.
Offline
iwconfig <interface> key s:ASCII_KEY
Should work for an ASCII key. Omit s: for hex.
Offline
I don't know if it's an ascii key or not.
But the weird things is that it works when I use wifi-radar.
And the main difference I think is that eth1 is not "unassociated".
Offline
^ iwconfig supports both wpa and wep. but the passcode (iwconfig s: passcode) doesn't work for wep. he's got to use a regular key instead, without the s: prefix.
No, iwconfig is only for WEP.
iwpriv is only for WPA on crap Ralink drivers. WPA on everything else is wpa_supplicant (network-manager and netcfg are just "fronts" to wpa_supplicant)
I don't know if it's an ascii key or not.
Try both ways and see if it works? Hex key will only contain numbers 0-9 and the letters a-f. It's probably a hex key.
Wireless devices need to "associate" to a wireless network first. Think of it as like plugging in a wired cable into a network card -- you have to do it first otherwise you simply won't be connected.
"unassociated" means that you either havn't finished configuring it to connect, or you have misconfigured it (eg, incorrect key or incorrectly set key).
Offline
Pages: 1