Bugzilla – Bug 271
under ad-hoc mode,can still communicate after setting essid to another value
Last modified: 2005-10-02 14:39:11
You need to log in before you can comment on or make changes to this bug.
We did this testing on ibm t40 and compaq x1000,both of which have FC2,2.6.8.1 kernel. steps: 1, On ibm t40: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid testing channel 2 % ifconfig eth1 192.168.2.20 up 2, On compaq x1000: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid testing channel 2 % ifconfig eth1 192.168.2.21 up % ping 192.168.2.20 we can see ping comes back with data. 3, then on compaq x1000, we change the essid: % iwconfig eth1 essid testing2 % iwconfig we can see that the essid has been changed. % ping 192.168.2.20 the x1000 can still communicate with t40.
Note from scrub: Please provide dmesg output at 0x3fff capturing the command that sets the ESSID to the new essid.
Created an attachment (id=98) [details] sometimes the two laptops can't communicate with each other. test it again in 0.13, but chances are good that after the association is established and the static IP is assigned, the two laptop can't communicate with each other. the PING gives message: Destination Host Unreachable. attached is the dmesg output when debug is set to 0x3fff.
Yan, was the above comment for the dell adhoc bug? Our bug is actually with pattern matching essid's. "testing" and "testing2" are incorrectly seen as the same essid, so you end up joining the old ad-hoc network, and hence can ping the machines in the original network.
No, the comment is for this bug. Following Salwan's advice above, we set the debug to 0x3fff and got the attached dmesg output. this time, we didn't set channel on the second laptop to avoid creating two ad- hoc networks: 1, On Compaq X1000: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc % iwconfig eth1 essid hello channel 2 % ifconfig eth1 192.168.2.20 up 2, On Dell D505: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc % iwconfig eth1 essid testing % ifconfig eth1 192.168.2.21 up % ping 192.168.2.20 we can see ping comes back with data. 3, then on Dell D505, we change the essid: % iwconfig eth1 essid hello2 % iwconfig we can see that the essid has been changed. % ping 192.168.2.21 the x1000 can still communicate with D505. so, as you said above, this problem still exists in 0.13.
sorry, i made a typing mistake. s/testing/hello so the 2nd step should be: 2, On Dell D505: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc % iwconfig eth1 essid hello % ifconfig eth1 192.168.2.21 up % ping 192.168.2.20
Fixed in v0.14
can't verify the fix now,will verify this when bug 413 is fixed.
To this bug, after setting essid to different value, the two laptops can not communicate. Mark this bug as fixed. To bug #413, maybe it doesn't happen everytime, I didn't see it during the testing.
the bug still exist in 0.15. steps: 1, On ibm t40: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid testing channel 2 % ifconfig eth1 192.168.2.20 up 2, On compaq x1000: % modprobe ipw2200 % iwconfig eth1 mode ad-hoc essid testing % ifconfig eth1 192.168.2.21 up % ping 192.168.2.20 we can see ping comes back with data. 3, then on compaq x1000, we change the essid: % iwconfig eth1 essid testing2 % iwconfig we can see that the essid has been changed. % ping 192.168.2.20 the x1000 can still communicate with t40.
Yan, Nan. Is the ethernet interface down? or is ethernet cable unplugged from the machine? ie. Please confirm that the pings aren't being routed through the ethernet cable.
i did this test again, our ethernet cable is unplugged from the machine,and the bug still exist in 0.15.
Fixed in version 0.16
Yan, Nan: if verification fails in 0.16, please provide debug=0x3fff debug log.
An addition to the previous comment. The debug log of interest is the one from the machine that changes its essid.
verified in 0.16.