From: Andre Correa <andre.correa@pobox.com>
To: netfilter@lists.netfilter.org
Subject: Re: firewall rules for subinterfaces
Date: Fri, 15 Oct 2004 12:25:46 -0200 [thread overview]
Message-ID: <416FDDEA.20209@pobox.com> (raw)
In-Reply-To: <416FCE80.9090801@pbl.ca>
Hi, there is really no meaning on setting rules for subinterfaces, If
you need to segment your network and can't plug new NICs look for VLANs.
You can apply rules indicating VLAN interfaces (-i and -o) like this:
eth0.100, eth0.200, etc...
Somebody correct me if I'm wrong but this was made possible under >= 2.6
kernel versions, on 2.4.x you can't do it too.
Hope it helps.
Andre
Aleksandar Milivojevic wrote:
> Chris Verges wrote:
>
>> Hey,
>>
>> Is there a way to add firewall rules for subinterfaces? I'm
>> trying to do the equivalent of:
>>
>> eth0 Intel Pro 10/100
>> eth0:0 192.168.1.1
>> eth0:1 192.168.2.1
>>
>> iptables -A INPUT -p icmp -i eth0:0 -j DENY
>> iptables -A INPUT -p icmp -i eth0:1 -j ACCEPT
>
>
> Nope you can't do that. There's no point in doing it. Just as you
> added virtual interfaces to your firewall box, so can any node on your
> network, effectively bypassing such firewall rules. If you have a need
> for such rules, than you really have a need for two separate physical
> networks (otherwise, you are implementing security by obscurity, which
> doesn't really work).
>
> If all you wanted to do is to force clients to use specific IP address
> on your firewall box, then do it by specifying destination IP address
> ("-i eth0 -d 192.168.1.1 -j DROP" and "-i eth0 -d 192.168.2.1 -j
> ACCEPT"). BTW, dropping all ICMP traffic might not be a good idea.
>
next prev parent reply other threads:[~2004-10-15 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 3:55 firewall rules for subinterfaces Chris Verges
2004-10-15 12:03 ` Leonardo Rodrigues Magalhães
2004-10-15 12:06 ` George Alexandru Dragoi
2004-10-15 13:20 ` Aleksandar Milivojevic
2004-10-15 14:25 ` Andre Correa [this message]
2004-10-15 14:44 ` Cedric Blancher
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=416FDDEA.20209@pobox.com \
--to=andre.correa@pobox.com \
--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