From: Dimitri Yioulos <dyioulos@onpointfc.com>
To: netfilter@vger.kernel.org
Subject: Re: Dual WAN set-up
Date: Thu, 12 Jan 2012 17:48:51 -0500 [thread overview]
Message-ID: <201201121748.51479.dyioulos@onpointfc.com> (raw)
In-Reply-To: <1326407319.2182.2.camel@andrew-desktop>
On Thursday 12 January 2012 5:28:39 pm Andrew Beverley wrote:
> On Thu, 2012-01-12 at 16:51 -0500, Dimitri Yioulos wrote:
> > Hi, folks.
> >
> > Please bear with me. I may have asked something similar in
> > the way-back, but am going to ask again, because I really
> > need to get this set up, have absolutely no idea how, and am
> > pertrified at the prospect:
> >
> > I currently have an iptables/Netfilter firewall router
> > configured thusly:
> >
> > WAN
> >
> > (192.168.x.x) LAN -- fw -- DMZ (10.x.x.x)
> >
> > OK, pretty basic. And, it has worked well for a long time.
> >
> > Now, I need to add a second WAN (provided by a second
> > provider). I need it to serve specific boxes in the DMZ, both
> > inbound and outbound. Currently, all boxes in the DMZ are
> > served by the single WAN connection. I'm not sure what other
> > information I need to provide you, but I'm hoping you all can
> > help with very specific instructions or a very detailed
> > how-to
>
> If you check the list archives there's been a few discussions
> on this recently (search for load balancing).
>
> One way of doing it is marking each connection and balancing
> those, as described in this excellent web page:
>
> http://www.sysresccd.org/Sysresccd-Networking-EN-Iptables-and-n
>etfilter-load-balancing-using-connmark
>
> Andy
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> netfilter" in the body of a message to
> majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
Thank, Andy. I'll give it a read. I'm not sure I'm after load
balancing, though, but rather dedicating one WAN to a specific
set of machines, if that's even possible. Also, I've seen
how-to's on the NET, but all assume that you're starting fresh,
and adding two WAN connections. I already have one in place, and
working fine.
Dimitri
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2012-01-12 22:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 21:51 Dual WAN set-up Dimitri Yioulos
2012-01-12 22:28 ` Andrew Beverley
2012-01-12 22:48 ` Dimitri Yioulos [this message]
2012-01-13 7:18 ` Andrew Beverley
2012-01-12 23:08 ` Lloyd Standish
2012-01-12 23:12 ` Lloyd Standish
2012-01-12 23:22 ` Dimitri Yioulos
2012-01-12 23:19 ` Dimitri Yioulos
2012-01-13 0:52 ` Lloyd Standish
2012-01-13 7:25 ` Andrew Beverley
2012-01-13 11:47 ` Dimitri Yioulos
2012-01-13 14:17 ` Lloyd Standish
2012-01-13 15:17 ` Dimitri Yioulos
2012-01-13 15:22 ` Dimitri Yioulos
2012-01-14 2:27 ` Lloyd Standish
[not found] ` <201201160956.23955.dyioulos@onpointfc.com>
2012-01-16 20:28 ` Lloyd Standish
2012-01-13 20:00 ` Lloyd Standish
2012-01-13 20:04 ` Dimitri Yioulos
-- strict thread matches above, loose matches on Subject: below --
2012-01-16 21:43 Dimitri Yioulos
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=201201121748.51479.dyioulos@onpointfc.com \
--to=dyioulos@onpointfc.com \
--cc=netfilter@vger.kernel.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