tree 35a221f0912891b2b04f9337288fbfd479761169
parent a689e6a9f470d2a72493b907c94ef23516bbbda6
author Leonid Rosenboim <lrosenbo@wrs.com> 1354915867 +0000
committer David Lamparter <equinox@opensourcerouting.org> 1358266921 +0100

bgpd: improve logging of invalid BGP Notifications

Invalid BGP Notification messages should be logged locally, cf.
RFC4271, Sect. 6.4, p 34,
  NOTIFICATION Message Error Handling

Current notification for invalid Notification code:

  2012/10/10 02:17:54 BGP: message index 10 not found in bgp_notify_msg (max is 8)
  2012/10/10 02:17:54 BGP: 192.168.1.1 received NOTIFICATION 10/0 ((no item found)) 0 bytes

the logging should be a bit more clear. The above logging really doesn't
explain much and looks more like a programming error.

[rewrote most of it to get in something I can call a shape -David]
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>