On Mo, 23.11.2009, 18:09, Ondrej Zajicek wrote:
It was clear for me. I checked route refresh specification and it seems to be pretty easy to implement (at least 'the requesting side' of it), therefore i hope we can implement it soon.
wooohoooo, great news, thank you so much!
BTW, what kind of user interface would be useful for you?
- per protocol request for route refresh
hm. I'm not exactly sure how you mean this - something like: bird> restart protocol R1234 soft
- something like 'configure' but with route refresh instead of protocol restart? it should ignore, report or restart peers that does not support router refres?
like bird> configure route-refresh => i'd prefer the per protocol thing (restart protocl R1234 soft). would be user-friendly and very scalable. if the peer doesn't support route refresh it should notify about it, IMHO. My script could then react and bring the protocol down and up again, on the other hand, depending on how much time you want to spend, you could make that an option in the config-file: protocl bgp R1234 { ... clear soft action [restart|report|ignore] } I'd be happy with a simple notification, though. Thank you so much. Wolfgang
-- Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."