[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Wed Jun 1 12:21:01 2005 -->
- <!--x-from-r13: genafnz ng irelfrpheryvahk.pbz (Pbo Fbkra) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Firewall design -->
- <li><em>date</em>: Wed Jun 1 12:21:01 2005</li>
- <li><em>from</em>: transam at verysecurelinux.com (Bob Toxen)</li>
- <li><em>in-reply-to</em>: <<a href="msg00009.html">[email protected]</a>></li>
- <li><em>references</em>: <[email protected]> <[email protected]> <<a href="msg00009.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] Firewall design</li>
Bob
On Wed, Jun 01, 2005 at 07:56:53AM -0400, Stuffed Crust wrote:
> On Tue, May 31, 2005 at 10:19:44PM -0400, Christopher Fowler wrote:
> > What ever I do my plan is to create the firewall as a bridging firewall
> > with _no_ address. The only access will be via serial console. We'll
> > install a console management device at the remote site so I will have to
> > access it first remotely before I can connect to the console on the
> > firewall to config or make changes.
>
> This limits its effectiveness somewhat, as you'll be forced to use
> ebtables instead of iptables, which has a much smaller functionality
> set. This is because when bridging the IP traffic never actually hits
> the interfaces, thus the standard INPUT/FORWARD/OUTPUT rules never
> apply. And NAT will certianly have to be handled by another machine;
> one with actual IP addresses configured.
>
> Is there any reason you don't do the following:
>
> ISP ---- [ NID box ] ------ SERVER1 [nat] --- INTERNAL network
> |--- SERVER2
> |--- SERVER3
> |--- SERVER4
> |----SERVER5
>
> Granted, this way you end up needing to configure firewalls on each
> machine. You could [transparently] insert your bridge firewall machine
> after the NID box much like you need a hub or switch there anyway.
>
> The above illustration is how I have things set up at work, and if
> bright house networks didn't want $80/month more for multiple IPs, at
> home as well. Each SERVER has its own firewall configured, and SERVER1
> does NAT for the internal private network.
>
> - Pizza
> --
> Solomon Peachy ICQ: 1318344
> Melbourne, FL JID: pitha at myjabber.net
> Quidquid latine dictum sit, altum viditur
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00009" href="msg00009.html">[ale] Firewall design</a></strong>
<ul><li><em>From:</em> pizza at shaftnet.org (Stuffed Crust)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00032.html">[ale] OT: Good Support Company for 3Com IP Phone System?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00034.html">[ale] Job Opening - Information Security Manager</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00012.html">[ale] Firewall design</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00005.html">[ale] USB external HDD</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00033"><strong>Date</strong></a></li>
<li><a href="threads.html#00033"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>