unable to join wep network manually...

mia_tech · 08-28-2010, 09:26 PM

I'm trying to join a wireles lab that I've setup with WEP encryption, but I'm unable to join. (I've tried on two different distros: ubuntu, and backtrack) same result.

here are the commands:

Code:

ifconfig wlan0 down
iwconfig wlan0 mode managed
iwconfig wlan0 essid MYNET
iwconfig wlan0 key XXXXXXXX
iwconfig wlan0 channel 3
dhclient wlan0

tries to contact dhcp but none responde to request, and when I do iwconfig, it shows as not associated

any help appreciated

thanks

quanta · 08-29-2010, 11:36 AM

Try "iwconfig wlan0 key restricted XXXXXXXX" and bring up wlan0 again.

mia_tech · 08-29-2010, 01:55 PM

Quote:

Originally Posted by quanta

Try "iwconfig wlan0 key restricted XXXXXXXX" and bring up wlan0 again.

same result... it tries to contact dhcp but is unsuccessful. And iwconfig shows "Not-Associated." What am I missing here?

crosstalk · 08-29-2010, 02:54 PM

I'm not familiar enough with networking to answer your questions, but here's what I use for iwconfig (the unusual options are to combat wireless interference (darn 108Mbps networks... they zap everything in the 2.4Ghz band.))

I use Gentoo, and this script was added at the top of the service for net.eth1 (the return code is checked by the other script). It's on a static IP, but I currently need dhcpcd to get everything else.

Code:

#!/bin/bash

#Just make sure localhost works
ifconfig lo up

#Set the wifi for our network. Force the settings.
iwconfig eth1 channel 5
(iwlist scan 2>/dev/null) | grep -o <our essid> &>/dev/null
if [ $? -eq 0 ]
then
	iwconfig eth1 essid <our essid> mode Managed channel 5 ap 00:0F:B5:E2:DA:A2 txpower 100mW sens 1 rts 256 frag 256 key <our wep key> power all
	ifconfig eth1 192.168.1.12
	dhcpcd -q -X 192.168.1.12 eth1 &>/dev/null
	echo > /etc/homewifi
	exit 0
fi

rm -f /etc/homewifi
exit 1

Although I don't think it will, I hope this helps.

quanta · 08-29-2010, 09:25 PM

Please give us the output of 'iwlist wlan0 scan' and 'dhclient wlan0'. As a temporary solutions, I suggest you use wicd instead of manually configure from command line, and troubleshoot this problem later.

mia_tech · 08-31-2010, 11:43 AM

Thanks, I installed wicd, and it worked!