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