* Firewall four nics, two separate routes
@ 2004-01-26 17:49 Ryan Johnson
2004-01-27 2:08 ` Alexis
0 siblings, 1 reply; 4+ messages in thread
From: Ryan Johnson @ 2004-01-26 17:49 UTC (permalink / raw)
To: netfilter
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Firewall four nics, two separate routes
@ 2004-01-26 18:50 bmcdowell
0 siblings, 0 replies; 4+ messages in thread
From: bmcdowell @ 2004-01-26 18:50 UTC (permalink / raw)
To: netfilter
Well, it doesn't seem to be very thorough, and it wouldn't encompass
non-IP (_IP_tables), but what about something like:
iptables -A FORWARD -i eth0 -o ! eth1 -j LOG --log-prefix "Wrong Route:
" (and -j DROP)
iptables -A FORWARD -i eth2 -o ! eth3 -j LOG --log-prefix "Wrong Route:
" (and -j DROP)
Test this. I'm just guessing here.
Bob
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Ryan Johnson
Sent: Monday, January 26, 2004 11:50 AM
To: netfilter@lists.netfilter.org
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Firewall four nics, two separate routes
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
0 siblings, 1 reply; 4+ messages in thread
From: Alexis @ 2004-01-27 2:08 UTC (permalink / raw)
To: netfilter
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Firewall four nics, two separate routes
2004-01-27 2:08 ` Alexis
@ 2004-01-27 2:37 ` Alexis
0 siblings, 0 replies; 4+ messages in thread
From: Alexis @ 2004-01-27 2:37 UTC (permalink / raw)
To: netfilter
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
>
>
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-01-27 2:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2004-01-26 18:50 bmcdowell
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.