[ltp] R40 + ipw2100 + WEP 256
Claudio Ferronato
linux-thinkpad@linux-thinkpad.org
Mon, 07 Feb 2005 16:33:22 +0100
Hi
I'm an owner of a beautiful (?!?) Thinkpad R40 (2722 BDG).
The wifi device is a centrino, which uses the driver ipw2100, found on
ipw2100.sf.net . The kernel is 2.6.10 without any patch, and i compiled
the driver as external, whith CONFIG_IPW2100_LEGACY_FW_LOAD set to "Y".
The firmware is in /etc/firmware, and all is good without encryption.
But when i try to use WEP, there is no connection.
The AP is an US-Robotics, with just a key of 256 bit, and the other wifi
device (on a windows 98) works well.
This is my script to load the device:
rmmod ipw2100 arc4 ieee80211_crypt_wep ieee80211 ieee80211_crypt
/sbin/modprobe ipw2100 channel=6 mode=1
/usr/sbin/iwpriv eth1 set_power 5
/usr/sbin/iwconfig eth1 key restricted s:fa(see_something_else_ok_?)5d
ifconfig eth1 192.168.137.12 netmask 255.255.255.0 up
ping -c 1 -I eth1 192.168.137.1
Obliusvly, the key is obfuscated :)
iwconfig shows me this:
eth1 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Ad-Hoc Channel:6 Cell: 00:00:00:00:00:00
Bit Rate=0kb/s Tx-Power:off
Retry:on RTS thr:off Fragment thr:off
Encryption key:6634-BUT_-DO_Y-OU_P-ERSI-ST_?-30 Security
mode:restricted
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But when I try to ping 192.168.137.1, i have just this message:
PING 192.168.137.1 (192.168.137.1) from 192.168.137.12 eth1: 56(84)
bytes of data.
From 192.168.137.12 icmp_seq=1 Destination Host Unreachable
--- 192.168.137.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
The routing table shouldn't have mistake
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.137.0 * 255.255.255.0 U 0 0 0 eth0
192.168.137.0 * 255.255.255.0 U 0 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
default usrobotics.wifi 0.0.0.0 UG 1 0 0 eth0
The WEP key is right, and eth0 has 192.168.137.11.
Should I downsize the key to 128 or 64 bit?
Claudio Ferronato