From: Paco Brufal <pbrufal@mutoid.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing to two interfaces
Date: Thu, 21 Nov 2002 18:28:45 +0000 [thread overview]
Message-ID: <marc-lartc-103790338109308@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103783300809624@msgid-missing>
On nov/20/2002, Martin A. Brown wrote:
> Good luck, Paco. I'd suggest returning here if you have specific troubles
> after you have digested these, and understand how they can help solve your
> current problem.
OK, I read what you suggested me, and the documents didn't answer my
question, but they gave me some ideas, and now all is working like I want :)
I have the luck that each service in the internal network has it own
IP, then I set up some iptables rules to redirect (via DNAT) the external
packets to internal servers. Then, in the router box, I set up routing
tables based on source hosts (the internal servers). When a packet arrives
from 10.10.10.2 (DNS), route it via eth1, if packet comes from 10.10.10.3
(HTTP) or 10.10.10.4 (SMTP), route it via eth2.
If somebody is interested in the exact commands, I can post the
script I used...
Thanks to everybody :)
--
...Slamma Jamma. Dj Omar Santana. 1996
--- Debian + Mutt + Postfix
* Origin: Web Page: http://pbrufal.kleenux.org (Fido 2:346/7.68)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-11-21 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 22:55 [LARTC] routing to two interfaces Paco Brufal
2002-11-20 23:05 ` Martin A. Brown
2002-11-20 23:26 ` Robert Felber
2002-11-20 23:34 ` Robert Felber
2002-11-20 23:45 ` Martin A. Brown
2002-11-21 0:04 ` Robert Felber
2002-11-21 0:09 ` Robert Felber
2002-11-21 0:27 ` Paco Brufal
2002-11-21 0:38 ` Paco Brufal
2002-11-21 3:37 ` Martin A. Brown
2002-11-21 8:27 ` Arthur van Leeuwen
2002-11-21 18:28 ` Paco Brufal [this message]
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=marc-lartc-103790338109308@msgid-missing \
--to=pbrufal@mutoid.org \
--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.