[Prism54-devel] [Bug 50] iwconfig eth0 channel x in monitor mode gives errors

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=50





------- Additional Comments From spamhole@gmx.at  2004-01-30 11:13 -------
What I've found out so far:


- there _is no_ automatic channel hopping in monitor mode (see bug #47). And
thats a good thing(tm), because it allows you to monitor one specific channel.

To verify this you can try:

set your AP to channel 11.

iwconfig eth0 mode managed
iwconfig eth0 channel 1
iwconfig eth0 mode monitor
tcpdump -i eth0

(you will see no beacons because there is no automatic channel hopping)

... do the same with your card being configured for channel 11 and you will see
beacons.


- there _is_ automatic channel hopping in _managed_ mode as long as you are not
connected to an AP.

To verify this:

make sure you aren't connected to an AP.
type iwconfig eth0 a few times and you'll see another channel each time.


- in monitor mode its not possible to set another channel with iwconfig, but the
latest kismet-cvs (with a prism54g source and channelhopping=true) can change
channels. So it seems that the firmware does support channel changes in monitor
mode (because kismet can do it too). But I dont know why it doesn't work with
iwconfig.

To verify this you can do the same as above, type iwconfig eth0 a few times
while kismet-cvs is running. Now you see the channels changing even in monitor mode.

I wonder what iwconfig eth0 channel x is doing differently then kismet...




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.