From owner-freebsd-questions@FreeBSD.ORG Fri Mar 14 08:15:28 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F3CEE18 for ; Fri, 14 Mar 2014 08:15:28 +0000 (UTC) Received: from at-hacker.in (at-hacker.in [188.120.233.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CB46C212 for ; Fri, 14 Mar 2014 08:15:27 +0000 (UTC) Received: from broadband-5-228-66-233.nationalcablenetworks.ru ([5.228.66.233] helo=[192.168.1.9]) by at-hacker.in with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1WOMkz-000INJ-1Q for freebsd-questions@freebsd.org; Fri, 14 Mar 2014 11:42:17 +0400 Message-ID: <5322B2A6.6020305@at-hacker.in> Date: Fri, 14 Mar 2014 11:41:26 +0400 From: Alex Pereklad User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: VPN choices? References: <5321F437.25463.1EE12BF@g8kbvdave.gmail.com> <5322B0BB.1070409@laverenz.de> In-Reply-To: <5322B0BB.1070409@laverenz.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2014 08:15:28 -0000 14.03.2014 11:33, Uwe Laverenz пишет: > I would recommend OpenVPN: it's free, reliable, scalable and quite > easy to install. There are tons of docs and howtos available. > > If you need a comfortable windows client, please have a look at this one: > > http://sourceforge.net/projects/securepoint/files/?source=navbar > OpenVPN has very strange behavior sometimes. For example, on server you have server's side of VPN tunnel IP 192.168.1.1 and client's side IP 192.168.1.2. You suppose that you openvpn client gets tunnel IP 192.168.1.2. But that's not true. The client thinks that it has IP 192.168.1.6 and the server has 192.168.1.5 %-( That's strange :-) And you can't ping IP 192.168.1.2 from server, but can ping 192.168.1.6 :-) But you have to set 192.168.1.2 as router to the client's network, not 192.168.1.6.