All of lore.kernel.org
 help / color / mirror / Atom feed
From: G Georgiev <subscriptions@navig.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] SNAT on IPSEC tunnel with kernel 2.6/KAME tools?
Date: Wed, 03 May 2006 17:22:30 +0000	[thread overview]
Message-ID: <200605031322.30125.subscriptions@navig.ca> (raw)


	Hi,

	Could not conceive an working set-up for an IPSEC VPN made with racoon/setkey 
on which I have one address on my side acting as an SNAT router for all 
traffic from my network to a network segment on the far side. 

my network  --- my gateway  ---------------------- remote network
10.0.0.0/24  - 10.0.0.1 (10.253.0.2)  -- tunnel - 192.168.0.0/22

	All traffic starts on my side, so if I can SNAT/MASQUERADE packets to the 
tunnel address (10.253.0.2) it shall work. This would have been possible with 
FreeSwan, as it created network interfaces (ipsec0, ipsec1..), however with 
setkey there is no way of making it.
	
	The VPN starts on the gateway, simply all traffic destinate to 192.168.0.0/22 
should get an SNAT to 10.253.0.2 and go via the tunnel. SNAT however is 
available only in POSTROUTING chain, and no outgoing interface really exists 
with setkey.

	So, next rule should be implemented on the gateway: "Packets going to 
192.168.0.0/22 should be SNAT to 10.253.0.2 and go via the tunnel"

	Some ideas?

	Thanks, George.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-05-03 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:22 G Georgiev [this message]
2006-05-05 13:39 ` [LARTC] SNAT on IPSEC tunnel with kernel 2.6/KAME tools? Patrick McHardy
2006-05-05 16:37 ` G Georgiev
2006-05-11 14:58 ` G Georgiev
2006-05-12  2:28 ` G Georgiev
2006-05-12  5:04 ` Patrick McHardy

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=200605031322.30125.subscriptions@navig.ca \
    --to=subscriptions@navig.ca \
    --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.