From: Bill Davidsen <davidsen@tmr.com>
To: netfilter@lists.netfilter.org
Subject: Re: Fairly complex multi-ISP firewall/router problem
Date: Fri, 02 Apr 2004 22:17:49 -0500 [thread overview]
Message-ID: <406E2CDD.2070900@tmr.com> (raw)
In-Reply-To: <1080943679.3421.4.camel@4100.internal.techforless.com>
Joe Thompson wrote:
> What is the architecture between the rest of the world and your
> firewall? Is it possible to use BGP and only one of the public
> subnets? This would in effect move the redundancy of the public side to
> the router(s) allowing you to use standard method's at the firewall.
All of the internal stuff is on a 192.168.x.x net. So that a packet
comes in NIC1 and gets DNAT'd to the internat address, then the reply
comes back to the firewall with the correct destination address, and the
source address gets reset correctly. That's where the problem comes in,
since now the packet can go back our through the NIC to either ISP. But
if it goes out the *wrong* NIC, the ISP thinks I'm spoofing and drops
the packet.
>
> We run a similar situation with one of our subnets, we have two circuits
> from separate provider's who were both gracious enough to add the routes
> in they're tables, if we lose one connection the rest of the world just
> uses the other route in and we of course use the other route out. The
> downside is getting both upstream providers to cooperate in routing, the
> upside is that you can utilize both links and keep things simple from an
> addressing perspective.
I actually left out a bit of the complexity, some of the outgoing
connections *must* go through one NIC or the other, because the
destination will only accept from a given source IP (and that IP will
only go out through the appropriate ISP).
There are two ways to patch this, one by addint the IP to the ARP table
with the MAC of the correct router, one by some code to ignore any NIC
which doesn't have an alias for the source address. Both are patches I
don't want to maintain.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-04-03 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 20:57 Fairly complex multi-ISP firewall/router problem Bill Davidsen
2004-04-02 21:06 ` Antony Stone
2004-04-03 3:24 ` Bill Davidsen
2004-04-02 21:32 ` Cedric Blancher
2004-04-02 21:36 ` John A. Sullivan III
2004-04-02 21:50 ` Antony Stone
2004-04-02 22:07 ` Joe Thompson
2004-04-03 3:17 ` Bill Davidsen [this message]
2004-04-13 9:29 ` Tarek W.
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 23:45 Daniel Chemko
2004-04-03 3:31 ` Bill Davidsen
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=406E2CDD.2070900@tmr.com \
--to=davidsen@tmr.com \
--cc=netfilter@lists.netfilter.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