From: Steve M Bibayoff <smb23@csufresno.edu>
To: netfilter@lists.netfilter.org
Subject: Using an device alias?
Date: Fri, 03 Jan 2003 11:28:19 -0800 [thread overview]
Message-ID: <b74ecb8788.b8788b74ec@cvip.net> (raw)
Sorry if everyone gets this twice, this one is a
second posting when I realized this was a closed list.
Original question:
Is it possible to use iptables with a device alias
(ex.. eth0:1)? I tries to add a filter rule and got
an error:
% iptables -t filter -I INPUT -i eth0:1 -j ACCEPT
Warning: wierd character in interface `eth0:1' (No
aliases, :, ! or *).
If i list the rules, it's listed, but it doesn't
appear to be working. I was wondering if someone had
a definite answer.
TIA
Steve
next reply other threads:[~2003-01-03 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 19:28 Steve M Bibayoff [this message]
2003-01-04 3:33 ` Using an device alias? Joel Newkirk
[not found] ` <3E19CD4E.2050700@csufresno.edu>
[not found] ` <3E19DD6B.7070503@csufresno.edu>
2003-01-06 19:56 ` Steve
2003-01-06 21:41 ` Joel Newkirk
2003-01-06 5:30 ` Raymond Leach
2003-01-07 17:23 ` WA Support
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 19:07 Steve M Bibayoff
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=b74ecb8788.b8788b74ec@cvip.net \
--to=smb23@csufresno.edu \
--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