From: Kevin McConnell <kevymac@yahoo.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Brad Chapman <kakadu_croc@yahoo.com>,
Afshin Lamei <linux_st@hotmail.com>,
netfilter@lists.netfilter.org
Subject: Re: Doing Bridge with firewalling
Date: Tue, 31 Dec 2002 12:47:56 -0800 (PST) [thread overview]
Message-ID: <20021231204756.1918.qmail@web40306.mail.yahoo.com> (raw)
In-Reply-To: <20021231202708.GP677@ns>
--- Stephen Frost <sfrost@snowman.net> wrote:
> The two havn't got anything to do with each other.
> NATing is modifying
> packets as they pass through the router. Addressing
> is the IP address
> and whatnot to access the firewall/router. One does
> not require the
> other.
This leads me to another question then. What are the
advantages of not having an IP address assigned to
interface(s) of the firewall? Like for instance, if my
firewall was the gateway to the outside world, how
would I tell machines behind the firewall to get out
to the outside world if they didn't have a default
route pointing to the internal address of the
firewall? Also, how would packets that hit the
firewall get routed through the other side?
=====
Kevin C. McConnell --RHCE-- <Red Hat Certified Engineer>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
next prev parent reply other threads:[~2002-12-31 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 10:51 Doing Bridge with firewalling Afshin Lamei
2002-12-31 16:08 ` Kevin McConnell
2002-12-31 19:03 ` Brad Chapman
2002-12-31 20:23 ` Kevin McConnell
2002-12-31 20:27 ` Stephen Frost
2002-12-31 20:47 ` Kevin McConnell [this message]
2002-12-31 20:54 ` Stephen Frost
2002-12-31 21:30 ` Ranjeet Shetye
2002-12-31 22:19 ` Kevin McConnell
2003-01-01 15:10 ` Stephen Frost
2003-01-01 15:08 ` Stephen Frost
2003-01-06 14:16 ` Toshihiro Sonoda
2003-01-06 15:03 ` Stephen Frost
2002-12-31 22:01 ` Kevin McConnell
2002-12-31 22:31 ` Arnt Karlsen
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=20021231204756.1918.qmail@web40306.mail.yahoo.com \
--to=kevymac@yahoo.com \
--cc=kakadu_croc@yahoo.com \
--cc=linux_st@hotmail.com \
--cc=netfilter@lists.netfilter.org \
--cc=sfrost@snowman.net \
/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