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/CONTROLLER-60 controller <p>The signed value for OpenFlow port numbers is exposed in the web GUI, which causes problems for port numbers &gt;=32768. Aside from the negative value being confusing, this prevents flow programming when the port is specified.</p> <p>Steps to Reproduce using OVS:</p> <ul class="alternate" type="square"> <li>sudo ovs-vsctl add-br C1</li> <li>sudo ovs-vsctl set-controller C1 tcp:&lt;odl-ip&gt;:6633</li> <li>sudo ovs-vsctl add-port C1 eth0 &#8211; set Interface eth0 ofport_request=32768</li> </ul> <p>Operating System: Linux<br/> Platform: PC</p> CONTROLLER-60

Signed Value Used for OpenFlow Port Number

Bug Resolved Won't Do Venkata Siva Vijayendra Bhamidipati seils Fri, 22 Nov 2013 14:42:27 +0000 Tue, 25 Jul 2023 08:22:50 +0000 Tue, 2 Jun 2015 16:40:46 +0000 adsal 0 6 <p>Hi Seils,</p> <p>The command :<br/> sudo ovs-vsctl add-port C1 eth0 &#8211; set Interface eth0 ofport_request=32768<br/> is working fine with mininet version 2.1.0+ and openflow 1.3.<br/> If you run the command :<br/> sudo ovs-vsctl add-port C1 eth0 &#8211; set Interface eth0 ofport_request=-212</p> <p>It will not accept the negative values.So it is working fine.</p> <p>(In reply to Rajani Srivastava from comment #1)<br/> &gt; Hi Seils,<br/> &gt; <br/> &gt; The command :<br/> &gt; sudo ovs-vsctl add-port C1 eth0 &#8211; set Interface eth0 ofport_request=32768<br/> &gt; is working fine with mininet version 2.1.0+ and openflow 1.3.<br/> &gt; If you run the command :<br/> &gt; sudo ovs-vsctl add-port C1 eth0 &#8211; set Interface eth0 ofport_request=-212<br/> &gt; <br/> &gt; It will not accept the negative values.So it is working fine.</p> <p>I just tested the Hydrogen base image and the issue still exists. Port numbers &gt;32768 are represented as negative values.</p> <p>Attachment attachment_for_value&gt;32768_in_mininet.png has been added with description: checked for the value 33333</p> <p>Attachment opendaylight_GUI_for_vale&gt;32768.png has been added with description: checked in opendaylight GUI</p> <p>Hi Seils,</p> <p>I tested it again on Hydrogen base image.And found that for port number &gt; 32768 ,it is working fine in command line as well in Opendaylight GUI.<br/> Please find the attachments and update me where are you getting the negative values.</p> <p>Attachment ports_info.png has been added with description: checked port number is accepted by ;</p> <p>Checked that port number is accepted with following commands :</p> <p>sudo ovs-vsctl list interface<br/> sudo ovs-ofctl dump-ports br1</p> <p>Hi Rajani,</p> <p>If you pass a port number greater than 32767 when adding an interface to the bridge in ovs, it will show up as a negative integer in the ODL GUI when you look at the port numbers for devices. You will see the right value in ovs-vsctl dump-ports because ovs is fine with it, but ODL currently won't be able to store/discover/parse it correctly, and will show the port as a negative number.</p> <p>The problem is that the open flow specification sets 16 bits aside for a port in the headers, and the third party openflowj library also accordingly reads/writes 16 bits on the wire, but java on the other hand, treats all short integers as signed. This is causing issues with the openflowj library and all other parts of the ODL code that deals with open flow ports because those 16 bits are treated as signed ints, not unsigned short ints as they should be.</p> <p>I'm working on the fix for this, and the fix is complicated and will take a while.</p> <p>Regards,<br/> Vijay</p> <p>Any updates on this? </p> <p>Calling TCP/UDP.getSourcePort() for iperf supplied packets very often results in returned negative values. I name iperf since the client does not allow for specifying the source port and instead reserves a random available port thus almost always resulting in problems if port no. needs to be extracted from the packet.</p> <p>This bug is part of the project to Move all ADSAL associated component bugs to ADSAL</p> <p>Deprecated code.</p> Development External issue ID 161 External issue URL Priority Rank 0|i02i2f: