On 2015-02-21, Josh Grosse <j...@jggimi.homeip.net> wrote:
> On 2015-02-16 14:43, Stuart Henderson wrote:
>>
>> Not this particular switch, but there isn't much that can go wrong with
>> statically configured link aggregation like this.
>
> On 2015-02-17 16:49, Adam Thompson wrote:
>>
>>DGS-1100 definitely does not support active LACP negotiation. The
>>"static trunk aggregation" it talks about is, basically, static
>>bonding, or what was once called EtherChannel. Which is exactly what
>>the trunk(4) manpage refers to as "IEEE 802.3ad static link
>>aggregation". You're good to go.
>
> I can confirm, now that I have the switch, that loadbalance doesn't
> work with my implementation, and I'll have to do more testing to determine
> why. I have roundrobin under test now, and it is working well so far.
>
>
Are you clear on exactly what loadbalance does?
A hash of
the protocol header is used to maintain packet ordering.
The hash includes the Ethernet source and destination
address, and, if available, the VLAN tag, and the IP source
and destination address.
In this mode, traffic between two individual IP/MAC addresses on
the same vlan will only use a single port, you need multiple addresses
to see the traffic balanced between multiple ports.
