sfp - fixed sfp-ignore-rx-loss parameter for hEX PoE;
To upgrade, click Check For Updates under System/Packages menu and select the stable Channel in RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
Everything went smoothly
I encountered an issue after the update (please post about the device, configuration, and unexpected symptoms)
I encountered an issue, but solved it (please post the solution)
0voters
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. The file must be generated while a router is not working as suspected or after some problem has appeared on the device
Please keep this forum topic strictly related to this particular RouterOS release.
I’m having some headache with the ‘invalid’ ip filter matcher, it seems to catch as invalid what before was ok.
I’m not sure what specific version started the problem, I noticed it this morning in 7.21.2 and I tryied 7.21.3 but it’s the same.
The temp workaround is a rule to allow traffic routed between local subnets before hitting the block:
allow established,related
drop invalid
If I disable the ‘drop invalid’ → all works (but it was ok some versions ago)
To be more clear: all the connections to the internet coming from different local vlans/subnets work ok, incoming connection as well .. it’s just the traffic routed between local subnet that is hitting the ‘invalid’ rule (it seems not consistently, hit and miss).
In this box there is a quite complex config, and I know it might be some layer8 problem, but this conf has been working fine for years (with little updates and adjustments every now and then).
Just be aware that there might be something different in how the ‘invalid’ matcher works, tell me if someone experience something related.
Thanks.
I remember something like you mentioned…
You certainly are using interface-list, even then it is happening?
I have a guess…
Several moves related to VRF are appearing in 7.22.
And they are appearing slowly since a while.
MAYBE… Maybe some moves related to that are affecting that functionality you mentioned.
First time i have ever had an issue after an update.
Just did this update on a CRS309 and its now just sat there with blue PWR light light illuminated, its dead to the world none of the SFP interfaces show any life.
Can you elaborate into more details the "the traffic routed between local subnet" part?
The thing is that if there is possibility for traffic to bypass your firewall in one direction (because there is either L2 connectivity or there is a more direct L3 path, available in one direction), then connection state (in firewall's view) will become invalid because it isn't able to "see" all traffic in both directions.
You’re right. I have been too naive because I was busy moving and renumbering a test k8s cluster. Torch fooled me (I’m more comfortable with *shark), and I came to the wrong conclusion.
Thanks
Interface Queue only-hardware-queue is still mandatory for full FastPath? Using any other Queue (also only-hardware-queue). fp-tx-byte and fp-tx-packet stays always to 0. [SUP-208088]
Hello,
Enabling IGMP-snooping on the bridge also disables hw offload on AR8327 configured with switch-based VLANs on RB450Gx4. The VLAN filtering on the bridge is off, and I've only had VLANs configured on it for the fist time in version 7.20.
