diff options
| author | Avneesh Sachdev <avneesh@opensourcerouting.org> | 2012-02-19 10:19:52 -0800 |
|---|---|---|
| committer | Avneesh Sachdev <avneesh@opensourcerouting.org> | 2012-04-08 13:46:29 -0700 |
| commit | 3b381c32fc2c325cc4ffb9f9f30a7e96e9bd87c6 (patch) | |
| tree | b4eb46f5fe28b4734723c9ff4227a94a5bd32b4e /bgpd/bgp_btoa.c | |
| parent | e96b312150d8e376c1ef463793d1929eca3618d5 (diff) | |
bgpd: fix issue in capability negotiation (BZ#700)
Address problem where bgpd would reject a session if a peer sent some
capabilities in its Open message, but did not include a Multiprotocol
extensions capability. Note that the session would come up if there
were no capabilities at all in the Open message.
* Add the 'mp_capability' out parameter to
bgp_capability_parse(). Set it to '1' if a Multiprotocol
extensions capability is encountered.
* Switch on 'mp_capability' instead of 'capability' in the calling
functions to determine if the peer indicated the set of AFI/SAFIs
it supports.
The net result is that when a peer does not send an MP capability,
it is assumed to support the AFI/SAFIs configured for it locally.
Diffstat (limited to 'bgpd/bgp_btoa.c')
0 files changed, 0 insertions, 0 deletions