You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting on OpenFlow 1.2, many matching fields started to support the usage of field value + mask (sometimes called Bitwise match). In other words, specific bits in the field must have specified values; for example, only source IP addresses in a particular subnet (e.g., nw_src=10.1.0.0/255.255.0.0 means that the OF rule will match 10.1.0.1 and also 10.1.24.252, etc).
The VLAN_id field supports Mask and that can be used to define matches for "VLAN range". Accordingly, instead of having N OpenFlow rules for matching N vlans, range matches can be expressed as a collection of bitwise matches and end up with Z<=N flows (Z tends to be much lower than N, but the worst case they will be equal). For example, let's say that you want to create EVCs for VLANs from 1000 to 1023, the standard way of doing so is by creating 24 rules with matches including:
vlan_id=1000,
vlan_id=1001,
...
vlan_id=1023,
However, using bitwise matches, you can define this with only 2 flows:
vlan_id=0x03e8/0xfff8
vlan_id=0x03f0/0xfff0
The text was updated successfully, but these errors were encountered:
Starting on OpenFlow 1.2, many matching fields started to support the usage of field value + mask (sometimes called Bitwise match). In other words, specific bits in the field must have specified values; for example, only source IP addresses in a particular subnet (e.g., nw_src=10.1.0.0/255.255.0.0 means that the OF rule will match 10.1.0.1 and also 10.1.24.252, etc).
The VLAN_id field supports Mask and that can be used to define matches for "VLAN range". Accordingly, instead of having N OpenFlow rules for matching N vlans, range matches can be expressed as a collection of bitwise matches and end up with Z<=N flows (Z tends to be much lower than N, but the worst case they will be equal). For example, let's say that you want to create EVCs for VLANs from 1000 to 1023, the standard way of doing so is by creating 24 rules with matches including:
vlan_id=1000,
vlan_id=1001,
...
vlan_id=1023,
However, using bitwise matches, you can define this with only 2 flows:
vlan_id=0x03e8/0xfff8
vlan_id=0x03f0/0xfff0
The text was updated successfully, but these errors were encountered: