I have a CRS-125, and I've seen quite a few
Is there a difference between adding all ports to the local bridge and setting all ports slave to ether1?

I'm essentially looking for a way to turn the switch into a dumb switch.

Hi!
Short answer:

MasterSlave means: use switch chip --> few features, high performance

Bridge means: use router CPU --> many features, low performance

For a dump switch, use master slave.
If you want to filter, use a bridge.

But take into mind, that from next release on (currently RC channel) there will be no more difference...

As of right now.
Master-slave switches on the hardware
Bridge switches through the CPU. I found that throughout was about 400-500mb when switching through the bridge.

Currently in the rc channel there is a new feature where bridge ports will offload switching to hardware, I've tested this and it implements really well and will make a difference to a number for remote sites we currently have set up as bridges.

If you need to depend on this at all I'd wait for it to roll into current channel though as there can be a lot of bugs to work out with is kind of thing.

Hi!
Short answer:
MasterSlave means: use switch chip --> few features, high performance
For a dump switch, use master slave.

How come when I slave all ports to Ether1, and set Ether1 master to "None", I can no longer connect to the switch? Not only that, but I can't pass traffic through the switch either.

There is apparently something in the default configuration of the CRS-125 that keeps you from turning this into a dumb L2 switch. While I don't know exactly what part of the default configuration keeps the brains, I do know I was able to get my dumb switch by resetting the config, and not loading a default configuration. Then I was able to do the Master-Slave setup and everything works hunky-dory now.

Thanks everyone!

Yep - in default config eth1 is WAN interface, thus blocks incoming traffic.

Hi!

That feature sounds interesting!
How is this offloading made? Is it like "fastpath", that it can only affect "non-filtered" sessions, or is it like ACLs in an enterprise-grade Switch?

Regards,
Stril