You should probably disable Auto Negotiation and fix it at 2.5Gbps on AX3 ether1 too...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 ?
When setting speed fixed on AX3 -> No Link on CSS610, both with auto and no autonegotiation.You should probably disable Auto Negotiation and fix it at 2.5Gbps on AX3 ether1 too...
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...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.
Confirmed on CSS610:If I go to the hosts screen... after about 20 seconds I get this at the top of the screen.
ERROR: SyntaxError: Unexpected token '{'
O..K ...it took a LOT longer then 20 seconds (just left the window open while I was doing something else).I'm not seeing that.
Edge as browser on Win11.
Your device is a dumb power consuming nothing without SwOS. So don't talk BS. And Mikrotik won't open source SwOS anyways. It wouldn't help you either way, as bugs are not fixed by just the action of publishing the source code.Most of the value is in the hardware anyway, few companies make outdoor reverse-PoE switches.
Fingers crossed...We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming SwOS lite versions, unfortunately, I cannot provide a release date now.