Changes

From SME Server
Jump to navigationJump to search
143 bytes added ,  11:58, 21 March 2019
Line 17: Line 17:  
The contrib basically works but there, can be complications when you want to combine it with standard host-host ipsec connections. The issue that 'may' arise is if an IPSEC connection is matched prior to the L2TPD one. I do have both types running on my test box but need more feedback on this.  
 
The contrib basically works but there, can be complications when you want to combine it with standard host-host ipsec connections. The issue that 'may' arise is if an IPSEC connection is matched prior to the L2TPD one. I do have both types running on my test box but need more feedback on this.  
   −
This is because pure ipsec usually relies on having connections from specific IP address / and or IDs / Certificates. To accept mobile clients, which could come from pretty well any IP address, we need to tell out L2TPD Ipsec configuration to accept connections from anywhere.  
+
This is because pure ipsec usually relies on having connections from specific IP address / and or IDs / Certificates. To accept mobile clients, which could come from pretty well any IP address, we need to tell our L2TPD Ipsec configuration to accept connections from anywhere.  
    
The potential issue is if you try a pure Ipsec connection that does not have a correct configuration in the database/configuration, it may try to connect via the L2TPD connection. That will not break anything, but you may experience odd results from the client.
 
The potential issue is if you try a pure Ipsec connection that does not have a correct configuration in the database/configuration, it may try to connect via the L2TPD connection. That will not break anything, but you may experience odd results from the client.
Line 39: Line 39:  
{{Note box|If you had installed an earlier version e.g 0.2x or lower then please uninstall first. The early dev versions used /etc/e-smith/templates-custom for their templates. Make sure there are no fragments lying about or you may get unexpected results.}}
 
{{Note box|If you had installed an earlier version e.g 0.2x or lower then please uninstall first. The early dev versions used /etc/e-smith/templates-custom for their templates. Make sure there are no fragments lying about or you may get unexpected results.}}
   −
The smeserver-libreswan-xl2tpd contrib is currently in the development repo at Contribs
+
The smeserver-libreswan-xl2tpd contrib is currently in the contribs repo.
   −
You will need the EPEL repo as well:
+
Add the EPEL and Libreswan repos:
 +
 
 +
yum  install smeserver-extrarepositories-libreswan smeserver-extrarepositories-epel
 +
signal-event yum-modify
 +
config set UnsavedChanges no
   −
https://wiki.contribs.org/Epel
      
With the yum repo database updated, you can then run the installation of the package.
 
With the yum repo database updated, you can then run the installation of the package.
   −
  yum --enablerepo=smedev,epel install smeserver-libreswan-xl2tpd
+
  yum --enablerepo=smecontribs,epel,libreswan install smeserver-libreswan-xl2tpd
    
That should bring everything in, including ipsec which is required
 
That should bring everything in, including ipsec which is required
Line 142: Line 145:     
  config setprop pptpd status disabled sessions 0
 
  config setprop pptpd status disabled sessions 0
 +
 +
signal-event remoteaccess-update
    
Take this action only *after* you have confirmed proper L2TP connection is working.
 
Take this action only *after* you have confirmed proper L2TP connection is working.

Navigation menu