My unRaid server always worked fine but I moved my physical server to a real rack and I had some issues with connecting to unRaid (without changing anything AFAIK). If I try to connect now to anything with unRaid the loading takes ages and the webui has a packetloss of 60%, I downloaded my diagnostics and found the problem:

 

May  3 02:37:00 Icecrown kernel: br0: received packet on bond0 with own address as source address
May  3 02:37:00 Icecrown kernel: br0: received packet on bond0 with own address as source address
May  3 02:37:00 Icecrown kernel: br0: received packet on bond0 with own address as source address
May  3 02:37:00 Icecrown kernel: br0: received packet on bond0 with own address as source address
May  3 02:37:00 Icecrown kernel: br0: received packet on bond0 with own address as source address
May  3 02:37:06 Icecrown kernel: net_ratelimit: 17 callbacks suppressed

Now according to a post I need to switch boding mode to option (1) instead of (0), but it says :

Quote

this mode requires a network switch with proper setup and support...

 

Which I don't have... I think... I have an HP 2510G and never bothered to set it up properly because I need a serial port

 

this is my current network setup, I use a basic switch. Nothing fancy

 

I have R710 with all 4 ethernet ports plugged into a switch.

 

Can I just change the bonding mode from (0) to (1) and will it work even tho I don't have a proper switch setup? Is there a place where I can find what all the bonding mode's do? (I'm sure if I google all of them I'll find out but was wondering if unRaid has something written about it)

 

Hope I gave enough information with a decent explanation

Edited May 3, 20179 yr by Zero

Set to mode 1 for active backup. No switch required. If unRaid tells you that you need a switch for mode 1 then unRaid is lying to you.

 

 

Modes of bonding :

 

• Mode 0 (balance-rr)
  This mode transmits packets in a sequential order from the first available slave through the last. If two real interfaces are slaves in the bond and two packets arrive destined out of the bonded interface the first will be transmitted on the first slave and the second frame will be transmitted on the second slave. The third packet will be sent on the first and so on. This provides load balancing and fault tolerance.
• Mode 1 (active-backup)
  Mode 1 places one of the interfaces into a backup state and will only make it active if the link is lost by the active interface. Only one slave in the bond is active at an instance of time. A different slave becomes active only when the active slave fails. This mode provides fault tolerance.
• Mode 2 (balance-xor)
  Transmits based on XOR formula. (Source MAC address is XOR’d with destination MAC address) modula slave count. This selects the same slave for each destination MAC address and provides load balancing and fault tolerance.
• Mode 3 (broadcast)
  The broadcast mode transmits everything on all slave interfaces. This mode is least used (only for specific purpose) and provides only fault tolerance.
• Mode 4 (802.3ad)
  The 802.3ad mode is known as Dynamic Link Aggregation mode. It creates aggregation groups that share the same speed and duplex settings. This mode requires a switch that supports IEEE 802.3ad Dynamic link. Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option. Note that not all transmit policies may be 802.3ad compliant, particularly inregards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Differing peer implementations will have varying tolerances for noncompliance.
• Mode 5 (balance-tlb)
  This is called as Adaptive transmit load balancing. The outgoing traffic is distributed according to the current load and queue on each slave interface. Incoming traffic is received by the current slave.
• Mode 6 (balance-alb)
  This is Adaptive load balancing mode. This includes balance-tlb + receive load balancing (rlb) for IPV4 traffic. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the server on their way out and overwrites the src hw address with the unique hw address of one of the slaves in the bond such that different clients use different hw addresses for the server.