Date: Fri, 04 Sep 2009 15:34:35 -0400 From: Boris Kochergin <spawk@acm.poly.edu> To: Remko Lodder <remko@elvandar.org> Cc: freebsd-bugs@freebsd.org Subject: Re: kern/138407: [gre] gre(4) interface does not come up after reboot Message-ID: <4AA16BCB.9000801@acm.poly.edu> In-Reply-To: <A9E537B5-91F2-4AEC-A5E0-3AEEB3ECBB3A@elvandar.org> References: <200908311737.n7VHb4NC068143@freefall.freebsd.org> <4AA1286A.9030302@acm.poly.edu> <0E54C96F-296A-453C-A5B2-99B51D810379@elvandar.org> <4AA1458F.7030106@acm.poly.edu> <A9E537B5-91F2-4AEC-A5E0-3AEEB3ECBB3A@elvandar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AA16BCB.9000801>