Firewall Wizards mailing list archives

Re: Firewall routing thought...


From: Devdas Bhagat <devdas () dvb homelinux org>
Date: Thu, 8 Jul 2004 23:00:34 +0530

On 06/07/04 13:50 -0400, Gwendolynn ferch Elydyr wrote:
On Fri, 2 Jul 2004, Eric Appelboom wrote:
If one has firewall A with external ip on the same subnet as firewall B.
How common is the practice of adding static routes on firewall A for The
networks protected by firewall B and the other way round.

Would this technique not lower the latency or overheads of not having the
packets en route from firewall A to firewall B being sent to its default
gateway to then be processed by the router and sent to firewall B. Thus the
traffic would be direct A<-->B

I think you're a bit confused about how routing/routers work, and what
the relative "costs" are.

Your network layout isn't really clear from your email, but as soon as
you make a change in broadcast domains, the router is going to be involved.
I thought it was fairly clear.

                                  Router
                                 ___|___
                                /       \
                                A       B
                                |       |
                                N1      N2      (internal networks)

A and B have default routes pointing to the router interface.
Hence, traffic flows from A to B and back via the router. The OP asks if
it is worthwhile to set static routes on A and B to bypass the router
and avoid the extra hop, since they are directly connected systems.


Besides being a tad messy would it be considered and at what traffic rate?

Well - I generally wouldn't consider it at any traffic rate.

First of all, it's not likely to improve your latency or overhead. The
packets are still going to be seen by the router.
Not in the network diagram above. Eric's point was that the router would
not process those packets at all.

Secondly, you've now added complexity to your network in the form of a
bunch of static routes in different places, all of which need to be
maintained - and almost certainly won't be, until some changes breaks
things.
If these are Unix systems, then putting the configurations of both
systems in a single place is a good idea. Use a versioning system to
manage the files, and then check them out when you need to change
configurations. Not as clean as a simpler configuration with a single
default route and directly connected hosts on the other end, but not
much more complex either.
Make things simple, but no simpler than they need to be.

"a tad messy" is almost always a signal to run away screaming.  That's
code for "unmaintainable" and "all-nighters".
Agreed.

Ranting briefly, a good design should be clear and easy to understand
and explain.  If you find yourself handwaving, or muttering quickly to
get past some point in your design [or adding in "here be dragons"],
you should stop and figure out why.
and then fix the design so that you don't need to handwave [0].

Devdas Bhagat
[0] Or at least document the decision requirements and logic so that the
next person can make changes if needed.
_______________________________________________
firewall-wizards mailing list
firewall-wizards () honor icsalabs com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards


Current thread: