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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1253104099.4584.9.camel@dogo.mojatatu.com>
Date:	Wed, 16 Sep 2009 08:28:19 -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-14 at 06:44 -0700, Xiaofei Wu wrote:

> On node A I run 'ping 192.168.1.215'(IP addr of node C eth0) on node A, one request 'only' get one reply. It's strange.
> On node B,
> window1:  'tcpdump -i wlan1 -n -e', I can see the mirroring packets.
> window2:  'tcpdump -i wlan2 -n -e', I see noting.
> It seems that node B didn't forward the mirroring packects. So I did anotner experiment to check it. 
> I am sure node B can forward packets. But it didn't forward the mirroring packets, why?  (something wrong 
> with the mirroring packets?)
> 

Please put some effort - these are things you can resolve on your
own. Many possibilities on node B:

- run netstats to see forwarding stats
- run ping from node B to .215 to see if you can reach it.
- check ARP tables
- add explicit route to .215
- check rpfilter

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