netdev - [iproute2] tc action mirred question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <210469.98452.qm@web111611.mail.gq1.yahoo.com>
Date:	Sun, 6 Sep 2009 10:13:40 -0700 (PDT)
From:	Xiaofei Wu <xiaofei_wu08@...oo.com>
To:	linux netdev <netdev@...r.kernel.org>
Cc:	hadi@...erus.ca
Subject: [iproute2] tc action mirred    question

Hi,

I have something to ask.

I construct a network like this:

/A\
B   D
\C/

All of the nodes(A, B, C, D) have two wireless cards (wlan0, wlan1).  A-B, B-C, A-D, D-C are wireless links.

Node A wnats to transmit packets with node C. Because the wireless links are not very reliable, I want to forward the same packet through A-B-C and A-D-C simultaneously. 
How to achieve my purpose？

Stephen Hemminger  said,
>Not sure what the best solution would be, but you could investigate
>using the 'tc filter mirred' action. Essentially, the traffic control
>command allows putting filters on output (or input) that can be used
>to do things like mirror packets.
>

On node A,
wlan0, IP address 192.168.1.1/24 ; wlan1, IP address 192.168.2.1/24
I use command 'tc filter add dev wlan0 ... match ip src 192.168.1.0/24 ...
action mirred egress mirror dev wlan1' to mirror packets.
When I use 'tcpdump -i wlan1', I can 'see' the packets  'A(wlan0)->B' (node B will forward them to C). How to forward the mirroring packets 'A(wlan1)' to D (then, node D forwards them to C) ?

Regards,
Wu

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html