From: Chris Verges <squirrel@headnut.org>
To: netfilter@lists.netfilter.org
Subject: firewall rules for subinterfaces
Date: Thu, 14 Oct 2004 23:55:35 -0400 [thread overview]
Message-ID: <20041015035535.GA19170@clifford.headnut.org> (raw)
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
When I try to do this at the command line, iptables spits back
an error about how colons (:) are not allowed in the interface
name. That brings up the interesting question of how to do this
whole thing ...
Any advice or insight is greatly appreciated!
Thanks,
chris
--
http://headnut.org
squirrel@headnut.org
next reply other threads:[~2004-10-15 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 3:55 Chris Verges [this message]
2004-10-15 12:03 ` firewall rules for subinterfaces 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
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=20041015035535.GA19170@clifford.headnut.org \
--to=squirrel@headnut.org \
--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