Hi,
Well it's not that I absolutely need the Set-Field with mask but it
looks like it's a solution to what I'm trying to do.
As I wrote before I wanna keep states in the packet header and then
match/set this information.
Therefore I thought that using the vlan field to store this
information and
Hi Clément,
If you really insist on using Set-Field with mask, you should take a look
at Openflow 1.5 and AFAIK the latest version of openvswitch has draft
support of OF1.5 masked Set-Field action. But it's out of scope now because
Ryu does not yet support Openflow 1.5.
2015-02-03 10:29 GMT+08:00
Hi,
On 2015年02月03日 01:45, Clément Rault wrote:
> Hi,
>
> Thanks.
>
> I did manage to use this new functionality yes. But I also need to be
> able to write only in some bits of the vlan field.
>
> Do you think that you will implement the set field instruction of the
> vlan field with mask any ti
Hi,
Thanks.
I did manage to use this new functionality yes. But I also need to be
able to write only in some bits of the vlan field.
Do you think that you will implement the set field instruction of the
vlan field with mask any time soon?
Like it's possible with the metadata field for example.
Hi,Clément
On 2014年12月01日 20:35, Clément Rault wrote:
> Hi,
>
> I'm trying to implement some inband mechanisms and for that I need to
> keep some information about the states of the nodes. Since nothing can
> be stored in the nodes I need to save it in the packet header.
>
> Basically I just wan
Hi,
I'm trying to implement some inband mechanisms and for that I need to
keep some information about the states of the nodes. Since nothing can
be stored in the nodes I need to save it in the packet header.
Basically I just wanna be able to remember which was the last outport
used by any switch.
