From owner-freebsd-bugs@FreeBSD.ORG Fri Sep 4 19:35:27 2009 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4587F106566B for ; Fri, 4 Sep 2009 19:35:27 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 9D8F78FC14 for ; Fri, 4 Sep 2009 19:35:26 +0000 (UTC) Received: (qmail 25500 invoked from network); 4 Sep 2009 19:35:24 -0000 Received: from unknown (HELO ?10.0.0.135?) (spawk@128.238.64.31) by acm.poly.edu with AES256-SHA encrypted SMTP; 4 Sep 2009 19:35:24 -0000 Message-ID: <4AA16BCB.9000801@acm.poly.edu> Date: Fri, 04 Sep 2009 15:34:35 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: Remko Lodder References: <200908311737.n7VHb4NC068143@freefall.freebsd.org> <4AA1286A.9030302@acm.poly.edu> <0E54C96F-296A-453C-A5B2-99B51D810379@elvandar.org> <4AA1458F.7030106@acm.poly.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@freebsd.org Subject: Re: kern/138407: [gre] gre(4) interface does not come up after reboot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2009 19:35:27 -0000 The other end is a machine that can't be rebooted for testing as frequently so I can't check how it behaves. Its tunnel is up and running. It's 7.1, though, so I don't even think it was a problem back then. Anyway, the state of the remote GRE tunnel does not appear to have any bearing on the problem. I have sniffed traffic from the 128.x machine on an intermediate router and it does not send anything out to the remote machine when I get the "ping: sendto: Network is down" message. Interestingly (or not?), running tcpdump on the GRE interface that doesn't have the RUNNING flag adds the RUNNING flag to it, and then it works. -Boris Remko Lodder wrote: > > I have multiple tunnels that work correctly that way. (6). Do you need > to issue 'ifconfig gre0 up' on the other side before it starts > working? or do you need to force > it on the 128.x machine? (please try both). > > On Sep 4, 2009, at 6:51 PM, Boris Kochergin wrote: > >> ifconfig_gre0="inet 10.0.0.1 10.0.0.2 netmask 255.255.255.0 tunnel >> 128.238.9.201 69.12.180.23 up" >> >> ...in rc.conf still leaves gre0 unusable after the system comes up. >> There are workarounds, but this seems like something that should be >> fixed. >