bugzilla-daemon at allevil
Jun 22, 2007, 11:14 AM
Post #3 of 4
Please do not reply directly to this email. All additional
[Bug 368] error in bgp fsm transitions (OpenSent)
[In reply to]
comments should be made in the comments box of this bug
------- Additional Comments From mukesh [at] cs 2007-06-22 19:14 -------
Sorry for the delay in getting back to you. Somehow, I didn't get a notification
about your first comment. Anyway, I can confirm that the change for
TCP_fatal_error fixes the problem for me. (I applied that change, and tested the
The other two changes (for TCP_connection_open and TCP_connection_open_failed) I
haven't applied or tested. It would be a couple of weeks before I got try that
out. And even then, I don't think my test environment would test the
That said, the change for TCP_connection_open_failed makes sense.
For TCP_connection_open, however, both the existing code, and the proposed
patch, seem wrong. According to the RFC, a TCP_connection_open event in the
OpenSent state should be dealt with via Connection Collision processing
mechanism. So the call to bgp_stop seems premature (regardless of whether Quagga
transitions to Idle or Active).
Does that sound right, or have I missed something?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Quagga-bugs mailing list
Quagga-bugs [at] lists