VPN - Revision history

Alblasco1702: style from the text

2015-03-06T10:10:42Z

style from the text

←Older revision		Revision as of 10:10, 6 March 2015
Line 11:		Line 11:
	In Wizard -> Basic Info -> Users, check the "Can connect via VPN" for every user that should be able to connect via VPN. Click "Change VPN Password" for the user and enter a password for your VPN connection.		In Wizard -> Basic Info -> Users, check the "Can connect via VPN" for every user that should be able to connect via VPN. Click "Change VPN Password" for the user and enter a password for your VPN connection.
	== from 1004 ==		== from 1004 ==
	Username=pluto_"then the username from lmce".		Username=pluto_"then the username from lmce".<br />
	Password="lmce password for the user".		Password="lmce password for the user".<br />
	select an ip or leave it to automatic.		select an ip or leave it to automatic.<br />
	select where the user can go troug		select where the user can go troug<br />
	1. Core only: Client can only connect to the core (192.168.80.1).		1. Core only: Client can only connect to the core (192.168.80.1).<br />
	2. Core localnetwork: Client can connect to the core and local network.		2. Core localnetwork: Client can connect to the core and local network.<br />
	3. everywhere: Client can connect to the core the local network and the internet.		3. everywhere: Client can connect to the core the local network and the internet.
	== end from 1004 ==		== end from 1004 ==

Alblasco1702: user from 1004

2015-03-06T10:08:35Z

user from 1004

←Older revision		Revision as of 10:08, 6 March 2015
Line 10:		Line 10:

	In Wizard -> Basic Info -> Users, check the "Can connect via VPN" for every user that should be able to connect via VPN. Click "Change VPN Password" for the user and enter a password for your VPN connection.		In Wizard -> Basic Info -> Users, check the "Can connect via VPN" for every user that should be able to connect via VPN. Click "Change VPN Password" for the user and enter a password for your VPN connection.
			== from 1004 ==
			Username=pluto_"then the username from lmce".
			Password="lmce password for the user".
			select an ip or leave it to automatic.
			select where the user can go troug
			1. Core only: Client can only connect to the core (192.168.80.1).
			2. Core localnetwork: Client can connect to the core and local network.
			3. everywhere: Client can connect to the core the local network and the internet.
			== end from 1004 ==

	* Note: Currently you need to re-enable the user and change his username after any change to the Network settings page as the files are rewritten		* Note: Currently you need to re-enable the user and change his username after any change to the Network settings page as the files are rewritten

Alblasco1702: use of pap-secrets instead of chap.

2015-02-10T14:50:45Z

use of pap-secrets instead of chap.

←Older revision		Revision as of 14:50, 10 February 2015
Line 43:		Line 43:

	And approved usernames are here:		And approved usernames are here:
	/etc/ppp/~~chap~~-secrets		/etc/ppp/pap-secrets

	General configuration is here:		General configuration is here:

Jimmejames at 05:25, 6 February 2014

2014-02-06T05:25:31Z

←Older revision		Revision as of 05:25, 6 February 2014
Line 97:		Line 97:
	==External Links==		==External Links==
	#[http://openvpn.net/ OpenVPN]		#[http://openvpn.net/ OpenVPN]


			==PROBABLY GOING TO BREAK A LOT OF THINGS- DO NOT FOLLOW THIS UNTIL IT'S REPORTED WORKING- Feb 5, 2014==
			#https://help.ubuntu.com/community/L2TPServer
			ipsec verify fails on sending bogus ICMP redirects- the following fixed that

			Edit /etc/sysctl.conf and add or uncomment the following lines:

			net.ipv4.ip_forward=1
			net.ipv4.conf.all.accept_redirects = 0
			net.ipv4.conf.all.send_redirects = 0
			net.ipv4.conf.default.send_redirects = 0
			net.ipv4.conf.eth0.send_redirects = 0
			net.ipv4.conf.default.accept_redirects = 0
			net.ipv4.conf.eth0.accept_redirects = 0

			Reload with:
			sudo sysctl -p /etc/sysctl.conf

			Doesn't work: https://help.ubuntu.com/community/L2TPServer

Jimmejames at 15:04, 2 February 2014

2014-02-02T15:04:53Z

