openvswitch: functionality sanity test
PATCH 1/1 openvswitch: functionality sanity test
Instructions for creating a simple bridge that will take over eth0. You cannot be executing out of an nfs-mounted filesystem while setting up the bridge.
--- docs/vswitch_test.sh | 36 ++++++++++++++++++++++++++++++++++++ 1 files changed, 36 insertions(+), 0 deletions(-) create mode 100755 docs/vswitch_test.sh
docs/vswitch_test.sh new file +36 -0
@@ -0,0 +1,36 @@ +#!/bin/sh + +# runqemu defaults for the first "guest" +# +my_inet4="192.168.7.2" +my_gw="192.168.7.1" + +# create a bridge +# +ovs-vsctl add-br br-int + +# Add a physical interface to your virtual bridge for connectivity off box. +# If your rootfs is nfs mounted (on eth0), you will die after attaching it +# to the bridge. +# +ovs-vsctl add-port br-int eth0 + +# Zero out your eth0 interface and slap it on the bridge interface. +# +ifconfig eth0 0 +ifconfig br-int ${my_inet4} netmask 255.255.255.0 + +# Change your default route. If you don't do this, nothing will +# be reachable. +# +route add default gw ${my_gw} br-int + +(You can then check that the connection works.) + +# The bridge configuration is persistant, so if something goes wrong +# and you reboot, it will still be messed up. Destroy the bridge, +# then add a route, or reboot. +# +ovs-vsctl del-br br-int +ifconfig eth0 ${my_inet4} +route add default gw ${my_gw} eth0
Signature · 1 line
1.7.3.4
Quoted 3 lines · Joe Slater
Instructions for creating a simple bridge that will take over eth0. You cannot be executing out of an nfs-mounted filesystem while setting up the bridge.
Thanks Joe. This looks good. Will you resend the updated ovs version bump as well ? If you reference this script/testing in it's commit log we should be good to go.
Bruce
Quoted 52 lines
Signed-off-by Joe Slater <[email protected]>--- docs/vswitch_test.sh | 36 ++++++++++++++++++++++++++++++++++++ 1 files changed, 36 insertions(+), 0 deletions(-) create mode 100755 docs/vswitch_test.shdocs/vswitch_test.sh new file +36
-1@@ -0,0 +1,36 @@ +#!/bin/sh + +# runqemu defaults for the first "guest" +# +my_inet4="192.168.7.2" +my_gw="192.168.7.1" + +# create a bridge +# +ovs-vsctl add-br br-int + +# Add a physical interface to your virtual bridge for connectivity off box. +# If your rootfs is nfs mounted (on eth0), you will die after attaching it +# to the bridge. +# +ovs-vsctl add-port br-int eth0 + +# Zero out your eth0 interface and slap it on the bridge interface. +# +ifconfig eth0 0 +ifconfig br-int ${my_inet4} netmask 255.255.255.0 + +# Change your default route. If you don't do this, nothing will +# be reachable. +# +route add default gw ${my_gw} br-int + +(You can then check that the connection works.) + +# The bridge configuration is persistant, so if something goes wrong +# and you reboot, it will still be messed up. Destroy the bridge, +# then add a route, or reboot. +# +ovs-vsctl del-br br-int +ifconfig eth0 ${my_inet4} +route add default gw ${my_gw} eth0 --1.7.3.4
Quoted 4 lines
_______________________________________________
meta-virtualization mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-virtualization
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"