From: "U.Mutlu" <for-gmane@mutluit.com>
To: netfilter@vger.kernel.org
Subject: Re: How to block all packets not destined to local IP's ?
Date: Thu, 18 Oct 2012 05:36:45 +0200 [thread overview]
Message-ID: <k5ntgc$t1g$1@ger.gmane.org> (raw)
In-Reply-To: <k5no3s$ot0$1@ger.gmane.org>
U.Mutlu wrote, On 10/18/2012 04:04 AM:
> I solved the problem in 2 steps, in that order:
> drop all packets to unwanted dest ip's
> drop all packets from unwanted cc's
>
> If the IP's are consecutive then one can use a the range option of iptables, like this:
> iptables -A INPUT -m iprange --dst-range x.x.x.210-x.x.x.219 -j DROP
>
> Ie.:
> iptables -A INPUT -m iprange --dst-range x.x.x.210-x.x.x.219 -j DROP
> ...
> iptables -A INPUT -m geoip --src-cc CN -j DROP
> ...
Correction: since all packets to non-local IP's go thru the FORWARD chain
the above example must be changed to:
iptables -A FORWARD -m iprange --dst-range x.x.x.210-x.x.x.219 -j DROP
> U.Mutlu wrote, On 10/18/2012 03:29 AM:
>> 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?
...because they go thru the FORWARD chain, not the INPUT chain!... :-)
Problem solved.
prev parent reply other threads:[~2012-10-18 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 1:29 How to block all packets not destined to local IP's ? U.Mutlu
2012-10-18 2:04 ` U.Mutlu
2012-10-18 3:36 ` U.Mutlu [this message]
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='k5ntgc$t1g$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.