I have recently upgraded my CRS “CRS125-24G-1S-2HnD-IN” from 6.6 to 6.7
I am now no longer able to achieve the speeds i was getting earlier on my LAN. A windows to windows file transfer only achieves 3.5MiB where as i would have usually get nearer 100MiB.
What is the easiest way of getting back to 6.6? the download pages only mention 6.7 now?
This screenshot shows me pushing a file over my gigabit network from a PC on ether2 to a server on ether8. You can see that both have negotiated at 1Gbps , what’s strange is the reported traffic on ether19 as the computer on that is on standby and there should be no traffic going to it.
My setup is pretty much as it is out of the box no queues and only a handful of NAT rules on the Gateway.
Apologies for bumping this a second time but i unplugged the cable from ether19 and the speed shot back up again. Its like the every port is only going as fast as the slowest link? When i did unplug ether19 winbox still reports its rate as 10mb even with it unplugged.
I have receive new 6.8rc1 firmware, from Mikrotik support, but unfortunately I have no time to test it now because December is always busiest month of the year. When I find time I will post new comment about that problem.
I have performed a ‘system reset configuration’ and if I let the router come back up without any settings i can see that the TX traffic on the incorrect port is no longer there. As soon as i try and run my import script or backup to restore my config the error returns and the import script fails with an error.
[admin@MikroTik] > import 68export.rsc
invalid value for argument numbers
[admin@MikroTik] >
I’m afraid I’m fairly new to mikrotik so without the quick set pages working on 6.8rc1 the only way i can get my configuration back means i end up with the error back as well.
To clarify, the issue is being caused by the switch chip behaving as a hub… All traffic coming in any port is being forwarded out all other slaved ports (broadcasts or not). If you have even one 10Mbit link, all links must transmit at that speed.
Only affects hardware switched ports, not bridging ports. Not even a foggy idea how this could have happened.
Update: Quick downgrade to 6.6 fixes the issue. If you’re running production, this looks like the best option so far.