[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(racoon 786) Re: Ipsec connection from gateway itself over vpn
- To: racoon@kame.net
- Subject: (racoon 786) Re: Ipsec connection from gateway itself over vpn
- From: KObermueller@t-online.de (Kay Obermueller)
- Date: Fri, 01 Oct 2004 11:32:31 +0200
- Delivered-to: racoon-archive@kame.net
- Delivered-to: racoon-outgo@kame.net
- Delivered-to: racoon@kame.net
- In-reply-to: <415C973F.2040502@t-online.de>
- References: <415C973F.2040502@t-online.de>
- Reply-to: racoon@kame.net
- Sender: owner-racoon@kame.net
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040820 Debian/1.7.2-4
Kay Obermueller wrote:
Hello everyone,
I'm not sure whether to place my question here or in the shorewall
mailing list.
I have created an ipsec connection with racoon in tunnel mode to
another gateway to connect one subnet on each side to each other. This
works fine. Only the ipsec gateway itself can't send packages to the
opposite subnet.
Shorewall is configured according to:
http://www.shorewall.net/IPSEC-2.6.html
Is there a second "roadwarrior" tunnel to be defined just only for the
gateway?
I have patched the kernel linux 2.8.1 and iptables-1.2.11 with the
"policy match" patch, but the "IPSEC-Netfilter" patches (mentioned in:
http://www.shorewall.net/IPSEC.htm) where rejected by patch-o-matic-ng
from 2004/09/21. How are they applied?
Kay
Oops, sorry, I used the kernel sources of 2.6.8 from Debian with Debian
patches.