Bugzilla – Bug 402
can't use ad-hoc when WEP is enabled
Last modified: 2005-10-03 15:42:27
You need to log in before you can comment on or make changes to this bug.
When WEP is enabled, the two laptops can associate but can't communicate with each other. steps: 1, on laptop1: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello channel 3 key 1111 % iwconfig we can see driver is associated. % ifconfig eth1 192.168.2.20 up 2, on laptop2: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello channel 3 key 1111 % iwconfig we can see driver is associated. % ifconfig eth1 192.168.2.21 up % ping 192.168.2.20 we can see ping comes back with NO data. If we don't set channel on laptop2 to avoid creating a new ad-hoc network, then laptop2 can't associate: 1, on laptop1: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello channel 3 key 1111 % iwconfig we can see driver is associated. % ifconfig eth1 192.168.2.20 up 2, on laptop2: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello key 1111 % iwconfig we can see driver is NOT associated.
Can you provide the dmesg output from the failing laptop with debug level set to 0x10ff? Basically: % dmesg -c > /dev/null % . load debug=0x10ff mode=1 % iwconfig eth1 essid hello key 1111 % dmesg -c > output and then attach output.
Created an attachment (id=106) [details] following the steps described in James' comment,we got the dmesg output following the steps described in James' comment,we got the dmesg output on the failed-to-associate laptop.
retest this on 0.15 again, have some more comments: 1, on laptop1: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello channel 3 key 1111 % iwconfig we can see driver is associated. % ifconfig eth1 192.168.2.20 up 2, on laptop2: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid hello key 1111 % iwconfig we can see driver is unassociated. % iwlist eth1 scan we can see the cell, which essid is hello, is using no encryption key.
Created an attachment (id=126) [details] Possible fix for this bug. Can you try this patch and see if the problem goes away? Applying this patch should result in the Ad-Hoc network being created w/ privacy enabled (currently it is being created w/out privacy, so the other peer can't associate)
The patch works. Will be fixed in version 0.16
verified in 0.16.