On Mon, Nov 23, 2009 at 12:50:19PM +0100, Wolfgang Hennerbichler wrote:
On Nov 23, 2009, at 08:19 , Wolfgang Hennerbichler wrote:
On Nov 20, 2009, at 16:17 , Ondrej Zajicek wrote:
On Fri, Nov 20, 2009 at 02:19:05PM +0100, Wolfgang Hennerbichler wrote:
Fellow Bird Users,
Now I realized that if I changed the definition for 'allnet' and do a 'configure soft' these routes that are added or removed to 'allnet' are not rejected or added, because it seems that there is no bgp soft reconfiguration taking place (it works if I trigger a soft reconfiguration outbound on the peer router, or if I restart the protocol which causes bgp to flap).
BGP soft reconfiguration is not implemented. 'configure soft' just means 'ignore changes in filters'.
because my co-worker gave me a hint, that it might not be totally clear what I'm asking for:
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. BTW, what kind of user interface would be useful for you? - per protocol request for route refresh - something like 'configure' but with route refresh instead of protocol restart? it should ignore, report or restart peers that does not support router refres? -- 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."