> It looks like the internal babel route status and the kernel routing > table can get out of sync when Node B regains comms while NodeA is in > the process of banning the route.
I've had an extended e-mail exchange with the original reporter, and spent all evening trying to reproduce the issue. No such luck. The original reporter himself can no longer reproduce it under 1.3.2. I'm stumped. If anyone else sees this issue, please report. -- Juliusz _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
