I'm running 1.2.1, config is like log "/var/log/bird/bird6.log" all; .... protocol bgp Rxxxx { local as myas; neighbor 2001:7f8::y as xxxx; route limit maxv6; import all; export all; table Txxxxyyyy; password "password"; rs client; missing lladdr ignore; passive on; } Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message? Best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333
On Thu, Mar 11, 2010 at 09:02:12PM +0100, Arnold Nipper wrote:
I'm running 1.2.1, config is like
Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message?
Because authentication is handled by kernel and BIRD is not even notified about failed attempts to connect. You would probably see a warning message in kernel message buffer (dmesg). -- 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."
On 11.03.2010 21:21 Ondrej Zajicek wrote
On Thu, Mar 11, 2010 at 09:02:12PM +0100, Arnold Nipper wrote:
I'm running 1.2.1, config is like
Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message?
Because authentication is handled by kernel and BIRD is not even notified about failed attempts to connect. You would probably see a warning message in kernel message buffer (dmesg).
But shouldn't I see that the peer session finally established? Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333
On 11.03.2010 21:44 Arnold Nipper wrote
On 11.03.2010 21:21 Ondrej Zajicek wrote
On Thu, Mar 11, 2010 at 09:02:12PM +0100, Arnold Nipper wrote:
I'm running 1.2.1, config is like
Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message?
Because authentication is handled by kernel and BIRD is not even notified about failed attempts to connect. You would probably see a warning message in kernel message buffer (dmesg).
But shouldn't I see that the peer session finally established?
ic ... BIRD _never_ logs when a session is established. It only logs when a protocol is addedor deleted. But this is more of a configuration issue than a operational message. I very much would like to see session status' changes in the log file :-) Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333
On 3/11/10 10:06 PM, Arnold Nipper wrote:
On 11.03.2010 21:44 Arnold Nipper wrote
On 11.03.2010 21:21 Ondrej Zajicek wrote
On Thu, Mar 11, 2010 at 09:02:12PM +0100, Arnold Nipper wrote:
I'm running 1.2.1, config is like
Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message?
Because authentication is handled by kernel and BIRD is not even notified about failed attempts to connect. You would probably see a warning message in kernel message buffer (dmesg).
But shouldn't I see that the peer session finally established?
ic ... BIRD _never_ logs when a session is established. It only logs when a protocol is addedor deleted. But this is more of a configuration issue than a operational message.
can't confirm that: Mar 11 14:38:56 rs1 bird: R8447x21: State changed to up Mar 11 14:38:56 rs1 bird: R8447x11: Incoming connection from x.x.x.x (port 50804) accepted Mar 11 14:38:56 rs1 bird: R8447x11: BGP session established Mar 11 14:38:56 rs1 bird: R8447x11: State changed to feed Mar 11 14:38:56 rs1 bird: R8447x11: Connected to table T8447x11 Mar 11 14:38:56 rs1 bird: R8447x11: State changed to up
I very much would like to see session status' changes in the log file :-)
what about this in your config: protocol bgp R8447x11 { debug {events, states}; }
Arnold
Wolfgang
On 11.03.2010 23:31 Wolfgang Hennerbichler wrote
On 3/11/10 10:06 PM, Arnold Nipper wrote:
ic ... BIRD _never_ logs when a session is established. It only logs when a protocol is addedor deleted. But this is more of a configuration issue than a operational message.
can't confirm that:
Mar 11 14:38:56 rs1 bird: R8447x21: State changed to up Mar 11 14:38:56 rs1 bird: R8447x11: Incoming connection from x.x.x.x (port 50804) accepted Mar 11 14:38:56 rs1 bird: R8447x11: BGP session established Mar 11 14:38:56 rs1 bird: R8447x11: State changed to feed Mar 11 14:38:56 rs1 bird: R8447x11: Connected to table T8447x11 Mar 11 14:38:56 rs1 bird: R8447x11: State changed to up
I very much would like to see session status' changes in the log file :-)
what about this in your config: protocol bgp R8447x11 { debug {events, states}; }
Will try it ... hopefully the daemon doesn't crash when I apply this to all peers ... Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333
On 11.03.2010 23:31 Wolfgang Hennerbichler wrote
On 3/11/10 10:06 PM, Arnold Nipper wrote:
On 11.03.2010 21:44 Arnold Nipper wrote
On 11.03.2010 21:21 Ondrej Zajicek wrote
On Thu, Mar 11, 2010 at 09:02:12PM +0100, Arnold Nipper wrote:
I'm running 1.2.1, config is like
Connection did not establish as peer hadn't password set. However as soon as he did session came up. So far, so good. But _why_ do I not see a log message?
Because authentication is handled by kernel and BIRD is not even notified about failed attempts to connect. You would probably see a warning message in kernel message buffer (dmesg).
But shouldn't I see that the peer session finally established?
ic ... BIRD _never_ logs when a session is established. It only logs when a protocol is addedor deleted. But this is more of a configuration issue than a operational message.
can't confirm that:
Mar 11 14:38:56 rs1 bird: R8447x21: State changed to up Mar 11 14:38:56 rs1 bird: R8447x11: Incoming connection from x.x.x.x (port 50804) accepted Mar 11 14:38:56 rs1 bird: R8447x11: BGP session established Mar 11 14:38:56 rs1 bird: R8447x11: State changed to feed Mar 11 14:38:56 rs1 bird: R8447x11: Connected to table T8447x11 Mar 11 14:38:56 rs1 bird: R8447x11: State changed to up
I very much would like to see session status' changes in the log file :-)
what about this in your config: protocol bgp R8447x11 { debug {events, states}; }
Perhaps debug commands 1 would already do? Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 9259 299 mobile: +49 172 2650958 fax: +49 6224 9259 333
On Thu, Mar 11, 2010 at 11:40:15PM +0100, Arnold Nipper wrote:
I very much would like to see session status' changes in the log file :-)
what about this in your config: protocol bgp R8447x11 { debug {events, states}; }
Perhaps
debug commands 1
No, 'debug commands' is something different. That controls logging of birdc access. -- 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."
On Thu, Mar 11, 2010 at 10:06:01PM +0100, Arnold Nipper wrote:
On 11.03.2010 21:44 Arnold Nipper wrote
But shouldn't I see that the peer session finally established?
ic ... BIRD _never_ logs when a session is established. It only logs when a protocol is addedor deleted. But this is more of a configuration issue than a operational message.
BIRD does not log much by default, mostly warnings, errors and changes caused by 'configure'. Messages related to ordinary behavior have to be enabled using 'debug' command or config option.
I very much would like to see session status' changes in the log file :-)
To see thus, you should enable it using: debug { events }; in appropriate protocol section. Or perhaps: debug protocols { events }; as a global option for all protocols. -- 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 (3)
-
Arnold Nipper -
Ondrej Zajicek -
Wolfgang Hennerbichler