Date: Tue, 5 Jun 2007 10:09:24 +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: <200706051009.25548.nvass@teledomenet.gr> In-Reply-To: <20070604113754.GA89017@glebius.int.ru> References: <1179829392.00743801.1179818401@10.7.7.3> <200706040957.38906.nvass@teledomenet.gr> <20070604113754.GA89017@glebius.int.ru>
index | next in thread | previous in thread | raw e-mail
On Monday 04 June 2007 14:37, Gleb Smirnoff wrote: > On Mon, Jun 04, 2007 at 09:57:36AM +0300, Nikos Vassiliadis wrote: > N> On Friday 01 June 2007 14:14, Gleb Smirnoff wrote: > N> > On Wed, May 30, 2007 at 02:32:21PM +0300, Alexander Motin wrote: > N> > A> Nikos Vassiliadis wrote: > N> > A> >> In my case doing a few times: > N> > A> >> ifconfig fxp0 192.168.1.71/16 > N> > A> >> ifconfig fxp0 192.168.1.71/24 > N> > A> >> locks the box. > N> > A> > N> > A> Doing this you are dropping all routes going via that network. > N> > Probably you A> are dropping route to your pptp peer which can > lead to N> > wrapping tunnel A> inside himself. > N> > > N> > Yes. This is a known problem with netgraph tunnels. > N> > N> I see. Would it be possible/desirable to control this kind > N> of situations using a LINK[012] flag? I mean having code/kludge > N> doing loop detection? > > I think that in this case loop detection can be implemented only > using mbuf tags. Thanks for the info. I'll try to break to the debugger and keep you informed about it. Nikoshelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706051009.25548.nvass>