I changed my internet service to Verizon Fios and they require their own OEM wireless router.
At first I tried to switch off its wireless and have my trusty Linksys WRT54G with the hyperWRT
flashed firmware get an IP address from the Linksys router and serve as the wireless connection
for my house. I was unable to get the Verizon and Linksys routers to cooperate.
The weird thing is that my linux box can connect to the Verizon router when WEP is off but not
when it is on (currently I only have a 64bit hex password). I've re-checked the password and
also entered the hex key in the plaintext format s: to no avail.
Here is the shell script I use for testing purposes. It lets me bring down the device and bring it
up with altered settings.
ifconfig wlan0 down
modprobe -r ndiswrapper
sleep 2
modprobe ndiswrapper
sleep 2
ifconfig wlan0 up
#ifconfig wlan0 up 192.168.1.99
sleep 2
#iwconfig wlan0 mode Managed essid "EGDT0" nick "desktop" channel 11 rate auto key 1F9014E95E
iwconfig wlan0 mode Managed essid "EGDT0" nick "desktop" channel 11 rate auto
sleep 2
dhcpcd wlan0
#route add default gw 192.168.1.1
The commented out lines are what doesn't work. I can't get a wep connection and I will eventually set up a
static address because it is supposedly less trouble to connect than when having to negotiate dhcp.
It doesn't recognize the iwconfig nickname because my connection on the router shows up like this:
Host: new-host
IP Address: 192.168.1.4
Subnet Mask: 255.255.255.0
MAC Address: 00:0c:41:6c:3e:09
Network Connection: Bridge
Lease Type: Dynamic
Port Forwarding Services: None
Windows Shared Folders: \\192.168.1.4\
I should add that my wife's Windows XP laptop connects flawlessly with WEP and my work assigned Windows XP
laptop has to try three times before it can successfully connect with WEP. I've tried the three times trick with linux
without success.
Any ideas? I used to have the tcpdump utility in VL3 but I don't see it in VL5.9. is it somewhere in the downloads
but I am not finding it?
Oops!. In my haste to post my problem I didn't search the forum properly for WEP connections problems. I found the answer
in a posting in the networking forum (which is where this belongs).
iwconfig key open XXXXXXXX fixed the connection problem for VL5.9. It seems routers have different preferences for
how the wep key is transmitted. When I used iwconfig key restricted XXXXXX it was unable to connect. Users will have to
try both and see which works.
I don't know about my windowsXP laptop connection problem but I mostly use my VL5.9 desktop at home anyway.