X-Git-Url: http://git.onelab.eu/?p=sliver-openvswitch.git;a=blobdiff_plain;f=INSTALL.userspace;h=f54b93e2e54c2efdc88054519038d98390e4183c;hp=241d79cb24afd0ed8bb46a00f6b528fb44d69ac2;hb=HEAD;hpb=58fda1dab104041fc693032475ec4662c1a52849

diff --git a/INSTALL.userspace b/INSTALL.userspace
index 241d79cb2..f54b93e2e 100644
--- a/INSTALL.userspace
+++ b/INSTALL.userspace
@@ -17,7 +17,7 @@ Building and Installing
 -----------------------
 
 The requirements and procedure for building, installing, and
-configuring Open vSwitch are the same as those given in INSTALL.Linux.
+configuring Open vSwitch are the same as those given in INSTALL.
 You may omit configuring, building, and installing the kernel module,
 and the related requirements.
 
@@ -31,31 +31,52 @@ The tun device must also exist as /dev/net/tun.  If it does not exist,
 then create /dev/net (if necessary) with "mkdir /dev/net", then create
 /dev/net/tun with "mknod /dev/net/tun c 10 200".
 
+On FreeBSD and NetBSD, the userspace switch additionally requires the
+kernel tap(4) driver to be available, either built into the kernel or
+loaded as a module.
+
 Using the Userspace Datapath with ovs-vswitchd
 ----------------------------------------------
 
-To use ovs-vswitchd in userspace mode, give the bridge a name that
-begins with "netdev:" in the configuration file.  For example:
+To use ovs-vswitchd in userspace mode, create a bridge with datapath_type
+"netdev" in the configuration database.  For example:
 
-    bridge.netdev:br0.port=eth0
-    bridge.netdev:br0.port=eth1
-    bridge.netdev:br0.port=eth2
+    ovs-vsctl add-br br0
+    ovs-vsctl set bridge br0 datapath_type=netdev
+    ovs-vsctl add-port br0 eth0
+    ovs-vsctl add-port br0 eth1
+    ovs-vsctl add-port br0 eth2
 
 ovs-vswitchd will create a TAP device as the bridge's local interface,
-named the same as the bridge minus the "netdev:" prefix, as well as
-for each configured internal interface.
+named the same as the bridge, as well as for each configured internal
+interface.
+
+Currently, on FreeBSD, the functionality required for in-band control
+support is not implemented.  To avoid related errors, you can disable
+the in-band support with the following command.
+
+    ovs-vsctl set bridge br0 other_config:disable-in-band=true
+
+Firewall Rules
+--------------
+
+On Linux, when a physical interface is in use by the userspace
+datapath, packets received on the interface still also pass into the
+kernel TCP/IP stack.  This can cause surprising and incorrect
+behavior.  You can use "iptables" to avoid this behavior, by using it
+to drop received packets.  For example, to drop packets received on
+eth0:
 
-Using the Userspace Datapath with ovs-openflowd
------------------------------------------------
+    iptables -A INPUT -i eth0 -j DROP
+    iptables -A FORWARD -i eth0 -j DROP
 
-To use ovs-openflowd in userspace mode, specify a datapath name that
-begins with "netdev:", and specify --ports with the names of the ports
-that should be included in the datapath as argument.  For example:
+Other settings
+--------------
 
-    ovs-openflowd netdev:br0 --ports=eth0,eth1,eth2
+On NetBSD, depending on your network topology and applications, the
+following configuration might help.  See sysctl(7).
 
-ovs-openflowd will create a TAP device as the bridge's local
-interface, named the same as the bridge minus the "netdev:" prefix.
+	sysctl net.inet.ip.checkinterface=1
 
 Bug Reporting
 -------------