same here. Link Aggregation 802.3ag doesnt work (netowork wasnt found) other modes are very unstable. Same switch, same server with VM ESXi4 works perfect.
Regards Valle.
bond0 works only in round-robin. BUG?
- Thread starter valshare
- Start date
same here. Link Aggregation 802.3ag doesnt work (netowork wasnt found) other modes are very unstable. Same switch, same server with VM ESXi4 works perfect.
Regards Valle.
Yes, the server was a netinstall debian lenny and it was working like a charm.
I've used the bare-metal CD installer when I've moved to OpenVZ.
valshare: thanks so I'm not alone! Also tried ESXi but too resources intensive.
On the server's screen I've a lot (lot) of this message:
Here is the ifconfig output:
Last edited:
Hello Dietmar,
today i have tested again with Link Aggregation 802.3ad.
I have working it now with the parameter bridge_stp on. But now i have the problem, if a change anything over the web interface, that i can´t connect to my server. Is there a way, that i can setup the bridge_stp on as a default parameter and that is not changed if i change anything over the web interface?!
Regards, Valle
today i have tested again with Link Aggregation 802.3ad.
I have working it now with the parameter bridge_stp on. But now i have the problem, if a change anything over the web interface, that i can´t connect to my server. Is there a way, that i can setup the bridge_stp on as a default parameter and that is not changed if i change anything over the web interface?!
Regards, Valle
Last edited:
i have checked it today .... sorry, bridge_stp off will set only, if i create a news bridge. The "Patch" shows me
@@ -35,6 +33,12 @@
bridge_stp off
but this isn´t vmbr0, right?!
In the "interfaces.new" are all ok.
@@ -35,6 +33,12 @@
bridge_stp off
but this isn´t vmbr0, right?!
In the "interfaces.new" are all ok.
Code:
auto bond0
-iface bond0 inet static
- address 192.168.1.3
- netmask 255.255.255.0
- slaves eth0 eth1 eth2 eth3
+iface bond0 inet manual
+ slaves none
bond_miimon 100
- bond_mode 802.3ad
+ bond_mode balance-rr
auto vmbr0
iface vmbr0 inet static
- address 192.168.1.3
+ address 192.168.1.5
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports bond0
@@ -35,6 +33,12 @@
bridge_stp off
bridge_fd 0
+auto vmbr2
+iface vmbr2 inet manual
+ bridge_ports none
+ bridge_stp off
+ bridge_fd 0Sorry, I don't get the question?
we set "bridge_stp off" by default. But you can change that manually by editing /etc/network/interfaces[.new] afterwards.
we set "bridge_stp off" by default. But you can change that manually by editing /etc/network/interfaces[.new] afterwards.
Hi,
Hope I didn't hi-jack this old thread.
I was jsut glad to see I'm not alone on this one. I've been struggling to configure load balancing, and I also got those bond0: received packet with own address as source address. I've tried setting the bond_mode to balance-rr, balance-alb, balance-tlb, balance-xor but they only result in unstable connections. I also tried setting bridge_stp to on but that didn't do anything. The switch is a D-Link DGS-3024 which seems to handle load balancing with the servers running Windows, so it sounds reasonable that it's either a Debian issue or maybe Linux kernel issue.
Any sight of a solution?
Hope I didn't hi-jack this old thread.
I was jsut glad to see I'm not alone on this one. I've been struggling to configure load balancing, and I also got those bond0: received packet with own address as source address. I've tried setting the bond_mode to balance-rr, balance-alb, balance-tlb, balance-xor but they only result in unstable connections. I also tried setting bridge_stp to on but that didn't do anything. The switch is a D-Link DGS-3024 which seems to handle load balancing with the servers running Windows, so it sounds reasonable that it's either a Debian issue or maybe Linux kernel issue.
Any sight of a solution?