New on RIPE Labs: New Text Service for RIPEstat
Dear colleagues, RIPEstat is now also available as a text-based interface for users who prefer a command-line interface (CLI) and those interested in including RIPEstat data in shell scripting. Please find more information on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-new-text-servic... Kind regards, Mirjam Kuehne RIPE Labs
Hello Mirjam, et al, thank you for the work on providing the text-based output for STAT. Please send thank-yous to the team. I have just noticed that if you query for e.g. an IPv4 prefix, it also seems to report a 1% IPv6-visibility on the 88 IPv6 peers. Is that a rounding-bug? :) Cheers Sascha
RIPEstat is now also available as a text-based interface for users who prefer a command-line interface (CLI) and those interested in including RIPEstat data in shell scripting. Please find more information on RIPE Labs:
-- Sascha E. Pollok E-Mail: sp@iphh.net Manager Network Design and Operations Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408 AG Hamburg, HRB 76071 20537 Hamburg, Germany CEO: Axel G. Kroeger
Hello Sascha, On 11/9/12 11:07 AM, Sascha E. Pollok wrote:
Hello Mirjam, et al,
thank you for the work on providing the text-based output for STAT. Please send thank-yous to the team.
I have just noticed that if you query for e.g. an IPv4 prefix, it also seems to report a 1% IPv6-visibility on the 88 IPv6 peers. Is that a rounding-bug? :)
We have noticed that before. What's happening is that one of the RIS IPv6 peers is passing an IPv4 full table feed. And that is incorrectly causing the visibility of v4 prefixes to be flagged as v6 visibility for that peer. Bug is logged and we intend to correct it soon. Thanks for the heads up. :)
Cheers Sascha
RIPEstat is now also available as a text-based interface for users who prefer a command-line interface (CLI) and those interested in including RIPEstat data in shell scripting. Please find more information on RIPE Labs:
Cheers, Vasco
Hello Vasco,
thank you for the work on providing the text-based output for STAT. Please send thank-yous to the team.
I have just noticed that if you query for e.g. an IPv4 prefix, it also seems to report a 1% IPv6-visibility on the 88 IPv6 peers. Is that a rounding-bug? :)
We have noticed that before. What's happening is that one of the RIS IPv6 peers is passing an IPv4 full table feed. And that is incorrectly causing the visibility of v4 prefixes to be flagged as v6 visibility for that peer. Bug is logged and we intend to correct it soon. Thanks for the heads up. :)
I had thought about that but assumed that the RIS sessions are clean with the address families. So - not a bug after all ;-) One could only argue if a "v4 prefix received on a v6 RIS session" is an IPv6 visibility ;-) Obrigado, Vasco! Cheers Sascha
participants (3)
-
Mirjam Kuehne -
Sascha E. Pollok -
Vasco Asturiano