Re: quagga misinterpreting route.

2016-11-12 Thread Zaphod Beeblebrox
After upgrading to 10.3p12 and messing about a bit, I found something else strange. On another mpd router, the ipv6 route was showing up as being on an unused port (bce1, in this case). I have the port connected to the switch (so it's up) but I'm not using it. So... I ifconfig'd down bce0. Then,

quagga misinterpreting route.

2016-11-12 Thread Zaphod Beeblebrox
I have an if-up mpd5 rule that says: route -n6 add $route -iface $interface where $route is something like 1001:abcd:1::/64 and $interface is something like ng2. When I go into quagga, I see: my.router.ca# sh ipv6 route 1001:abcd:1::1 Routing entry for 1001:abcd:1::/64 Known via "kernel", dis

[Bug 194109] [lor] if_lagg rmlock <-> if_addr_lock

2016-11-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194109 Ryan Stone changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org |rst...@freebsd.org -- You are receiv

[Bug 194109] [lor] if_lagg rmlock <-> if_addr_lock

2016-11-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194109 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: rstone Date: Sat Nov 12 19:03:24 UTC 2016 New revision: 308580 URL: https://svnweb.freebsd.org/changeset/base/308580 Log: Don't read if_counters with i