netdev - Re: [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-prev] [day] [month] [year] [list]

Message-Id: <1252328063.4533.12.camel@dogo.mojatatu.com>
Date:	Mon, 07 Sep 2009 08:54:23 -0400
From:	jamal <hadi@...erus.ca>
To:	Xiaofei Wu <xiaofei_wu08@...oo.com>
Cc:	linux netdev <netdev@...r.kernel.org>
Subject: Re: [iproute2] tc action mirred    question

On Mon, 2009-09-07 at 05:38 -0700, Xiaofei Wu wrote:

> I just want to know:
> 1) Could I forward the mirroring packets to another node ,and then route it to the destination(if I use 
> iproute2 (ip, tc ...)  )?  I described my purpose in my last email.

Yes, you can mirror to another node(B/D). To route on that node(B/D),
your dst MAC address has to be correct for that destination node(B/D) to
accept it. You could try to run  the destination node in promisc mode
and you may be able to get away without changing dst mac.

> 2)  After I mirrored the packets, I should use 'ip route' , 'ip rule' to modify route tables.  Is this right?
> 

Assuming you are talking about B/D, yes you can do routing there if the
node accepts it..

> >You should repeat the same on wlan1 to mirror to wlan0 i.e on wlan1:
> >match ip src 192.168.2.0/24 ...
> >action mirred egress mirror dev wlan0
> 
> Would this cause loops?
> 

Ok, so this was the trick question;->
I dont see how the loop would happen - they are different "match" rules
i.e one is for 192.168.2.0/24 and the other is for 192.168.1.0/24
Whether it loops or not is easy for you to verify.

cheers,
jamal

--
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