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/OPNFLWPLUG-557 OpenFlowPlugin <p>Handshake in Openflow (both 1.0 and 1.3) is incorrect. </p> <p>Spec says that a HELLO exchange must be completed for controller and switch to agree to the features. Controller starts issuing further protocol dependent requests <em>BEFORE</em> it gets the first HELLO from the switch. This is a violation of the spec.</p> <p>Compliance to the spec should be the standard behavior and should be possible to override it when dealing with non-compliant implementations via a settable config property.</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-557

Broken protocol handling part 1 - incorrect handshake

Bug Resolved Cannot Reproduce Unassigned Anton Ivanov Tue, 6 Oct 2015 08:59:58 +0000 Mon, 27 Sep 2021 09:01:39 +0000 Mon, 2 Nov 2015 18:19:18 +0000 General 0 2 <p>Hi Anton,<br/> what makes you think that openflowPlugin sends further requests before receiving get-features reply from switch?</p> <p>Trying to reproduce it again - I lost the tpcdump trace where the controller was sending the stats request before it should. Once I have it, will update the bug.</p> <p>Hi guys,</p> <p>I tested handshake with ODL and Ryu, but only Ryu follows exactly what the specs says. A OFPT_HELLO response message isn't sent back to device. </p> <ul> <li>Controller IPL: 10.0.1.6</li> </ul> <p>Captures here:</p> <p>ODL handshake: <a href="https://www.cloudshark.org/captures/750ff9b41e8f" class="external-link" target="_blank" rel="nofollow noopener">https://www.cloudshark.org/captures/750ff9b41e8f</a><br/> Ryu handshake: <a href="https://www.cloudshark.org/captures/6e1f33a9deb0" class="external-link" target="_blank" rel="nofollow noopener">https://www.cloudshark.org/captures/6e1f33a9deb0</a></p> <p>I think it's not exactly a bug, but a matter of protocol conformity.</p> <p>I talked to Michal and he told me that the pipeline flushing was optimized. <br/> That's why we can see a OFPT_HELLO response from controller inside of OFPT_FEATURES_REQUEST (packet #2) here: <a href="https://www.cloudshark.org/captures/750ff9b41e8f" class="external-link" target="_blank" rel="nofollow noopener">https://www.cloudshark.org/captures/750ff9b41e8f</a>.</p> Development External issue ID 4418 External issue URL Rank 0|i031vz: