-v1.4.0 - xx xxx xxxx
+v1.5.0 - xx xxx xxxx
------------------------
+ - OpenFlow:
+ - Added support for querying, modifying, and deleting flows
+ based on flow cookie when using NXM.
+ - Added new NXM_PACKET_IN format.
+ - ovs-ofctl:
+ - Added daemonization support to the monitor and snoop commands.
+ - ovs-vsctl:
+ - The "find" command supports new set relational operators
+ {=}, {!=}, {<}, {>}, {<=}, and {>=}.
+ - ovsdb-tool now uses the typical database and schema installation
+ directories as defaults.
+ - The default MAC learning timeout has been increased from 60 seconds
+ to 300 seconds. The MAC learning timeout is now configurable.
+
+
+v1.4.0 - 30 Jan 2012
+------------------------
+ - Compatible with Open vSwitch kernel module included in Linux 3.3.
- New "VLAN splinters" feature to work around buggy device drivers
in old Linux versions. (This feature is deprecated. When
broken device drivers are no longer in widespread use, we will
now be properly mirrored for any flows, regardless of their
actions.
- Track packet and byte statistics sent on mirrors.
+ - The sFlow implementation can now usually infer the correct agent
+ device instead of having to be told explicitly.
- ovs-appctl:
- New "fdb/flush" command to flush bridge's MAC learning table.
- ovs-test:
and connectivity issues. This tool currently is not included in RH or
Xen packages.
- RHEL packaging now supports integration with Red Hat network scripts.
+ - bonding:
+ - Post 1.4.*, OVS will be changing the default bond mode from balance-slb
+ to active-backup. SLB bonds carry significant risks with them
+ (documented vswitchd/INTERNALS) which we want to prevent unsuspecting
+ users from running into. Users are advised to update any scripts or
+ configuration which may be negatively impacted by explicitly setting
+ the bond mode which they want to use.
-v1.3.0 - xx xxx xxxx
+v1.3.0 - 09 Dec 2011
------------------------
- OpenFlow:
- Added an OpenFlow extension which allows the "output" action to accept
via "ip_frag" in ovs-ofctl).
- New ovs-ofctl "get-frags" and "set-frags" commands to get and set
fragment handling policy.
- - CAPWAP tunneling now supports an extension to transport a 64-key. By
- default it remains compatible with the old version and other
+ - CAPWAP tunneling now supports an extension to transport a 64-bit key.
+ By default it remains compatible with the old version and other
standards-based implementations.
- Flow setups are now processed in a round-robin manner across ports
to prevent any single client from monopolizing the CPU and conducting