AVM, Fritz!Repeater 2400, firmware 7.50 (latest version available today). I have two of those.
it's difficult to guess from outside what these consumer Mesh devices are making use of to avoid any kind of issues like multiple paths, network loops (lack of an stp or rstp (and not talking of mstp) implementation. Fighting windmills I'd say - and very likely unrelated to the GS105E. The consumer network manufacturers need to learn and document. I would prefer you are going to challenge AVM about this - while I know the XS708T has everything on board you need for a business class L2 network. Still, it's unknown what is configured there.
AVM, Fritz!Repeater 2400, firmware 7.50 (latest version available today). I have two of those.
...
As a test, I temporarily plugged the repeater into an XS708T directly. Now, I do not get any dup responses. Should have tried that earlier. 😕
With this, and not really understanding what's going on, I'll replace the 105E with some small managed switch.
Where was the repeater - technically a Mesh device connecting multiple networks - connected before?
It's difficult to guess from outside what these consumer Mesh devices are making use of to avoid any kind of issues like multiple paths, network loops (lack of an stp or rstp (and not talking of mstp) implementation. And knowing the consumer product designers avoid reliable and standard compliant solutions....
Fighting windmills I'd say, trial and error - and very likely unrelated to the GS105E. The consumer network manufacturers need to learn and document things much better.
I would prefer you are going to challenge AVM about this - while I know the XS708T has everything on board you need for a business class L2 network.
Still, it's unknown what is configured on the XS708T, how things are connected to the rest of the network.
With this, and not really understanding what's going on, I'll replace the 105E with some small managed switch.
I'm not convinced you do yourself a favor looking for a "small managed switch" here - whatever product you have in mind now. already a switch with a simple loop prevention (sending out some frames to all network ports and decide based on what is coming back) could already lead to even more random results.
Most consumer mesh look great on paper. The reality is often following quick if more complex configurations than what the vendor has in mind are enabled.
