Date: Wed, 03 Apr 2013 22:45:00 +0600 From: "Eugene M. Zheganin" <emz@norma.perm.ru> To: freebsd-net@freebsd.org Subject: Re: gre tunnel woes Message-ID: <515C5C8C.50708@norma.perm.ru> In-Reply-To: <20130403181747.0fa7677e@zeta.dino.sk> References: <CAPS9%2BSvcTUQo-O8AefjwpHGKPXwne%2BiWM9P4D4uF-NO8zdt8xw@mail.gmail.com> <20130403150053.GC5100@calendar.blacquiere.nl> <CAPS9%2BSsRe=t34eWEOWkraAMqpdmTP8Of1beGRsSo6c3deQm_LA@mail.gmail.com> <20130403181747.0fa7677e@zeta.dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. On 03.04.2013 22:17, Milan Obuch wrote: > Well, I am struggling with this too, and now I just use /etc/rc.local > containing > > #!/bin/sh > > ifconfig gre0 up > ifconfig gre1 up > > to bring tunnels to real life. Maybe not that nice, but simple and > working. > > It's an ancient bug; it's reported in GNATS ( http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/164475 - it was known long before the report, once I just decided to actually put it in GNATS; unfortunately, it wasn't fixed). Actually, as I can remember, this was never working since gre(4) was introduced in 4.x (for various reasons). It's somehow related with default route for the tunnel remote end, but anyway this still isn't fixed. And yeah, everyone who's using gre is using some sort of custom rc script to fix the RUNNING flag after a boot. Eugene.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515C5C8C.50708>