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).
----- Oryginalna wiadomość -----
> Od: "FUJITA Tomonori" <[email protected]>
> Do: "szymon mentel" <[email protected]>
> DW: [email protected]
> Wysłane: czwartek, 10 lipiec 2014 1:38:37
> Temat: Re: [Ryu-devel] OXM_OF_VLAN_VID and ofp_packet_in message
>
> On Wed, 9 Jul 2014 11:40:44 +0200 (CEST)
> Szymon Mentel <[email protected]> wrote:
>
> > 7. Then I look at the Wireshark using OF13 dissector and it turns out the
> > there's only
> > OFPXMT_OFB_IN_PORT field in the match.
> >
> > It's the same for OF 1.2. Am I missing something or just OVS doesn't send
> > complete match
> > in the packet_in message?
> >
> > If anyone knows why things are like that, please let me know.
>
> Oops, probably I was wrong. OVS sets only the values that can not be
> determined from the packet data, e.g., in_port, metadata, tunnel_id,
> etc. It's compliant to the spec.
>
------------------------------------------------------------------------------
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
