* [LARTC] Source routing, sort of
@ 2001-12-24 20:57 Michael T. Babcock
0 siblings, 0 replies; only message in thread
From: Michael T. Babcock @ 2001-12-24 20:57 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-12-24 20:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-24 20:57 [LARTC] Source routing, sort of Michael T. Babcock
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox