Ticket #853 (closed defect: fixed)

Opened 2 years ago

Last modified 4 months ago

ip_ plugins doesn't report ipv6 stats.

Reported by: feiner.tom Assigned to: nobody
Priority: normal Milestone: Munin 1.4.4
Component: plugins Version: 1.4.3
Severity: normal Keywords:
Cc: kurt@roeckx.be

Description

Forwarded from: http://bugs.debian.org/567551

It seems that the ip_ plugin now added some support for reporting ipv6 stats, but it's not properly working. The only thing that works is suggesting it.

There is nothing that uses ip6tables to report the stats. I added the following in my version and it seems to be working: ip6tables -L ${INPUT} -v -n -x | grep -m1 "$IP" |

awk "{ print \"in.value \" \$2 }"

ip6tables -L ${OUTPUT} -v -n -x | grep -m1 "$IP" |

awk "{ print \"out.value \" \$2 }"

Note that there is a "/128" after the IP address and not a space in case of ipv6.

Kurt

Change History

02/14/10 19:09:52 changed by snide

  • milestone changed from Munin 1.5 to Munin 1.4.4.

Pushing it for 1.4.4, since it's a real bug.

11/18/10 09:36:43 changed by andrieslouw

When you replace all instances of :: in your IP by :0: (or as many as needed) the plugin works well!

Example: ip_2a00:dd0:0:13:b:a::1 -> Doesn't work ip_2a00:dd0:0:13:b:a:0:1 -> Does work

And: ip_2a00:dd0:0:13:b::1 -> Doesn't work ip_2a00:dd0:0:13:b:0:0:1 -> Does work

I don't know if this problem originates from ip6tables, or the plugin in Munin, but replacing instances of :: by :0: solved all problems for me!

(Example: http://monitor.weserv.nl/prodes.nl/libertus.prodes.nl/ip_2a00_dd0_0_13_b_a_0_1.html )

01/09/12 08:45:21 changed by kenyon

  • status changed from new to closed.
  • resolution set to fixed.

The issues in the original bug report were fixed in these trunk revisions: r3289, r4077; and these 1.4-stable revisions: r4076. This is essentially a duplicate of #1009.

Regarding comment 2 by andrieslouw, if that problem still exists, it is a separate issue. I will create a new ticket for tracking that.

01/09/12 08:48:16 changed by kenyon

New ticket extracted from comment 2 is #1172.

01/09/12 08:51:07 changed by kenyon

Sorry, this wasn't a duplicate of #1009, but closely related.