https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/BGPCEP-218 bgpcep <p>1) ODL only accepts BGP connection if 4-byte AS capability is sent by peer<br/> 2) When I enable 4-byte AS support in Spirent it sends the capability along with other capabilities in the same parameter as I show below:</p> <p>rame 5: 113 bytes on wire (904 bits), 113 bytes captured (904 bits) Ethernet II, Src: Performa_00:00:05 (00:10:94:00:00:05), Dst: Vmware_ce:72:24 (00:0c:29:ce:72:24) Internet Protocol Version 4, Src: 3.3.3.4 (3.3.3.4), Dst: 3.3.3.3 (3.3.3.3) Transmission Control Protocol, Src Port: 179 (179), Dst Port: 34078 (34078), Seq: 1, Ack: 62, Len: 43 Border Gateway Protocol - OPEN Message<br/> Marker: ffffffffffffffffffffffffffffffff<br/> Length: 43<br/> Type: OPEN Message (1)<br/> Version: 4<br/> My AS: 200<br/> Hold Time: 180<br/> BGP Identifier: 3.3.3.4 (3.3.3.4)<br/> Optional Parameters Length: 14<br/> Optional Parameters<br/> Optional Parameter: Capability<br/> Parameter Type: Capability (2)<br/> Parameter Length: 12<br/> Capability: Multiprotocol extensions capability<br/> Type: Multiprotocol extensions capability (1)<br/> Length: 4<br/> AFI: IPv4 (1)<br/> Reserved: 00<br/> SAFI: Unicast (1)<br/> Capability: Support for 4-octet AS number capability<br/> Type: Support for 4-octet AS number capability (65)<br/> Length: 4<br/> AS Number: 200</p> <p>ODL seems not to like this format because it still complaints about missing 4-byte AS capability where it is clearly there.</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-218

Capability Parameter Parse Issue

Bug Resolved Done Claudio David Gasparini Claudio David Gasparini Tue, 5 May 2015 11:13:33 +0000 Sun, 3 Mar 2019 11:50:25 +0000 Wed, 3 Jun 2015 11:49:35 +0000 Bugzilla Migration Bugzilla Migration BGP 0 5 <p>&gt; ODL seems not to like this format</p> <p>Other devices, including ExaBGP, do put every Capability in separate "Optional Parameter: Capability" container (so "Optional Parameters" becomes a list).<br/> This Open message from Spirent has single element in "Optional Parameters", and "Optional Parameter: Capability" is a list.</p> <p>The current ODL parsing logic expect the ExaBGP case, not the Spirent case.</p> <p>The second paragraph of <a href="https://tools.ietf.org/html/rfc5492#section-3" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc5492#section-3</a> states:<br/> "A BGP speaker determines the capabilities supported by its peer by<br/> examining the list of capabilities present in the Capabilities<br/> Optional Parameter carried by the OPEN message that the speaker<br/> receives from the peer."<br/> which I read as "Spirent is right", but for interoperability reasons, ODL should perhaps expect lists on both levels.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/19787/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/19787/</a></p> <p>Is it possible to cherry-pick this to stable/helium?</p> <p>Thanks/Luis</p> <p>&gt; Is it possible to cherry-pick this to stable/helium?</p> <p>I have heard the answer is "No.", because the patch introduces a rather significant change to internal APIs.</p> Development External issue ID 3117 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02axj: