From owner-freebsd-net@FreeBSD.ORG  Tue Mar 19 04:49:43 2013
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id E0EDA671
 for <freebsd-net@freebsd.org>; Tue, 19 Mar 2013 04:49:43 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 8F51B123
 for <freebsd-net@freebsd.org>; Tue, 19 Mar 2013 04:49:43 +0000 (UTC)
Received: from [192.168.248.33] ([192.168.248.33])
 by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r2J4ndlP004035
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
 for <freebsd-net@freebsd.org>; Tue, 19 Mar 2013 10:49:40 +0600 (YEKT)
 (envelope-from emz@norma.perm.ru)
Message-ID: <5147EE5D.5070203@norma.perm.ru>
Date: Tue, 19 Mar 2013 10:49:33 +0600
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Subject: Re: mpd5 and multiple route to send to clients
References: <9EC8E2D3-A52B-4FF1-B840-3D962DF8D917@gmail.com>
In-Reply-To: <9EC8E2D3-A52B-4FF1-B840-3D962DF8D917@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (elf.hq.norma.perm.ru [192.168.3.10]); Tue, 19 Mar 2013 10:49:41 +0600 (YEKT)
X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1,
 USER_IN_WHITELIST=-100 autolearn=unavailable version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 04:49:43 -0000

Hi.

On 18.03.2013 3:26, Yoann Gini wrote:
> Hello,
>
> I’m Yoann. It’s my first message here so a little brief about me. I’m a OS X Server System Administrator and Trainer, actually working on a FreeBSD based setup for a simple service provider infrastructure.
>
> I currently setup a L2TP over IPSec VPN server with FreeBSD 9.1 and mpd 5.6.
>
> I’ve done with success my setup with radius authentication and all interesting stuff except for one thing that I can’t find on Internet.
>
> I need to push some routes to my clients to configure them to use the VPN interface to reach some private network available behind my server.
>
>
You cannot do this with a pptp or l2tp, they just don't have that ability.
You could do this using openvpn, but openvpn is a horrible mess of 
weirdness and incompatibility.

Standard approach is either using remote pptp/l2tp peer as default 
gateway, or creating a sticky route on the client side.

Eugene.