Hi,

I'm testing with Traffic Flow, and if I'm using IPFIX and then switch to V9, the stream still includes IPFIX packets as well as V9 packets until after I reboot the device. I'm also noting a length error in the V9 packets. I'm still researching.

Larry

The beauty of using CURL, is that you don't have to figure too much out. Okay, I'm getting stats now. Just to parse is all. I can figure that much out.

Hi, The SwOS has some real good stats that can be delivered over a Digest Authorization with URI, but in testing, I'm having issue getting the Digest Authorization to work. Are there any requirements we should know about, for example, any requirements (say for example on the length and format of the...

Hey, this is a big shit post, but interesting reading. I for one prefer stability. Yea the GUI is getting a bit dated, but you have to think of it this way. Mikrotik is such a big tool, rewriting to match something the "U" company has done is no small task. And I for one, though an OSS dev...

Funny, which vendor? I like the Mikrotik even with this tiny bug.

I'd like to jump in here as well. Right now, you have to approximate using the flow receipt time, which is not accurate. It should be fairly strait forward to add this as you are setting it already in the header of both the v5 and v9 streams. So, it's basically copy and paste into the IPFIX template...

I've just purchased 2 SwOS 5 port devices. It's a great little 5 port managed switch for my small home office. I'm monitoring it using SNMP, but unlike the RouterOS (which I also have two), the Mikrotik MIB is not present. It appears to only support the standard interface table, the standard system ...