[ovs-dev] [PATCH v2 3/3] datapath: add layer 3 flow/port support

thomas.morin at orange.com thomas.morin at orange.com
Wed May 21 12:38:06 UTC 2014


Hi Jesse,

2014-05-19, Jesse Gross:
[...snip...]
>>> I actually have much less of a problem with including an EtherType
>>> from a GRE tunnel. For one thing it actually exists in the packet
>>> rather than being an artificial namespace. Another thing is that it is
>>> metadata akin to the input port that can't be reproduced from the
>>> packet data since it comes from the tunnel header that has been
>>> stripped off.
>>
>> Ok.
>>
>> So we would settle on preserving the ethertype in OVS_KEY_ATTR_ETHERTYPE
>> for non-Ethernet payloads received over GRE ?
>
> I think what I would probably do is to define a new tunnel attribute
> for EtherType and unconditionally include it when it is part of the
> protocol. This most closely reflects the format of the data and should
> hopefully avoid any quirks with layers or wildcards later on.

Two questions, to make sure we are clear on the type of genericity to 
achieve:
- rules to process a packet depending on its ethertype, and process 
packets possibly coming from Eth ports and GRE ports, would need to be 
duplicated to test the Ethernet ethertype and the tunnel ethertype ?
- what about other link layers than ethernet that may have an ethertype 
? (thinking Infiniband at least for IP and ARP payloads, ATM too,...)

Best,

-Thomas
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.



More information about the dev mailing list