Date: Fri, 27 Apr 2001 00:30:24 -0500 (CDT) From: Nick Rogness <nick@rogness.net> To: Chris Hardie <chris@summersault.com> Cc: Tony Landells <ahl@austclear.com.au>, questions@FreeBSD.ORG Subject: Re: Confusion about router/firewall traffic from router itself Message-ID: <Pine.BSF.4.21.0104270025200.52943-100000@cody.jharris.com> In-Reply-To: <Pine.BSF.4.33.0104262250070.620-100000@nollie.summersault.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Apr 2001, Chris Hardie wrote: > > >From the sound of things, I'm assuming that our setup is non-standard. > > I'm interested to know what a "typical" setup might be that would > eliminate the need for my earlier questions. It seems that most folks > would have similar starting points: an upstream ISP with a router that > you plug into, a firewall that needs to be the entry point for all > network traffic, and a need to access network services from inside the > network. What would one do rather than plug the link into the > router/firewall? The part that caught me was the fact that you are peering with your ISP with private IP's. Typically, They interconnect with you at 1 point with 1 public IP (normally a T1 or something) and you request additional public space from them or ARIN. Things get difficult when trying to multi-home your network with other ISP's and your carrying Private IP space in your routing tables. May I ask who is your ISP? Nick Rogness <nick@rogness.net> - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0104270025200.52943-100000>