Re: [Babel-users] Route-dete :wq

> I think babel is meant to do triggered updates however using tcpdump I was > not able to see them when the route was inserted. That's a fair assessment. Triggered updates are broken in 1.8.0, they should work in current master. (My fault for introducing the bug, and full credit to Gwendoline

Re: [Babel-users] Route-dete :wq

Hi Toke, possible solutions that come to my mind are: * making babel trigger updates on newly appeared routes Wait, it isn't doing that already? Yeah, this would be an obvious improvement :) I think babel is meant to do triggered updates however using tcpdump I was not able to see them when

Re: [Babel-users] Route-dete:wq

Christof, I'm very much interested in your experiments, which are likely to improve the quality of the Babel implementations. > We have update-interval set to 5 minutes to reduce the load on the network > because we are hoping to run this topology on 500+ APs with 1000+ Clients. The protocol is

Re: [Babel-users] Route-dete :wq

Christof Schulze writes: > possible solutions that come to my mind are: > * making babel trigger updates on newly appeared routes Wait, it isn't doing that already? Yeah, this would be an obvious improvement :) Also, why isn't l3roamd detecting when the client