Hi all, I have a CRS125-24G-1S-2HnD-IN running v6.38.1 with routerboard firmware 3.33.
My setup is pretty basic, ether1 is WAN port and all other ports are bridged together as LAN (ether2 is master). I want to mirror all ports on the LAN bridge to a port (e.g. ether24) for monitoring. As far as I can tell I need to remove ether24 from the bridge and then configure each port mirror individually via the command line, e.g.:
/interface ethernet switch
set ingress-mirror0=ether24 egress-mirror0=ether24
/interface ethernet switch port
set ether2 ingress-mirror-to=mirror0 egress-mirror-to=mirror0
set ether3 ingress-mirror-to=mirror0 egress-mirror-to=mirror0
set ether4 ingress-mirror-to=mirror0 egress-mirror-to=mirror0
...
set ether23 ingress-mirror-to=mirror0 egress-mirror-to=mirror0
I executed those commands but am not seeing mirrored traffic on my ether24 port as expected. I’m only seeing broadcast traffic from the switch group that it is a member of. if/when i make master port=none for ether24 I see no traffic.
I’ve also simplified the configuration so only a single port (ether4) sends ingress/egress traffic to mirror0.
This is a default configuration of my cloud router switch. However, just to be clear are there any other prerequisites for mirroring to work? e.g. change ether24 from network port to switch port? something like that?
I send the mirror port to a promiscuous vswitch in VMware, where I have several virtual machines analyzing packets using different tools. I will be using tcpdump/tshark, Wireshark, packet beats, ntop, and possibly some others.
I can tell there is no traffic flowing to the VM by two ways:
the mikrotik interface statistics pages show a low amount of Kbps and packets per second on the destination interface. The amount is identical to other interfaces on the same switch/bridge in mikrotik
running tcpdump on one of my VMs shows only broadcast traffic is being sent to the ether24interface (presumably because it is on same switch/bridge group)
I can’t be the only one using a CRS that wants to mirror so I assume I must be missing something implied (but not stated) in the wiki page I mentioned.
I was finally able to partially resolve this error and I wanted to reply to my own post so others could benefit.
Mikrotik support assisted me over the course of several weeks and were unable to reproduce my problem. We tried several different configurations that did not improve matters; my port mirror would always work for somewhere between a few seconds and 2 minutes and then stop working entirely until the next reboot.
In the end, the solution proposed by mikrotik support was to move my egress/ingress mirror port over to ether8 instead of ether24. No other changes were made but for whatever reason that was sufficient to resolve the problem and get a port mirror working consistently, and it has been working flawlessly for about a week now.
I am running RouterOS “v6.39rc25 (testing)” as directed by mikrotik support, and routerboard firmware 3.33 (on firmware type ar9344). During the testing process, I changed these software/firmware revisions, reset the configuration with no defaults, etc and nothing worked until i switched the mirror0 destination to be ether8 instead of ether24
I say “partially resolve” above because mikrotik support was unable to reproduce the problem and did not resolve the problem with ether24 so in my opinion that is a clear indication something is still wrong. Hopefully they will continue to work on this issue so no one else encounters it.