Show Posts
1
General Discussion / Re: LAGG - Failover with different switches
« on: September 19, 2024, 08:36:48 am »
Thank you for the quick response. I hoped that OPNsense can bond the interfaces in a virtual switch. Indeed MLAG would be the best solution, but unfortunately the switches are from different vendors (Dell and FS respectively) and MLAG is therefore not an option.
The ports of the switches are indeed not configured as edge ports, so I'll tackle this first. Nevertheless, I was under the impression that the "failover" LAGG works by actively refusing (or appearing as "dead") on the port that is not primary. The interface is indeed active, although I don't know whether it's accepting packets or not.
EDIT: It seems that putting the ports of the switches where OPNSense connects in edge mode solved the problem, apparently. Thank you for your help - I'll reach back if the problem continues, at least now I'm on the right track.
EDIT2: The problem was very silly. In the end, the problem was that I've migrated an old router to this one, and the old router was still active at the same IP address, and was poisoning the ARP cache of the switches. It now works. Strangely, only Windows and Apple clients were affected, while Android (and Linux) worked correctly.
The ports of the switches are indeed not configured as edge ports, so I'll tackle this first. Nevertheless, I was under the impression that the "failover" LAGG works by actively refusing (or appearing as "dead") on the port that is not primary. The interface is indeed active, although I don't know whether it's accepting packets or not.
EDIT: It seems that putting the ports of the switches where OPNSense connects in edge mode solved the problem, apparently. Thank you for your help - I'll reach back if the problem continues, at least now I'm on the right track.
EDIT2: The problem was very silly. In the end, the problem was that I've migrated an old router to this one, and the old router was still active at the same IP address, and was poisoning the ARP cache of the switches. It now works. Strangely, only Windows and Apple clients were affected, while Android (and Linux) worked correctly.