diff options
| author | Ben Pfaff <blp@nicira.com> | 2012-09-20 08:40:29 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@nicira.com> | 2012-09-20 08:40:29 -0700 |
| commit | c6100d92142bc3dd325180cb4e10553eb4341731 (patch) | |
| tree | d03b58dd371880d8fda4785f4cc1bb3100f412e5 /NEWS | |
| parent | 2ac3c572267c550302eee88d4f584b3694d88f88 (diff) | |
ovs-ofctl: Accept port keywords, OF1.1 port numbers, reject port number 0.
OpenFlow 1.0 has special reserved ports in the range 0xfff8 to 0xffff.
OpenFlow 1.1 and later has the same ports in the range 0xfffffff8 to
0xffffffff and allows the OF1.0 range to be used for ordinary ("physical")
switch ports. This means that, naively, the meaning of a port number in
the range 0xfff8 to 0xffff given on the ovs-ofctl command line depends on
the protocol in use. This commit implements something a little smarter:
- Accept keyword names (e.g. LOCAL) for special reserved ports
everywhere that such a port can plausibly be used (previously they
were only accepted in some places).
- Translate 0xfff8...0xffff to 0xfffffff8...0xffffffff for now, since
OF1.1+ isn't in widespread use and those particular ports aren't
likely to be in use in OF1.1+ anyway.
- Log warnings about those ports when they are specified by number, to
allow users to fix their invocations.
Also:
- Accept the OF1.1+ port numbers for these ports, without warning, for
compatibility with the upcoming OF1.1+ support.
- Stop accepting port number 0, which has never been a valid port
number in OpenFlow 1.0 and later. (This required fixing some tests
that inadvertently used this port number).
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -9,6 +9,14 @@ post-v1.8.0 - OpenFlow: - Allow bitwise masking for SHA and THA fields in ARP, SLL and TLL fields in IPv6 neighbor discovery messages, and IPv6 flow label. + - ovs-ofctl: + - Commands and actions that accept port numbers now also accept keywords + that represent those ports (such as LOCAL, NONE, and ALL). This is + also the recommended way to specify these ports, for compatibility + with OpenFlow 1.1 and later (which use the OpenFlow 1.0 numbers + for these ports for different purposes). + - Commands and actions that accept port numbers no longer accept port 0, + which is not a valid port number in OpenFlow 1.0 and later. - ovs-dpctl: - Support requesting the port number with the "port_no" option in the "add-if" command. |