From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SNAT or DNAT or what?
Date: Tue, 15 Apr 2003 18:10:35 +0000 [thread overview]
Message-ID: <marc-lartc-105043029309656@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105041792824038@msgid-missing>
Hi Ashok,
: > Are you fetching mail from a particular mailserver? If so:
: > # mailserver!3.165.64.20
: > # route add -host $mailserver gw 192.168.2.1
: > # mailserver!3.165.64.20
: > # ip route add $mailserver via 192.168.2.1
: > -Martin
:
: Wouldnt setting up ip rules to forward the appropriate traffic through the
: proper gateway be better?
Why use the RPDB if you don't need to? I subscribe to the KISS notion
(keep it simple, stupid!).
If all of his mail connections are to a single "smarthost", or a small set
of IP addresses, there's no reason for him to use "ip rule", since he can
make a specific route in the main routing table to the destination.
If he is using multiple mailservers in "unknown" networks, then he'll need
to look at the link load sharing solutions, such as multipath routes, or
multiple outbound links with RPDB/fwmark'ing solutions.
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-04-15 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 14:43 [LARTC] SNAT or DNAT or what? Torsten Puls
2003-04-15 15:05 ` Martin A. Brown
2003-04-15 17:48 ` N N Ashok
2003-04-15 18:10 ` Martin A. Brown [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-105043029309656@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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.