Thanks for your ideas, I tried them and a few changes based on them.
The results were a little bit confusing, but in the end I got it working:
1) I removed all "auto ..." statements for br0, br1, eth0, eth1 - no
interfaces got up.
2) I put the "auto ..." statements back to eth0 and eth1 - all works,
but at 2nd
reboot the bridges again won't come up, no idea why.
3) I removed pre-up and post-down from br0 and br1 - br1 works as
expected, br0 doesn't
The only difference I see, is the up-statement in the last line,
which works on br1.
4) I commented this out - both interfaces won't work
5) I uncommented this up-statement again and added a new up-statement
for default gw on br0 - all works now!
For completeness, here is the working "/etc/network/interfaces":
# ----- Start of "/etc/network/interfaces" ----- #
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#auto br0
allow-ovs br0
iface br0 inet static
address 85.###.###.###
netmask 255.255.255.255
network 85.###.###.###
broadcast 85.###.###.###
gateway 85.###.###.###
mtu 1500
ovs_type OVSBridge
ovs_ports eth0
# pre-up ifconfig $IFACE up
# post-down ifconfig $IFACE down
auto eth0
allow-br0 eth0
iface eth0 inet manual
address 0.0.0.0
ovs_bridge br0
ovs_type OVSPort
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down
up route add default gw 85.###.###.### dev br0
# The secondary network interface
#auto br1
allow-ovs br1
iface br1 inet static
address 10.###.###.###
netmask 255.255.255.0
network 10.###.###.0
broadcast 10.###.###.255
mtu 1500
ovs_type OVSBridge
ovs_ports eth1
# pre-up ifconfig $IFACE up
# post-down ifconfig $IFACE down
auto eth1
allow-br1 eth1
iface eth1 inet manual
address 0.0.0.0
ovs_bridge br1
ovs_type OVSPort
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down
up route add -net 10.48.0.0/16 gw 10.###.###.1 dev br1
# ----- End of "/etc/network/interfaces" -----
I think, the "pre-up ifconfig $IFACE up" statements on the two bridges
just touched them, what was
they need to get up! When I commented them out, the "up route add ..."
entries did the same.
Do you know a more "straight forward" and clean way, to touch the
bridges? - I don't like to start complicated scripts
that aren't really needed, and to add the routes will just hide the real
reason, why they are put in. Maybe on
other machines, one doesn't need routes at all.
Thanks once again. Now I can go on playing with Xen ... ;-)
Greetings,
Berthold Humkamp
Am 17.03.2014 21:16, schrieb Gurucharan Shetty:
> I reproduced your problem.
>
> Remove
> pre-up ifconfig $IFACE up
> post-down ifconfig $IFACE down
You mean in br0 / br1 block? - done!
> Those two does not make much sense for this context.
>
> On Mon, Mar 17, 2014 at 1:03 PM, Gurucharan Shetty <[email protected]> wrote:
>>>> What does "ovs-vsctl show" say?
>>> no bridges or ports, only the version
>> Okay.
>> Now,
>> ovs-vsctl add-br br0
>> followed by:
>> ovs-vsctl show
>> shows the bridge "br0", right?
right!
>> "ifconfig br0" shows the bridge too?
right!
>> If so:
>> /etc/init.d/openvswitch-switch stop
>>
>> "ifconfig br0" does not show the bridge anymore?
right!
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
