Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: G Georgiev <subscriptions@navig.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SNAT on IPSEC tunnel with kernel 2.6/KAME tools?
Date: Thu, 11 May 2006 14:58:12 +0000	[thread overview]
Message-ID: <200605111101.12051.subscriptions@navig.ca> (raw)
In-Reply-To: <200605031322.30125.subscriptions@navig.ca>


	Could you (or someone else on the list) just tell me how this can be done 
with the netfilter? I could not find a way for it. I am with kernel 2.6.16-14 
now. The problem, again:

 >     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
 >
 >     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"

	George.

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

  parent reply	other threads:[~2006-05-11 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:22 [LARTC] SNAT on IPSEC tunnel with kernel 2.6/KAME tools? G Georgiev
2006-05-05 13:39 ` Patrick McHardy
2006-05-05 16:37 ` G Georgiev
2006-05-11 14:58 ` G Georgiev [this message]
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=200605111101.12051.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox