On Wed, 16 Jul 2014 09:58:45 +0200 (CEST)
Szymon Mentel <[email protected]> wrote:
> To satisfy my curiosity I've run another tests to see whether it's always
> possible to determine values from ofp_packet_in sent by OVS. Basically, I
> setup OVS to include 0 bytes of the original packet in ofp_packet_in:
> sudo ovs-ofctl -O Openflow1{2,3} add-flow s1
> priority=100,dl_vlan=50,actions=controller\(max_len=0\).
>
> And it still includes only OXM for IN_PORT - so there's no way to determine
> other fields' values. I'm using
> OVS version 1.11.0 and from my point of view it's not behaving correctly (for
> OF 1.3 and 1.2).
I think that it's the correct behavior from the OF spec.
The spec says:
The match field is a set of OXM TLVs containing the pipeline fields
associated with a packet. The pipeline fields values cannot be
determined from the packet data, and include for example the input
port and the metadata value (see 7.2.3.9).
and
The set of OXM TLVs may also optionally include packet header
fields. Most switches should not include those optional fields, to
minimise the size of the packet-in, and therefore the controller
should not depend on their presence and should extract header fields
from the data field.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
