[quagga-users 9963] Re: OSPF binding to wrong interface on FreeBSD 7
jgreco at ns.sol.net
Wed Oct 1 21:15:39 IST 2008
> John Lingate schrieb:
> > This bug was reported around the release of FreeBSD 7, but does not seem
> > to have made any progress.
> > http://bugzilla.quagga.net/show_bug.cgi?id=420
> > Is this because the sockopt.c.diff patch is correct, which isn't
> > entirely clear from the following comments, or is there some other
> > solution to this problem? Thanks!
> Just a question for clarity:
> I see that the FreeBSD port contains a small patch from Jan-2008 that adds
> three lines to sockopt.c to restore old behaviour:
> Can anyone confirm that the current quagga port works correctly on RELENG_7?
It Does Not. It looks like it appears to under certain circumstances,
such as if you only have one interface advertising (this is based on
observation, not analysis). It definitely goes to hell if you use it
in an environment with a bunch of interfaces. We were using Quagga out
of ports originally when we first saw all this.
The sockopt.c.diff patch appears like it might work, except that we're
still seeing a low incidence of OSPF "events" which we haven't isolated.
There was a response, I believe on the FreeBSD lists, that suggested it
wasn't really a correct solution.
I've refrained from commenting until now since we didn't have a good
feeling for how it was behaving in the long run. In the short run, it
*appears* to work just like older Quagga on older FreeBSD.
Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
"We call it the 'one bite at the apple' rule. Give me one chance [and] then I
won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN)
With 24 million small businesses in the US alone, that's way too many apples.
More information about the Quagga-users