I am going to be moving all Layer-3 off of my CRS-125 and using it as a pure switch. I see the states indicate full line speed switching across ports when used as a switch vs. bridged. Can I run SwOS on a CRS-125 (I don't see an image for it in the d/l section), and if not, how can I ensure it is in switch mode across all ports?

SwOS isn't available for the CRS125.

To ensure it's in switch mode simply create a single bridge and have all ports (interfaces) as members of that bridge.

edit - I forgot mention you need to be running 6.41 or higher I think for that to work.

thanks - we are on the latest ( 6.43.8 ) so that shouldn't be a problem.

So you are saying that all I have to really do to move the CRS125 to be a hw-switch (right now, it is acting as a super simple AP router) is to move ether1 (WAN) into the main bridge (where all other interfaces are)?

Better yet, if I want to run it purely as a managed switch AND NOTHING ELSE, I should just revert to factory defaults and use QuickSet "WISP AP" with mode = Bridge?

A reset should do it for you. Quickset as WISP AP and make sure Bridge All LAN Ports is ticked.

A reset should do it for you. Quickset as WISP AP and make sure Bridge All LAN Ports is ticked.

Thanks! Do you know if this configuration on the CRS125 will hw offload switching for the wlan1 wireless interface?

I'm open to correction on this but I'm pretty sure there is no hardware offload for the wlan interface.

At least not on mine:

# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
0 H ether1 LAB yes 1 0x80 10 10 none
1 I H ether2 LAB yes 1 0x80 10 10 none
2 I H ether3 LAB yes 1 0x80 10 10 none
3 I H ether4 LAB yes 1 0x80 10 10 none
4 I H ether5 LAB yes 1 0x80 10 10 none
5 I H ether6 LAB yes 1 0x80 10 10 none
6 I H ether7 LAB yes 1 0x80 10 10 none
7 I H ether8 LAB yes 1 0x80 10 10 none
8 I H ether9 DEVNET yes 1 0x80 10 10 none
9 I H ether10 DEVNET yes 1 0x80 10 10 none
10 I H ether11 DEVNET yes 1 0x80 10 10 none
11 I H ether12 DEVNET yes 1 0x80 10 10 none
12 I H ether13 DEVNET yes 1 0x80 10 10 none
13 I H ether14 DEVNET yes 1 0x80 10 10 none
14 H ether15 DEVNET yes 1 0x80 10 10 none
15 I H ether16 DEVNET yes 1 0x80 10 10 none
16 I H ether17 CORENET yes 1 0x80 10 10 none
17 I H ether18 CORENET yes 1 0x80 10 10 none
18 I H ether19 CORENET yes 1 0x80 10 10 none
19 I H ether20 CORENET yes 1 0x80 10 10 none
20 I H ether21 CORENET yes 1 0x80 10 10 none
21 I H ether22 CORENET yes 1 0x80 10 10 none
22 I H ether23 CORENET yes 1 0x80 10 10 none
23 I H ether24 CORENET yes 1 0x80 10 10 none
24 I wlan1 DEVNET 1 0x80 10 10 none
25 H sfp1 CORENET yes 1 0x80 10 10 none

as the wifi interface is NOT on the same switch-chip as the eth ports, wifi will never have hardware-accelleration.
wifi will allways pass thru the cpu and is limited by the cpu performance