Line 76:
Line 76:
{{Note box|There can only be ONE Ipsec L2TPD-PSK connection}}
{{Note box|There can only be ONE Ipsec L2TPD-PSK connection}}
−
Here we assume your local network is 192.168.101.x
+
Note that some settings are preconfigured in the ipsec_connections database.
−
db ipsec_connections set L2TPD-PSK xl2tpd \
+
db ipsec_connections show L2TPD-PSK
+
+
We need to add some basic settings to the connection. Here we assume your local network is 192.168.101.x
+
+
db ipsec_connections setprop L2TPD-PSK \
status enabled \
status enabled \
IPRangeStart 192.168.101.180 \
IPRangeStart 192.168.101.180 \
IPRangeFinish 192.168.101.200 \
IPRangeFinish 192.168.101.200 \
rightsubnet 192.168.101.0/24 \
rightsubnet 192.168.101.0/24 \
−
passwd somesecret \
+
passwd somesecret
−
dpdaction clear \
−
dpddelay 10 \
−
dpdtimeout 90
{{Note box| You CAN change some values as '''IPRangeStart''' and '''IPRangeFinish''' but you need to keep same subnet.<br>
{{Note box| You CAN change some values as '''IPRangeStart''' and '''IPRangeFinish''' but you need to keep same subnet.<br>
Line 94:
Line 95:
config show dhcpd
config show dhcpd
+
+
{{Note box|Ipsec has access private as default; if you want to connect from wan, you need to change it to public }}
+
+
config setprop ipsec status enabled
Now we can enable the required services which will automatically add the correct firewall ports.
Now we can enable the required services which will automatically add the correct firewall ports.
−
config setprop xl2tpd status enabled
config setprop xl2tpd status enabled
config setprop ipsec status enabled
config setprop ipsec status enabled
signal-event ipsec-update
signal-event ipsec-update
−
−
{{Note box|Ipsec has access private as default; if you want to connect from wan, you need to change it to public }}
You can regenerate the server templates with:
You can regenerate the server templates with: