Re: Thank you for your attention and I just want to sniff the mangement and control frames
Joerg Mayer <[email protected]>
| Newsgroups | gmane.network.ethereal.user |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Jun 09, 2006 at 10:08:01PM +0800, ???? wrote:
> Thank you for your patient guidance.I followed you and
> executed the same command.But it seems there is something wrong when
> I execute the command
> " iwconfig eth1 channel 1" .
Regarding the results of iwlist, it should be iwconfig eth1 channel 11,
but it doesn't matter, because changing the channel doesn't work.
> <BODY><PRE>[root@MIPV6 ~]# uname -a
> Linux MIPV6 2.6.15 #1 Sat May 20 13:39:07 CST 2006 i686 i686 i386 GNU/Linux
> [root@MIPV6 ~]# lsb_release -a
> LSB Version: 1.3
> Distributor ID: FedoraCore
> Description: Fedora Core release 4 (Stentz)
> Release: 4
> Codename: Stentz
> [root@MIPV6 ~]# modinfo ipw2100
> filename: /lib/modules/2.6.15/kernel/drivers/net/wireless/ipw2100.ko
> description: Intel(R) PRO/Wireless 2100 Network Driver
> version: 1.2.0
...
> parm: mode:network mode (0=BSS,1=IBSS,2=Monitor)
> parm: channel:channel
...
OK, you are running a fairly current version of the driver and monitor
mode has been compiled in.
> [root@MIPV6 ~]# iwconfig
...
> Warning: Driver for device eth1 has been compiled with version 19
> of Wireless Extension, while this program supports up to version 17.
> Some things may be broken...
I currently have a problem to judge whether this might be the reason for
the problems you are seeing.
> eth1 IEEE 802.11b ESSID:"netgear2" Nickname:"ipw2100"
> Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:93:4F:C1
> Bit Rate=11 Mb/s Tx-Power:16 dBm
> Retry min limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=100/100 Signal level=-56 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:101 Missed beacon:0
>
> [root@MIPV6 ~]# iwlist eth1 scan
> Warning: Driver for device eth1 has been compiled with version 19
> of Wireless Extension, while this program supports up to version 17.
> Some things may be broken...
>
> eth1 Scan completed :
> Cell 01 - Address: 00:0F:B5:93:4F:C1
> ESSID:"netgear2"
> Protocol:IEEE 802.11bg
> Mode:Master
> Channel:11
There is an AP on channel 11
> Encryption key:off
> Bit Rate:54 Mb/s
> Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
> Quality:70 Signal level:0 Noise level:0
> Extra: Last beacon: 5396ms ago
>
> [root@MIPV6 ~]# iwconfig eth1 mode monitor
Can you please verify with iwconfig, that eth1 is now in monitor mode?
> [root@MIPV6 ~]# iwconfig eth1 channel 1
> Error for wireless request "Set Frequency" (8B04) :
> SET failed on device eth1 ; Operation not supported.
Now I'm very confused: This should have "just worked".
> [root@MIPV6 ~]# tethereal -i eth1
> Warning: Couldn't obtain netmask info (eth1: no IPv4 address assigned).
> Capturing on eth1
> 0.000000 Netgear_93:4f:c1 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32768/00:0f:b5:93:4f:c1 Cost = 0 Port = 0x8002
...
And that's how it looks when you only capture ethernet frames, not
802.11 frames on the wireless interface.
I currently don't have an idea why "iwconfig eth1 channel 11" (or 1)
fails. Can you please verify that setting monitor mode worked and have a
look at the output of dmesg, whether there are any suspicious messages
when you change the mode.
Ciao
Joerg
--
Joerg Mayer <[email protected]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.