Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Dimitri Yioulos <dyioulos@onpointfc.com>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Cc: "DiCecca, Caitlin" <cdicecca@onpointfc.com>
Subject: Re: Dual WAN setup redux
Date: Wed, 1 Feb 2012 11:51:30 -0500	[thread overview]
Message-ID: <201202011151.30910.dyioulos@onpointfc.com> (raw)
In-Reply-To: <1328030100.2018.1.camel@andy-laptop>

On Tuesday 31 January 2012 12:15:00 pm Andrew Beverley wrote:
> On Fri, 2012-01-27 at 18:03 -0500, Dimitri Yioulos wrote:
> > Well, here I am, again, asking for help setting up a dual WAN.
>
> Any chance of an ascii diagram? It's a bit difficult to understand what
> you have and what you are trying to achieve without it.
>
> Andy
>
>

Lloyd, Andy, and others,

Let me see what I can do here:


                                                                WAN2                       
                                ___________   75.x.x.24/29, gw 75.x.x.30
                                |              |---------eth3 (75.x.x.25) 
                                |              |      (eth0:0=75.x.x.26, ...)
Local network           |              |                   
192.168.100.0/22 ----|fw/router|                 WAN1
eth1 (192.168.100.1) |              |   65.x.x.160/27, gw 65.x.x.161
                                |__________|--------eth0 (65.x.x.162)
                                       |             (eth0:0=65.x.x.163, ... )
                                       |                     
                                    DMZ  
                           192.168.1.0/24             
                         eth1 (192.168.1.1)    
                                       |                                       |               
                                       |                      
                                       |
          ___________________|_____________________               
          |                   |                   |                   |
        box1            box2             box3            box4
   192.168.1.2  192.168.1.3   192.168.1.4   192.168.1.5
   (65.x.x.163    (65.x.x.164   
      eth0:0)          eth0:1)

I'd like for boxes 3 and 4 to use WAN2.

The above probably looks like an unholy mess (and it may be; a discussion for 
another day, though), but hope it helps clarify things.  That's what I'm after.

Thanks.

Dimitri

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


  reply	other threads:[~2012-02-01 16:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 23:03 Dual WAN setup redux Dimitri Yioulos
2012-01-31  1:50 ` Lloyd Standish
2012-01-31 17:15 ` Andrew Beverley
2012-02-01 16:51   ` Dimitri Yioulos [this message]
2012-02-01 18:49     ` Andrew Beverley
2012-02-01 19:46       ` Dimitri Yioulos
2012-02-01 20:25         ` Andrew Beverley
2012-02-01 20:35 ` Andrew Beverley
2012-02-01 22:08   ` Dimitri Yioulos
2012-02-01 23:32     ` Andrew Beverley
2012-02-02  7:35     ` Andrew Beverley
  -- strict thread matches above, loose matches on Subject: below --
2012-02-02 17:52 Dimitri Yioulos
2012-02-02 23:11 ` Andrew Beverley

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=201202011151.30910.dyioulos@onpointfc.com \
    --to=dyioulos@onpointfc.com \
    --cc=cdicecca@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