From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.samba.org
Subject: Re: alias
Date: Mon, 3 Jun 2002 23:09:12 +0100 [thread overview]
Message-ID: <200206032209.g53M9DA25322@Networker.rockstone.co.uk> (raw)
In-Reply-To: <20020603220345.61683.qmail@web9904.mail.yahoo.com>
On Monday 03 June 2002 11:03 pm, "Jörgen" Danielsson wrote:
> Running a firewall with 6 diff networks, and using a
> default policy that is drop, then as far as i know you
> have to add -i and -o option to forward rules in order
> for them to work. Or am I wrong there ?
Well, you don't *have* to, but it's a good idea.
However, I still think you can do everything you want to just by calling them
eth1, and not trying to use eth1:0, eth1:1 etc.
Antony.
next prev parent reply other threads:[~2002-06-03 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 19:59 alias =?unknown-8bit?q?J=F6rgen?= Danielsson
2002-06-03 20:37 ` alias Antony Stone
2002-06-03 22:03 ` alias =?unknown-8bit?q?J=F6rgen?= Danielsson
2002-06-03 22:09 ` Antony Stone [this message]
2002-06-03 22:15 ` alias =?unknown-8bit?q?J=F6rgen?= Danielsson
2002-06-03 22:44 ` alias Antony Stone
2002-06-03 20:56 ` alias Alin Nastac
2002-06-03 21:57 ` alias =?unknown-8bit?q?J=F6rgen?= Danielsson
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=200206032209.g53M9DA25322@Networker.rockstone.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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