>> repeatedly failing and restoring an interface (ifconfig down/up),
This is a known issue, Dave. The code that checks for interface down/up
events is racy, it can get confused if you do up/down/up and it doesn't
trigger before the interface gets back up -- it thinks that nothing
changes.
The
I stepped back to 1.6.3 and the kernel and babel ribs stayed correct
no matter how much I upped or downed the usb0 interface while keeping
the wifi alive.
This by itself does not mean enough (because source specific routing
is not in 1.6 as best I recall)
In terms of bisecting between babel
I have definitively proven that on at least one of the arm boxes we
are using (the getchip) that there is either a new babel bug in git,
and/or arm related issue with forming the netlink message, or a kernel
bug, or excessive gamma radiation in the atmosphere.
I am going to step back to 1.6.1 and
3 matches
Mail list logo