Thank you Ben. Taking another look at the specs for 1.3.0, I see you are right. I somehow missed this sentence about set-field: "The value of oxm_hasmask must be zero and no oxm_mask is included."
On Mon, Oct 21, 2013 at 11:10 PM, Ben Pfaff <b...@nicira.com> wrote: > On Mon, Oct 21, 2013 at 11:05:37PM +0200, Marco Canini wrote: >> Imagine I want to have a rule that for every matching packet modifies >> just the first byte of the dst ETH address and leaves the rest as is. >> Can I do this in OpenFlow? >> Since version 1.2, set-field uses OXM field value+mask types. However, >> reading from the specs, I am not clear whether the combination of >> set-field and an OXM field value+mask allows for fine-grained >> modifications of header fields. > > I don't think you can do this with standardized OpenFlow. The > set-field action always sets the whole field > > The Open vSwitch NXAST_REG_LOAD action can modify part of a field, so > you can do this with Open vSwitch. _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
