Re: ng_pptpgre + netmask_change results to lock

2007-06-05 Thread Nikos Vassiliadis
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

Re: ng_pptpgre + netmask_change results to lock

2007-06-04 Thread Gleb Smirnoff
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.

Re: ng_pptpgre + netmask_change results to lock

2007-06-04 Thread Nikos Vassiliadis
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> Do

Re: ng_pptpgre + netmask_change results to lock

2007-06-01 Thread Gleb Smirnoff
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. Proba

Re: ng_pptpgre + netmask_change results to lock

2007-05-30 Thread Alexander Motin
Hi. Nikos Vassiliadis wrote: In my case doing a few times: ifconfig fxp0 192.168.1.71/16 ifconfig fxp0 192.168.1.71/24 locks the box. Doing this you are dropping all routes going via that network. Probably you are dropping route to your pptp peer which can lead to wrapping tunnel inside hims

Re: ng_pptpgre + netmask_change results to lock

2007-05-28 Thread Nikos Vassiliadis
On Monday 28 May 2007 10:57, Julian Elischer wrote: > Nikos Vassiliadis wrote: > > On Tuesday 22 May 2007 10:06, I wrote: > >> Hello everybody, > >> > >> I just managed to lock my box and I want to report it > > define "lock"? > > Does it still respond to on the keyboard? No, but I was trying to

Re: ng_pptpgre + netmask_change results to lock

2007-05-28 Thread Julian Elischer
Nikos Vassiliadis wrote: On Tuesday 22 May 2007 10:06, I wrote: Hello everybody, I just managed to lock my box and I want to report it define "lock"? Does it still respond to on the keyboard? (Assuming you have the debugger in your kernel?). Does it still ping? Sometimes these still re

Re: ng_pptpgre + netmask_change results to lock

2007-05-28 Thread Nikos Vassiliadis
On Tuesday 22 May 2007 10:06, I wrote: > Hello everybody, > > I just managed to lock my box and I want to report it > in case it's known(or it helps in some way). It is a > 6.2-STABLE from March 13. I did update to RELENG_6. > The procedure that triggers > the lock is simple: > > 1) Create a p

ng_pptpgre + netmask_change results to lock

2007-05-22 Thread Nikos Vassiliadis
Hello everybody, I just managed to lock my box and I want to report it in case it's known(or it helps in some way). It is a 6.2-STABLE from March 13. The procedure that triggers the lock is simple: 1) Create a pptp tunnel. 2) Set is as your default gateway. 3) Play a bit with the netmask of the