$ ovs-ofctl add-flow br0 actions=load:0->NXM_OF_IN_PORT[],2,3,4,5,6
If the input port is important, then one may save and restore it on the
- stack:
+ stack::
$ ovs-ofctl add-flow br0 actions=push:NXM_OF_IN_PORT[],\
load:0->NXM_OF_IN_PORT[],\
A: A policing policy can be configured on an interface to drop packets that
arrive at a higher rate than the configured value. For example, the
following commands will rate-limit traffic that vif1.0 may generate to
- 10Mbps:
+ 10Mbps::
$ ovs-vsctl set interface vif1.0 ingress_policing_rate=10000
$ ovs-vsctl set interface vif1.0 ingress_policing_burst=8000
However, not all "Permission denied" errors are caused by SELinux. So, before
blaming too strict SELinux policy, make sure that indeed SELinux was the one
-that denied OVS access to certain resources, for example, run:
+that denied OVS access to certain resources, for example, run::
$ grep "openvswitch_t" /var/log/audit/audit.log | tail
type=AVC msg=audit(1453235431.640:114671): avc: denied { getopt } for pid=4583 comm="ovs-vswitchd" scontext=system_u:system_r:openvswitch_t:s0 tcontext=system_u:system_r:openvswitch_t:s0 tclass=netlink_generic_socket permissive=0
$ ovs-vsctl add-port br0 tap1
#. Create the GRE tunnel on `host2`, this time using the IP address for
- ``eth0`` on `host1` when specifying the ``remote_ip`` option:
+ ``eth0`` on `host1` when specifying the ``remote_ip`` option::
$ ovs-vsctl add-port br0 gre0 \
-- set interface gre0 type=gre options:remote_ip=<IP of eth0 on host1>
$ rpmbuild -bb rhel/kmod-openvswitch-rhel6.spec
-You might have to specify a kernel version and/or variants, e.g.:
+You might have to specify a kernel version and/or variants, e.g.::
$ rpmbuild -bb \
-D "kversion 2.6.32-131.6.1.el6.x86_64" \
The TSO support may be enabled via a global config value
``userspace-tso-enable``. Setting this to ``true`` enables TSO support for
-all ports.
+all ports.::
$ ovs-vsctl set Open_vSwitch . other_config:userspace-tso-enable=true