←Older revision		Revision as of 15:04, 2 February 2014
Line 44:		Line 44:
	And approved usernames are here:		And approved usernames are here:
	/etc/ppp/chap-secrets		/etc/ppp/chap-secrets

			General configuration is here:
			/etc/xl2tpd/xl2tpd.conf

	=Old/custom VPN=		=Old/custom VPN=

Jimmejames at 14:55, 2 February 2014

2014-02-02T14:55:51Z

←Older revision		Revision as of 14:55, 2 February 2014
Line 38:		Line 38:

	<b>Note</b>: If auth.log is empty, 12.04 has a bug that set the owner incorrectly- fix via: "sudo chown syslog /var/log/auth.log" from a terminal		<b>Note</b>: If auth.log is empty, 12.04 has a bug that set the owner incorrectly- fix via: "sudo chown syslog /var/log/auth.log" from a terminal

			From a terminal, you can verify your preshare key here:
			/etc/ipsec.secrets

			And approved usernames are here:
			/etc/ppp/chap-secrets

	=Old/custom VPN=		=Old/custom VPN=

Jimmejames at 05:18, 7 January 2014

2014-01-07T05:18:24Z

←Older revision		Revision as of 05:18, 7 January 2014
Line 36:		Line 36:
	You can also monitor authentication procedure with:		You can also monitor authentication procedure with:
	tail -f /var/log/auth.log		tail -f /var/log/auth.log

			<b>Note</b>: If auth.log is empty, 12.04 has a bug that set the owner incorrectly- fix via: "sudo chown syslog /var/log/auth.log" from a terminal

	=Old/custom VPN=		=Old/custom VPN=

Foxi352: /* Debug */

2012-05-28T09:01:37Z

Debug

←Older revision		Revision as of 09:01, 28 May 2012
Line 34:		Line 34:
	Anyway you can debug the connection procedure with tcpdump using the following command:		Anyway you can debug the connection procedure with tcpdump using the following command:
	tcpdump -i any port 500 or port 4500		tcpdump -i any port 500 or port 4500
			You can also monitor authentication procedure with:
			tail -f /var/log/auth.log

	=Old/custom VPN=		=Old/custom VPN=
	The following is a hack to add VPN support to LinuxMCE for version prior to 1004. It may not even work anymore, and I would not recommend it.		The following is a hack to add VPN support to LinuxMCE for version prior to 1004. It may not even work anymore, and I would not recommend it.

Foxi352: Added debugging information

2012-05-28T08:52:04Z

Added debugging information

←Older revision		Revision as of 08:52, 28 May 2012
Line 30:		Line 30:
	'''Do NOT forward port 1701 (L2TP)''', this would have allowed direct access to the L2TP server, bypassing IPSEC entirely and sending all your data unencrypted. The whole idea is that the IPSEC connection encrypts your data from end to end, and on the server end, this data will be passed on to port 1701 internally.		'''Do NOT forward port 1701 (L2TP)''', this would have allowed direct access to the L2TP server, bypassing IPSEC entirely and sending all your data unencrypted. The whole idea is that the IPSEC connection encrypts your data from end to end, and on the server end, this data will be passed on to port 1701 internally.

			==Debug==
			As per nature of VPN there is not much debug possibility. VPN servers silently drop wrong packets to not give any information to potential hackers.
			Anyway you can debug the connection procedure with tcpdump using the following command:
			tcpdump -i any port 500 or port 4500
	=Old/custom VPN=		=Old/custom VPN=
	The following is a hack to add VPN support to LinuxMCE for version prior to 1004. It may not even work anymore, and I would not recommend it.		The following is a hack to add VPN support to LinuxMCE for version prior to 1004. It may not even work anymore, and I would not recommend it.

Foxi352: /* VPN in LinuxMCE 1004 */

2012-05-28T07:44:05Z

VPN in LinuxMCE 1004

←Older revision		Revision as of 07:44, 28 May 2012
Line 3:		Line 3:
	VPN (Virtual Private Networking) provides secure communication to your core when you are away. It also offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)		VPN (Virtual Private Networking) provides secure communication to your core when you are away. It also offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)
	=VPN in LinuxMCE 1004=		=VPN in LinuxMCE 1004=
	In LinuxMCE 1004 there is an integrated L2TP server.		In LinuxMCE 1004 there is an integrated L2TP server. It uses openswan and xl2tpd packages.

	==Setup==		==Setup==