On May 12, 2004, at 2:41 PM, Mark Johnson wrote:

What if sessions were attacked without MD5 in place. We would just see session resets. As these happen anyway frequently at peering points is there any straightforward way to determine if the vulnerability caused the reset?

Depends on why it happens frequently. If it happens because you've got Network/Transport Layer or underlying connection problems then there's some other brokenness you should probably be more concerned with. If you're referring to session resets because of a peer or user action then something akin to "Last reset due to FOO" can likely be gleaned from "show bgp neighbor" output, especially since BGP performs "graceful shutdown" via notification messages under normal conditions I.e., you should probably be very concerned with any session reset for which no valid explanation is available via CLI or other means. -danny