I ended up using firewall rules to collect the numbers, then the API to extract the data. Works well enough for what I needed. On average, inbound IPv6 accounts for 19.6% of my total traffic over the last 5 days. On any single day it can be as high as 40%. On 10 April 2015 at 20:41, Terry Sweetser <terry+mikrotik@skymesh.net.au> wrote:
You will also need connection tracking turned on for both ip and ipv6 to get netflow.
You could also set up queues to track ipv4 and ipv6 separately and graph them?
http://about.me/terry.sweetser
------------------------------------------------------------------------
*From:* Bob Purdon <mailto:%3Ca%3Ebobp@purdon.id.au%3C/a%3E> *Sent:* Saturday, April 04, 2015 6:03PM *To:* Mikrotik Australia Public List <mailto:%3Ca%3Epublic@talk. mikrotik.com.au%3C/a%3E> *Subject:* Re: [MT-AU Public] Graphing IPv4 vs IPv6 traffic
Interesting - will check this out. As I only saw the "Traffic flow" item
under IPv4 in the Mikrotik web interface, I wrongly assumed it would only export IPv4 flows..
Using the HTTP API to collect firewall rule counters also seems like a workable approach (not as ugly as ssh'ing into the router ever 5 mins :-) ).
I'm sure one of those approaches will get me to where I want to go :-)
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au