From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Source routing, sort of
Date: Mon, 24 Dec 2001 20:57:24 +0000 [thread overview]
Message-ID: <marc-lartc-100922750709226@msgid-missing> (raw)
I have a system with two interfaces, eth0 is on the Internet, eth1 on
an internal connection. Because of using ipsec and its internal
routing, I need certain connections to be made from the internal
interface that will be going out over the ipsec0 device.
For example:
eth0: 1.2.3.4 (internet address)
ipsec0: 1.2.3.4 (always the same as the external interface)
eth1: 192.168.0.1 (internal address)
ping -n 192.168.1.1 (over VPN) attempts to send a ping from 1.2.3.4
because ipsec0's interface address is 1.2.3.4. How can I get arbitrary
connects, based on destination, to be sourced from 192.168.0.1 instead
of 1.2.3.4?
I'm assuming some basic source NATting is required; off to read the
docs again ...
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
reply other threads:[~2001-12-24 20:57 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=marc-lartc-100922750709226@msgid-missing \
--to=mbabcock@fibrespeed.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox