I've brought up the server to collect some stats for the IPV6ONLYEXP IPv6-only experimental SSID at RIPE67.
I just made a new copy of the VM that I typically use, with practically zero changes - so there are some artifacts of that. Hence I thought would be worth explaining here what is what.
The "Gateway traffic" graph is a graphed screen-scrape of the "show interface" bps values. It's intentionally vague - as I use it for different purposes - either for measuring aggregate load on the interface in case the interface is dualstacked, or, in a setups like this one, measuring the utilization on the interface looking at the SSID - like the setup at RIPE67. Due to its generic nature, it's always easy to have this graph, so I do.
IPv4/IPv6 traffic graphs talk about traffic on 3 interfaces: the one facing the wireless clients connecting to IPV6ONLYEXP, the one facing the internet (it's dualstack), and the one facing the recursive resolver with DNS64. This is IP-MIB::ipIfStatsHCInOctets.ipv6, IP-MIB::ipIfStatsHCOutOctets.ipv6, IP-MIB::ipIfStatsHCInOctets.ipv4, IP-MIB::ipIfStatsHCOutOctets.ipv4, graphed over time.
Another very generic graph - it collects the output of IPv6 neighbor table and IPv4 ARP table and does some aggregates. Also it pipes the data to the two other graphs that do a more meaningful work.
The term "VLAN" is a bit of a misnomer in this case - they are actually the three different interfaces. Just that the tooling expects a single trunk connection, and I did not want to mess with the code too much. Thus, a weird "VLAN number" 0. Again, it's not a VLAN number, it's the trailing digit of the interface number.
This graph deduplicates the addresses seen on the VLAN based on the MAC address and does some aggregates after. So, it allows to remove the artifacts that are arising due to the use of privacy addresses and/or usage of more than one address per host. The "VLAN" you are going to be interested in is the #1 - this is the interface going to the SSID.
Same story as the previous one - but the dataset is taken across all VLANs. Why have it ? In bigger setups there may be more than one wireless VLAN, so this allows to gauge the number of clients that are overall on the network. For this setup, I left it mostly just as a sanity check.
So, now that I told what is what - here's how to get it: http://ripe67.ipv6-test.net/munin/ipv6noc/index.html.
This is a host which is not available over the legacy IP protocol - if you wanna view the stats - update yourself to the current version of the IP! Also - all the data is being collected only over the current version of IP protocol as well (IPv6) - I did not use the legacy IP for the management.
| Name | Last Modified | Size | Type |
|---|---|---|---|
| Parent Directory/ | - | Directory |