Uploaded image for project: 'OpenFlowPlugin'
  1. OpenFlowPlugin
  2. OPNFLWPLUG-72

Packet out does not contain buffer id corresponding to the buffer id of the respective packet in.

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Resolution: Won't Do
    • None
    • None
    • General
    • None
    • Operating System: Windows
      Platform: PC

    Description

      Test Case:
      =========
      -> Connect two switches with 2 hosts attached to the controller
      ->Install flow in the switches to punt the arp packet to the controller with max length as 40.

      {table="0", match="oxm

      {eth_type="0x806"}

      ", dur_s="9", dur_ns="364000", prio="2", idle_to="1000", hard_to="1200", cookie="0x1", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out

      {port="ctrl", mlen="40"}

      ]}]}]}

      -> Ping from host1 to host2.

      The switch is sending packet-in with buffer id set to a value. The corresponding packet-out containing the payload of packet-in has buffer id set to OFP_NO_BUFFER instead of the actual value from the packet-in.

      The packet capture is attached.

      Another issue is that here the packet is malformed due to the insufficient size of the packet with no proper header. In this case should the controller send it out on an output port or simply ignore?

      Thanks,
      Sindhuri.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            dbandyop@cisco.com Debolina Bandyopadhyay
            sindhuri.b@ericsson.com Sindhuri B
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: