14
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − Copied from http://forums.contribs.org/index.php?topic=36033.0+ − ='''IPSec Network-to-Network VPN SME Server 7.1 HOWTO'''= + + − + − +
no edit summary
Extracted from http://forums.contribs.org/index.php?topic=36033.0
='''IPSec Network-to-Network VPN SME Server 7.1 HOWTO'''=
Author(s): Lloyd Keen, David Biczo
'''Author(s): Lloyd Keen, David Biczo'''
Revised: 7th March 2007
'''Revised: 7th March 2007'''
Summary: The purpose of this howto is to guide you through the procedure to connect two private subnets, both behind servers running SME Server version 7.1 in server/gateway mode via an encrypted tunnel using IPsec (sometimes referred to as NETKEY or Kernel IPsec). Both servers have static IP’s on the external interface using PPPoE or bridged Ethernet. NETKEY under linux 2.6 works a bit different to Ipsec under linux 2.4, the most obvious difference being that there is no visible ipsecx device as such. This document serves as a guide only, it worked for us but YMMV. As usual “all care but no responsibility taken”. Comments and suggestions are welcome. If you don’t feel comfortable following the procedure described below, then I have written a script which will prompt you for the required settings and automate the process for you. You can download the script here. This script is written for my personal use - if you can get any benefit from it - great, but if it doesn't work then you're on your own. You can download the script from here: [http://www.comnetel.com/sme7_ipsec/ipsec_install.sh]
Summary: The purpose of this howto is to guide you through the procedure to connect two private subnets, both behind servers running SME Server version 7.1 in server/gateway mode via an encrypted tunnel using IPsec (sometimes referred to as NETKEY or Kernel IPsec). Both servers have static IP’s on the external interface using PPPoE or bridged Ethernet. NETKEY under linux 2.6 works a bit different to Ipsec under linux 2.4, the most obvious difference being that there is no visible ipsecx device as such. This document serves as a guide only, it worked for us but YMMV. As usual “all care but no responsibility taken”. Comments and suggestions are welcome. If you don’t feel comfortable following the procedure described below, then I have written a script which will prompt you for the required settings and automate the process for you. You can download the script here. This script is written for my personal use - if you can get any benefit from it - great, but if it doesn't work then you're on your own. You can download the script from here: [http://www.comnetel.com/sme7_ipsec/ipsec_install.sh]