NetBSD Problem Report #43317

From root@geo.phys.spbu.ru  Sun May 16 23:00:23 2010
Return-Path: <root@geo.phys.spbu.ru>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 9124663BC69
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 16 May 2010 23:00:23 +0000 (UTC)
Message-Id: <20100516230019.8296668F95@geo.phys.spbu.ru>
Date: Mon, 17 May 2010 03:00:19 +0400 (MSD)
From: kab00m@geo.phys.spbu.ru
Reply-To: kab00m@geo.phys.spbu.ru
To: gnats-bugs@gnats.NetBSD.org
Subject: Several bugs in gre
X-Send-Pr-Version: 3.95

>Number:         43317
>Category:       kern
>Synopsis:       Several bugs in gre
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 16 23:05:00 +0000 2010
>Closed-Date:    Fri Sep 30 08:38:08 +0000 2016
>Last-Modified:  Fri Sep 30 08:38:08 +0000 2016
>Originator:     Dima Veselov
>Release:        NetBSD 5.1_RC1
>Organization:
>Environment:
System: NetBSD neo 5.1_RC1 NetBSD 5.1_RC1 (Aliguera) #2: Thu May 13 00:11:42 MSD 2010 kab00m@neo:/usr/obj/sys/arch/amd64/compile/Aliguera amd64
Architecture: x86_64
Machine: amd64
>Description:
	First, applying adress to gre(4) before bringing it up cause immediate panic and reboot. Can't catch message, something about mutex locking against itself.
	Second, route doesn't allow -interface on gre, saying bad value. I don't know if it is a bug, but FreeBSD allow this.
	Third, making a tunnel as documented cause computer freeze upon first usage. I don't know if it has to be allowed, gre(4) manpage and implementation should be consistent.
>How-To-Repeat:
	1. 
	ifconfig gre0 create
	ifconfig gre0 inet 10.11.11.11/23 10.11.11.12
	Here goes panic

	3.
        ifconfig gre0 create
        ifconfig gre0 10.10.10.10 10.10.10.11 netmask 0xffffffff up
        ifconfig gre0 tunnel 10.10.10.10 10.10.10.11
        route add 192.168.10/24 10.10.10.11
	telnet 192.168.10.1
	Here computer freezes

>Fix:
	1. 
	Just bring gre up before assigning address
	ifconfig gre0 create
	ifconfig gre0 up
	ifconfig gre0 inet 10.11.11.11/23 10.11.11.12
	3.
	Don't use same addresses inside tunnel, use virtual ones
	ifconfig gre0 create 
	ifconfig gre0 172.20.20.1 172.20.20.2 netmask 0xffffffff up
	ifconfig gre0 tunnel 10.10.10.10 10.10.10.11
	route add 192.168.10/24 10.10.10.11

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/43317: Several bugs in gre
Date: Mon, 17 May 2010 11:18:53 +0200

 On Sun, May 16, 2010 at 11:05:00PM +0000, kab00m@geo.phys.spbu.ru wrote:

 > 	First, applying adress to gre(4) before bringing it up cause
 >immediate panic and reboot. Can't catch message, something about mutex
 >locking against itself.

 This part is due to pullup #1357, which will be backed out before RC2.

 Martin

State-Changed-From-To: open->feedback
State-Changed-By: dyoung@NetBSD.org
State-Changed-When: Sun, 30 Oct 2011 18:57:18 +0000
State-Changed-Why:
This should be fixed in -current, please give it a try?


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Fri, 30 Sep 2016 08:38:08 +0000
State-Changed-Why:
"should be fixed" since 2011


>Unformatted:
 	Downloaded from ftp.

Home	PR Database Search