All of lore.kernel.org
 help / color / mirror / Atom feed
From: "U.Mutlu" <for-gmane@mutluit.com>
To: netfilter@vger.kernel.org
Subject: How to block all packets not destined to local IP's ?
Date: Thu, 18 Oct 2012 03:29:22 +0200	[thread overview]
Message-ID: <k5nm1g$brb$1@ger.gmane.org> (raw)

Subtitle: [xtables geoip] rules not applied to packets for non-configured IP's

Hi,
from the router link (just 1 link) I'm getting traffic for multiple IP's
(a quasi multihomed system, actually a host node and multiple virtual systems therein),
that's correct so, but is there a way to drop all packets to IP's
that are actually not configured on the local system?
Is there a better way than writing a drop/reject-rule for each such IP?

And related to this, I think there is a bug in xtables geoip
because if there is a packet for such a not-configured IP
then the iptables rules (at least geoip rules) aren't applied to such packets.
How to fix this?

Confirmation, fixes and workarounds welcome. Thx.


             reply	other threads:[~2012-10-18  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  1:29 U.Mutlu [this message]
2012-10-18  2:04 ` How to block all packets not destined to local IP's ? U.Mutlu
2012-10-18  3:36   ` U.Mutlu

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='k5nm1g$brb$1@ger.gmane.org' \
    --to=for-gmane@mutluit.com \
    --cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.