From owner-freebsd-net@FreeBSD.ORG Mon Jun 4 07:01:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6783816A469 for ; Mon, 4 Jun 2007 07:01:32 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from wmail.teledomenet.gr (wmail.teledomenet.gr [213.142.128.16]) by mx1.freebsd.org (Postfix) with ESMTP id 003B913C46E for ; Mon, 4 Jun 2007 07:01:31 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris (unknown [192.168.1.71]) by wmail.teledomenet.gr (Postfix) with ESMTP id C97E41C90ED; Mon, 4 Jun 2007 10:01:29 +0300 (EEST) From: Nikos Vassiliadis To: Gleb Smirnoff Date: Mon, 4 Jun 2007 09:57:36 +0300 User-Agent: KMail/1.9.1 References: <1179829392.00743801.1179818401@10.7.7.3> <465D60C5.50503@freebsd.org> <20070601111457.GY89017@FreeBSD.org> In-Reply-To: <20070601111457.GY89017@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706040957.38906.nvass@teledomenet.gr> Cc: freebsd-net@freebsd.org, Alexander Motin Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 07:01:32 -0000 On Friday 01 June 2007 14:14, Gleb Smirnoff wrote: > On Wed, May 30, 2007 at 02:32:21PM +0300, Alexander Motin wrote: > A> Nikos Vassiliadis wrote: > A> >> In my case doing a few times: > A> >> ifconfig fxp0 192.168.1.71/16 > A> >> ifconfig fxp0 192.168.1.71/24 > A> >> locks the box. > A> > A> Doing this you are dropping all routes going via that network. > Probably you A> are dropping route to your pptp peer which can lead to > wrapping tunnel A> inside himself. > > Yes. This is a known problem with netgraph tunnels. I see. Would it be possible/desirable to control this kind of situations using a LINK[012] flag? I mean having code/kludge doing loop detection? Nikos