X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=2aba34fdf4f1840d4db4c3635c2477586832893d;hb=79c9f2ee7883b52860c76c3730725f5731402874;hp=e6ad3872701c17fc98141e0c3d9120e0776aad9e;hpb=a0bc29a541fc7dc6e20137d5558e2094d614e6ab;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index e6ad3872..2aba34fd 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -127,8 +127,8 @@ The currently defined key-value pairs are:
network-uuids
xe network-list
.hwaddr
xx:xx:xx:xx:xx:xx
.bond-rebalance-interval
tap
gre
remote_ip
, local_ip
, and
+ in_key
. Note that if two ports are defined that are
+ the same except one has an optional identifier and the other does
+ not, the more specific one is matched first. in_key
+ is considered more specific than local_ip
if a port
+ defines one and another port defines the other. The arguments
+ are:
+ remote_ip
local_ip
in_key
flow
. If
+ flow
is specified then any key will be accepted
+ and the key will be placed in the tun_id
field
+ for matching in the flow table. The ovs-ofctl manual page
+ contains additional information about matching fields in
+ OpenFlow flows. Default is no key.out_key
flow
. If
+ flow
is specified then the key may be set using
+ the set_tunnel
Nicira OpenFlow vendor extension (0
+ is used in the absense of an action). The ovs-ofctl manual
+ page contains additional information about the Nicira OpenFlow
+ vendor extensions. Default is no key.key
in_key
and
+ out_key
at the same time.tos
inherit
, in which case the ToS will be copied from
+ the inner packet if it is IPv4 or IPv6 (otherwise it will be
+ 0). Note that the ECN fields are always inherited. Default is
+ 0.ttl
inherit
, in which case the
+ TTL will be copied from the inner packet if it is IPv4 or IPv6
+ (otherwise it will be the system default, typically 64).
+ Default is the system default TTL.csum
false
to disable.pmtud
false
to disable.patch
peer
argument is required that indicates the name
+ of the other side of the patch. Since a patch must work in
+ pairs, a second patch interface must be declared with the
+ name
and peer
arguments reversed.