-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual stack collectors and data sources #117
Comments
I'd love to see this happen, too, as I have an ipv6 only network, I primarily need ipv6 metrics. @akpw thank you so much for implementing this exporter and documenting it so well! I came to you, because Mikrotik doesn't seem to have any interest in adding ipv6 monitoring stuff to the existing SNMP support. There is no support for ipv6 BGP neighbors and lot's of other things missing, that you already include. So expanding mtkxp seems to be the best route. Addding conneciton support to ipv6 only routers and ipv6 route statistics are my biggest pain points as of now. Thanks again! |
Hello @akpw I hope you are well!! I agree that IPV6 metrics would be best In my opinion, BGP IPV6 would be good From now on, more than grateful for the good work you do! |
@savitarMK OK that sounds good. adding dual stack is easy by itself, though the real life testing might indeed be needed |
added initial dual stack for route and few others, feel free to test out and let me know. |
Thanks for that @akpw , working great for "simple"access routers with small amount of ipv6 prefixes. On my backbone routers however, I can't currently use the route feature.
Also it takes too long and times out. Since you know your code much better than me: is it easy for you to just fetch router counts by for example:
That would only return the number of prefixes, not every single detail, which won't be used after all. Thanks in advance, Johannes |
@irrwitzer42 right though unfortunately fetching conditional counts is not as straightforward with the current version of routeros-api library. fyi, I asked a related question there for now, I did some quick optimisations that might help as well, so feel free to try with the latest |
@akpw Thank you so much for trying to implement this approach! I tried your updated code for one of my backbone routers, but it doesn't help much in my case. For now, thank you again for this great exporter and your very quick response to this feature request! BR, Here's the current log by the way:
|
+pool |
Hi,
First of all, this is an amazing piece of software. @akpw, thank you very much for your effort!
I suggest we could implement dual stack collectors and data sources, so that both IPv4 and IPv6 metrics could be collected.
Below is a list of most evident places in the code where only IPv4 data are collected and IPv6 data are ignored:
mktxp/mktxp/datasource/connection_ds.py
Line 27 in f70719d
mktxp/mktxp/datasource/connection_ds.py
Line 47 in f70719d
mktxp/mktxp/datasource/dhcp_ds.py
Lines 31 to 33 in f70719d
mktxp/mktxp/datasource/pool_ds.py
Line 26 in f70719d
mktxp/mktxp/datasource/pool_ds.py
Line 41 in f70719d
mktxp/mktxp/collector/public_ip_collector.py
Line 26 in f70719d
mktxp/mktxp/datasource/route_ds.py
Line 26 in f70719d
Regards,
The text was updated successfully, but these errors were encountered: