SwOS Lite version 2.18 released!

SwOS Lite version 2.18 released
http://www.mikrotik.com/download

What’s new in v2.18:

*) added option to set forced 2.5G for SFP+ ports;
*) css610: added a distinct “Health” menu;
*) css610pi: updated PoE firmware;
*) fixed multicast forwarding after disabling IGMP snooping;
*) fixed SNMP ifSpeed OID reporting in certain cases;
*) ftc11xg: fixed DHCP packet forwarding;
*) limit the number of displayed GUI “Hosts” entries up to 512;
*) improved SwOS Lite web interface stability and responsiveness;

Glad to see there is still development for this version.

*) added option to set forced 2.5G for SFP+ ports;

How do you set this ?

Never mind, found it. Disable autonegotiation and then you can select.

Follow up:
On CSS610 I set an S+RJ10 to forced 2.5Gb, connected to ether1 of AX3 using VLAN trunk.
Link becomes active. So far so good.
On AX3 log files I see it determines speed as being 2.5Gb, which is ok however …nothing passes (after the facts I can see in log files what happened).
Only when I enable autonegotiation, I can get access via that link.

Am I missing something ?

can we please please please get option 82 in swos lite!

You should probably disable Auto Negotiation and fix it at 2.5Gbps on AX3 ether1 too…

When setting speed fixed on AX3 → No Link on CSS610, both with auto and no autonegotiation.
Also visible on AX3, ether lights go out for that port.

When auto negotiation is disabled you often need a crossover cable. Auto-crossover is often also disabled if auto negotiation is disabled

I understand what you say but I don’t understand why that would be needed… doesn’t make sense from a practical point of view.
Auto MDX is something from the previous century !

Anyhow, SUP-146041 created. Let’s see what support says about it.

Actually I believe onnoossendrijver is correct, modern ethernet controllers use standard IEEE 802.3ab auto negotiation protocol to automatically determine MDI, speed and duplex and for a practical standpoint it makes perfect sense, and once you disable auto negotiation you must use crossover cable…

Got response from support.
Some info provided both from CSS610 and AX3.

In parallel I ordered some CAT6 cross-convertor plugs.
We’ll see …

Final ordeal:
it’s (again) S-RJ10 acting up. It can not be controlled to set lower speed.

Which revision of S-RJ10 are you using? There is a Rev 2
Read about it

It is Rev 2.
That module will adjust on its own to lower speed when needed (e.g. when connected to 2.5G port of AX3) but it can not be configured to do so (e.g. when connecting 2 S-RJ10 to each other and not wanting full 10G because it will burn your fingers).

Yeah they get really hot.
I’ve read that they need to be set at a fixed speed.

Can you try this on RouterOS also if you have CRS somewhere?

Good to see more development, I’m running a few Netpower Lite 7R devices currently at 2.17.
Please consider feature requests for new releases:

  • option to not save all config changes immediately, instead keep them only in RAM, and have a separate “Save” button (this way previous working config can be restored by reboot/power-cycle if you lost access due to wrong change)
  • option to reboot (optionally including power-cycling the PoE powered device) after some number of failures to get IP address by DHCP, to recover from wrong config change or hung uplink radio without power-cycle (tricky to do with reverse-PoE redundant power from multiple customers)

If I go to the hosts screen… after about 20 seconds I get this at the top of the screen.

ERROR: SyntaxError: Unexpected token ‘{’

yup, same here on two css610

I’m not seeing that.
Edge as browser on Win11.

Confirmed on CSS610:
Screenshot_20240319-075916.jpg

O..K …it took a LOT longer then 20 seconds (just left the window open while I was doing something else).
Now I see it as well.