From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Craig Subject: Re: Match packet mark with --set-mark to ip rule fwmark Date: Wed, 07 Jan 2004 15:00:43 +1000 Sender: netfilter-admin@lists.netfilter.org Message-ID: <3FFB927B.4010208@snapgear.com> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: kaiwen Cc: netfilter@lists.netfilter.org kaiwen wrote: > (3) [root@g webauth]# ip ro show table test2 > prohibit 192.168.8.122 > > I expect ping from 192.168.8.122 to 192.168.250.197 to be drop, BUT is is > successful. Why? > Did I miss out anything? Please advice. prohibit specifies the destination address, not the source. So the ping from 192.168.8.122 to 192.168.250.197 will get through. Additionally, the reply goes through OUTPUT, not PREROUTING, so it won't be marked and dropped either. If you add your mark rule to the OUTPUT chain, then you should see the reply being dropped. I assume you are just using prohibit for testing: there is no point marking a packet with iptables and then dropping it iproute2, when you could just drop it with iptables in the first place. -- Philip Craig - SnapGear, A CyberGuard Company - http://www.SnapGear.com