Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Jun 2007 09:57:36 +0300
From:      Nikos Vassiliadis <nvass@teledomenet.gr>
To:        Gleb Smirnoff <glebius@freebsd.org>
Cc:        freebsd-net@freebsd.org, Alexander Motin <mav@freebsd.org>
Subject:   Re: ng_pptpgre + netmask_change results to lock
Message-ID:  <200706040957.38906.nvass@teledomenet.gr>
In-Reply-To: <20070601111457.GY89017@FreeBSD.org>
References:  <1179829392.00743801.1179818401@10.7.7.3> <465D60C5.50503@freebsd.org> <20070601111457.GY89017@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706040957.38906.nvass>