On Wed, 2007-08-08 at 03:17 -0700, David Miller wrote:
> Then I don't understand your problem. If they are specific 802.11
> protocol packets, the radio stack is in a much better situation to
> filter out things like this.
What do you mean by radio stack? You can't really send any frames into
the monitor devices *except* raw radiotap+802.11 frames, and these are
exactly the problem because they're mirrored out right away. But because
we have a different radiotap header on outgoing than on incoming frames
to allow userspace to see the transmission indication (was the packet
ACKed by the other side etc) we ourselves mirror them out as well.
We also mirror out packets from other virtual devices associated with
the same PHY as the virtual monitor.
So think of it this way:
[ monitor interface (radiotap+802.11) ] [ STA mode interface (802.3) ]
| |
\ /
\ /
\ /
\ /
[ mac80211 ]
|
[ PHY ]
|
[ wireless medium ]
Now for packets that come in on the right path, they get mirrored out
back to the STA mode interface as well. That's fine. For packets that
come from the bottom, they get cloned and sent to both devices at the
top with different framing.
Additionally, packets that come in via any interface on the top are
redirected to all monitor interfaces *after* their transmission via the
PHY and are amended by a radiotap header that indicates whether the
transmission was successful. So if you run tcpdump on both interfaces
above you'll see the IPv4 multicast packet sent to the STA mode
interface come up on the STA mode interface right away, and you'll also
see it on the monitor interface after it was transmitted by the PHY.
The problem now comes in when you actually transmit a 802.11 framed
packet down the monitor device. Because the mac80211 code mirrors all
transmitted packets up to all monitor interfaces, and the generic code
mirrors the packet as soon as it was sent to the device (via
dev_queue_xmit_nit) you see it twice.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
