All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis" <alexis@attla.net.ar>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Firewall four nics, two separate routes
Date: Mon, 26 Jan 2004 23:37:30 -0300	[thread overview]
Message-ID: <000f01c3e47e$830e4ab0$0200000a@heretic> (raw)
In-Reply-To: 002f01c3e47a$7a6f3f80$0200000a@heretic

its too late at night, i drive so many kms today, i cant write.

this is the real message


think lan1 lan2 wan1 wan2

the firewall box, must have NO default route

ip rule add from lan1 lookup table 5
ip rule add from lan2 lookup table 6
ip route add default via wan1 table 5
ip route add default via wan2 table 6

sorry


----- Original Message ----- 
From: "Alexis" <alexis@attla.net.ar>
To: "netfilter" <netfilter@lists.netfilter.org>
Sent: Monday, January 26, 2004 11:08 PM
Subject: Re: Firewall four nics, two separate routes


> think lan1 lan2 wan1 wan2
>
> the firewall box, must have NO defaul route
>
> ip rule add from lan1 lookup table 5
> ip rule add from lan2 lookup table 6
> ip route add default via wan1 table 5
> ip route add default via wan1 table 6
>
> thats it.
>
>
>
> ----- Original Message ----- 
> From: "Ryan Johnson" <rjohnson@espgroup.net>
> To: <netfilter@lists.netfilter.org>
> Sent: Monday, January 26, 2004 2:49 PM
> Subject: Firewall four nics, two separate routes
>
>
> Hi all,
>
> I have a firewall with four nics, two external nics with two public ips
and
> two internal nics with private ips (two different networks). What I would
> like to do is force all traffic from each internal network to its
> corresponding external nic. I believe the only solution to this is to use
> iproute2, but I have had to luck. So traffic from internal net1 will be
> routed out external nic1, then the other side, internal net2 will be
routed
> out the external nic2. Internal net1 traffic should never go out external
> nic2 and internal net2 traffic should never go out external nic1.
>
>
> Thank you in advance,
> Ryan
>
> Ryan Johnson
> Security Architect
> ESP Group
>
>
>
>
>
>




  reply	other threads:[~2004-01-27  2:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 17:49 Firewall four nics, two separate routes Ryan Johnson
2004-01-27  2:08 ` Alexis
2004-01-27  2:37   ` Alexis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-26 18:50 bmcdowell

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='000f01c3e47e$830e4ab0$0200000a@heretic' \
    --to=alexis@attla.net.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.