I would like to use your implementation in NS3 for some research in 5G network slicing. In order to achieve this i would like to use an external SDN controller (ONOS is my prefered choice) but i found a critical bug.
I observed using wireshark that OpenFlow LLDP package that was received in the SDN controller (OFPT_PACKET_IN) was truncated previously by the ofswitch13 switches, affecting to the last part of the Data field of the OpenFlow 1.3 package.
It's true that with floodlight controller works, because i imagine that the fields that need to build the topology are correct (since the truncation happens at the end of the package) but ONOS needs this last part of the package and using a simple topology like this:
2 hosts
4 switches
ONOS goes crazy (because the received message indicates for example that Port Description is Port\330g in stead of Port 2).
Below I attached a wireshark capture form ONOS and Floodlight controllers to see clearly what i'm talking about.
Dear @ljerezchaves,
I would like to use your implementation in NS3 for some research in 5G network slicing. In order to achieve this i would like to use an external SDN controller (ONOS is my prefered choice) but i found a critical bug.
I observed using wireshark that OpenFlow LLDP package that was received in the SDN controller (OFPT_PACKET_IN) was truncated previously by the ofswitch13 switches, affecting to the last part of the Data field of the OpenFlow 1.3 package.
It's true that with floodlight controller works, because i imagine that the fields that need to build the topology are correct (since the truncation happens at the end of the package) but ONOS needs this last part of the package and using a simple topology like this:
ONOS goes crazy (because the received message indicates for example that Port Description is Port\330g in stead of Port 2).
Below I attached a wireshark capture form ONOS and Floodlight controllers to see clearly what i'm talking about.
Any idea?
Thanks, Rubén.
wireshark_captures_onos_floodlight.zip