From: Jandre Olivier <jandre@megaserve.net>
To: lartc@vger.kernel.org
Subject: [LARTC] src routing question
Date: Thu, 09 Sep 2004 09:04:59 +0000 [thread overview]
Message-ID: <41401CBB.2050003@megaserve.net> (raw)
Howzit guys,
I have a question that has been boggling my mind:
i have 2 servers( firewalls)
1 server connected to main ISP and another to another ISP( only certain
traffic 195.0.0.0/8)
Server 1 to main ISP:
lan: eth0 192.168.1.0/24
outside: eth1 196.15.203.194/30 gw 196.15.203.193
DMZ: eth3 196.16.202.209/28 (mailservers etc )
private: eth4 10.0.10.2/24
Server 2 to second ISP ( only certain ips route through that)
# network 195.0.0.0/8 must route through here
outside: eth1 10.0.1.35/24
private: eth0 10.0.10.1/24
I use `ip rule add fwmark` and `iptables -t mangle PREROUTING` to route
packets marked for 195.0.0.0/8 through 10.0.10.1/32
I masquarade the packets leaving eth1 on server 2 to 195.0.0.0/8
I want my DMZ section to be able to route to that network as well via
10.0.10.1
obviously when a packet from 195.0.0.0/8 send me a mail it comes in on
server 1(via the internet) and should go back out server 1 ( with src
routing enabled )
My question:
with src routing enabled if I mark packets use `iptables -t mangle
PREROUTING -i eth3 -s 196.16.202.209/28 -p all -j MARK --set-mark 888`
will packets coming from 195.0.0.0 then be routed through server 2 , it
wont work then cause its not src routed?????
When i start a download or something from the mailserver in the dmz
zone, it go out via server2 , but will packets coming which originate
from 195.0.0.0/8 via internet be routed out through server 1 again with
my src routing enabled
i tried to explain it quite clearly, hope its understandable
Hope u guys can help
Thanks
--
Regards
Jandre
"Some people are alive only because
it is illegal to kill them."
_____________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-09-09 9:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41401CBB.2050003@megaserve.net \
--to=jandre@megaserve.net \
--cc=lartc@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 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.