Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a RouterOS box set up to bridge two ethernet connections. I have use-ip-firewall=yes in the bridge configuration, so that the ports go through the firewall.

I've enabled netflow reporting via ip/traffic-flow, but the only packets I see reported are broadcast and multicast packets, not the packets that are flowing through the bridge. The documentation indicates that traffic flow logging happens after firewall processing and that it won't work with bridged connections by default, but I would have thought that use-ip-firewall=yes ought to address this.

Is it possible to make this work somehow?

share|improve this question

I think the basis for their NetFlow support is centered on open source technologies. We tried to configure Mikrotik NetFlow with Scrutinizer NetFlow & sFlow Analyzer and it wasn't possible at that time, which was about a year ago. If things have changed with their NetFlow support since then, we would certainly be willing to run more tests. Please send us a packet capture, if we can be of any help.

share|improve this answer
I've got it set up to pipe into flowd, but AFAICT it's nothing to do with the collector. I believe the data just isn't being sent out from the router -- I get the multicast and broadcast packets OK, which makes me think that flowd is set up perfectly well. – Tim Sep 21 '10 at 14:48

IP firewalled bridges will only monitor flows for packets crossing your bridge, meaning that any connection between machines located in the same side of your bridge won't be shown in NetFlow as packets never reach your router.

If you ping a node located in the remote side of the bridge, you should be able to monitor in "/ip firewall connections" both broadcast ARP packets requesting the remote node IP, and then the established ICMP connections, this time crossing your router.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.