From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 src/FreeS/WAN
Date: Thu, 14 Feb 2002 06:22:18 +0000 [thread overview]
Message-ID: <marc-lartc-101366776114481@msgid-missing> (raw)
Hi!
I've got two FreeS/WAN gateways setup, with one subnet<->subnet tunnel
setup, which is working fine.
I've setup iproute2 to route anything for either subnet via the ipsec0
device using a src address of the local interface. This is to force
locally generated traffic (ie, traffic generated on the server) to go
through the VPN, rather than out with a source IP of the external
interface.
So I've done:
ip rule add table 1 prio 100
ip route add table 1 <remoteLAN>/CIDR dev ipsec0 src <internalIP>
ip route flush cache
Now, my confusion is with regards to the src <internalIP> bit. I've
been assuming that the 'src ...' syntax actually changes the source IP
in the packets matching the route to the IP specified, much like SNAT
does.
But this doesn't seem to be the case.
With the above rule set in place, traffic from the local LAN gets
routed over the VPN to the other end, but appears to have come from
the IP of whatever LAN client sent the packet, not the internal IP of
the VPN gateway.
I expected that since I haven't specified that table 1 only pertains
to traffic from device 'lo' it should apply the rule to all traffic,
including traffic from the local LAN that's crossing the VPN, and
change the src IP in the packets to its own internal IP.
It's kernel 2.2.19, I believe (definitely a 2.2 series kernel).
What am I missing?
--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.enfusion-group.com] 1:15am up 18 days, 6:35, 2 users
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-02-14 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 6:22 Adrian Chung [this message]
2002-02-14 8:07 ` [LARTC] iproute2 src/FreeS/WAN bert hubert
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-101366776114481@msgid-missing \
--to=adrian@enfusion-group.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.