Reload fails - bird 1.3.2
I think this is harmless, but reload all does this: bird> reload all kernel1: reload failed device1: reload failed MyBGP: reloading If I understand rightly what reload is meant to do for kernel/device (nothing), shouldn't this either report 'reloading' or say 'skipped' or something? I spent a little while debugging this thinking I've done something wrong. Config below (same as before) just in case I have. -- Alex Bligh protocol kernel { persist; # Don't remove routes on bird shutdown scan time 10; # Scan kernel routing table every 20 seconds import all; export all; learn; # Learn all alien routes from the kernel } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol bgp MyBGP { local as 65000; neighbor 10.255.199.1 as 65000; export filter { accept; }; import filter { accept; }; next hop self; import all; export all; }
On Wed, Aug 17, 2011 at 07:56:37PM +0100, Alex Bligh wrote:
I think this is harmless, but reload all does this:
bird> reload all kernel1: reload failed device1: reload failed MyBGP: reloading
If I understand rightly what reload is meant to do for kernel/device (nothing), shouldn't this either report 'reloading' or say 'skipped' or something?
You are right, this is just harmless. For device protocol it is really nothing (as device protocol is pseudoprotocol which does not generate any routes). For kernel protocol, reload might have a sense (you could change import filter and then use 'configure soft'), but is not implemented (and not really important, because there are periodic scans that works in a similar manner). -- 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."
participants (2)
-
Alex Bligh -
Ondrej Zajicek