Linux Netfilter discussions
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: blocking traffic between two internal interfaces ?
Date: Wed, 19 Oct 2005 23:32:56 -0500	[thread overview]
Message-ID: <200510192332.56574.rob0@gmx.co.uk> (raw)
In-Reply-To: <20051020041130.0D02EF6F2@sorry.no-ip-here.net>

On Wednesday 2005-October-19 23:11, Seferovic Edvin wrote:
> I would use interfaces, not IP addresses.
>
> 	You mean - physdev matching?

I mean -i and -o options.

> Iptables -A FORWARD -d 172.20.0.0/16 -m physdev --physdev-in eth1
> -j DROP
>
> This rule works now.. I must had an ESTABLISHED connection in my
> conntrack table since this rule didn't work first time I tried it.

That makes sense. See, you can't evaluate why something doesn't work as 
expected unless you know the whole picture.

> Now Ive restarted my gateway

You can also flush all iptables rules, unload all netfilter modules, 
then reload and restore. You'll start with an empty conntrack table. 
(Someone will mention the new conntrack tool which will work with 
2.6.14 and later.)

> and applied this rule and now I cannot access the 172.20.0.0 net.
>
> Any suggestions?

Was this not the goal? What is to suggest?
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


       reply	other threads:[~2005-10-20  4:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051020041130.0D02EF6F2@sorry.no-ip-here.net>
2005-10-20  4:32 ` /dev/rob0 [this message]
2005-10-20  5:22   ` blocking traffic between two internal interfaces ? Seferovic Edvin
     [not found] <20051020052237.E5BB0F4DA@sorry.no-ip-here.net>
2005-10-20 13:27 ` /dev/rob0
     [not found] <20051020030747.A4016F6F2@sorry.no-ip-here.net>
2005-10-20  3:40 ` /dev/rob0
2005-10-20  4:11   ` Seferovic Edvin
2005-10-20  3:07 Seferovic Edvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510192332.56574.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox