Hi Tim, Thanks for raising these valid points.
prometheus-smokeping-prober is still quite a young package, and was first uploaded not long before the bullseye freeze, so it perhaps lacked a bit of polish. The cap_net_raw debconf db setup is identical to how it is implemented in prometheus-blackbox-exporter, which also defaults to false. In the case of blackbox_exporter, I think this is *probably* justified, since it probes targets on demand, and accepts targets in the scrape URL. smokeping_prober is a little different however, since the targets are predefined, and are pinged on a schedule determined by smokeping_prober itself, so the opportunity for abuse is greatly diminished. I think we could safely enable cap_net_raw by default for this package. On the subject of logging errors when unable to send packets, I don't believe this would be best implemented by a debian patch, since such errors are not debian-specific. I recommend that you open an issue upstream on github to address that. Daniel Swarbrick
