From: John Adams <johna@onevista.com>
To: netfilter@lists.samba.org
Subject: Re: 2 ISPs on firewall
Date: Tue, 2 Jul 2002 22:29:16 -0400 [thread overview]
Message-ID: <200207030229.WAA23566@onevista.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207021852410.20445-100000@e33.eng.roonetworks.com>
On Tuesday 02 July 2002 09:53 pm, Matthias Kattanek wrote:
> There seems to be lots of question about multihomed firewall/routers.
> I am in similiar situation. Having 2 ISP, where to provide services too.
>
> I managed to forward traffic to e.g. a web server in the DMZ zone.
> Main problem I encounter is that the response is always going out
> via the DEFAULT gateway on the router.
> (In my case one ISP doesn't like it and drops the response.)
>
> I was under the impression that connection tracking of Netfilter keeps
> "track" which interface the traffic came in and anticipated it would go
> out the same route it came from.
>
> What am I missing here?
> What does it take to make it happen?
> Do I just need additional rules for Netfilter?
> Would something like "ip_conntrack_isp" work out? Understood such module
> needs to be developed. Q just arises is that a way to go?
Here's a script I use with iproute2. It gives two default routes with
different weightings for different speed lines.
johna
GATEWAY0=216.254.97.1
GATEWAY1=65.185.37.22
NIC0=216.254.97.15
NIC1=65.185.37.21
route del default
ip route add 0.0.0.0/0 via $GATEWAY0 table E0
ip route add 0.0.0.0/0 via $GATEWAY1 table E1
ip rule add from $NIC0 table E0
ip rule add from $NIC1 table E1
ip route add default scope global \
nexthop via $GATEWAY0 weight 6 \
nexthop via $GATEWAY1 weight 1
ip route flush cache
next prev parent reply other threads:[~2002-07-03 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 1:53 2 ISPs on firewall Matthias Kattanek
2002-07-03 2:29 ` John Adams [this message]
2002-07-03 17:46 ` Carlos Lopez
-- strict thread matches above, loose matches on Subject: below --
2002-07-03 2:12 George Vieira
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=200207030229.WAA23566@onevista.com \
--to=johna@onevista.com \
--cc=netfilter@lists.samba.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