We need to able to add Ipv6 hosts to the <BeaconList>. However, PingER Measurement Agents (MA) that are not IPv6 capable need to NOT ping the IPv6 hosts, else there is noise in the measurements. At the same time we do not wish to upgrade pinger2.pl at all MAs.
An interim solution is to not add IPv6 hosts to the Beacon list, rather enter them into the local <HostList> for MAs that wish to add IPv6 monitoring.
Pros:
Simple modification to pinger2.pl to not ping hosts with IPv6 addresses if the MA is not ping6 capable
If the host is not ping6 capable then the reponse will look like: pi@pinger-raspberry ~ $ ping6 2607:f8b0:4007:802::200e socket: Address family not supported by protocol |
Cons:
Mitigations
Add a <BeaconList6> for IPv6 targets. This requires modifications to create the new <BeaconList6>, plus modifying pinger2.pl to utilize the new <BeaconList6>
Pros:
Cons: