Created attachment 347132 [details] build.log $summary also, attached build.log Unfortunately my search for a solution didn't bring up much except for some ancient results.
thought i had seen this one before. My problem was that iptables was setup to drop all ICMP traffic, so i had to temporarily drop a few rules from iptables to let configure complete...
No iptables involved here... but I couldn't reproduce this on a new machine.
I have a fix for this, just waiting to make sure the cure is not worse than the disease.
I wonder whether it makes any sense to filter out ICMP on lo. Essentially any firewall tutorial starts with something like `iptables -i lo -j ACCEPT`. Is there any valid use case for filtering traffic on lo? What attack model does it guard against? Perhaps it's not worth the risk of future breakage to support a (IMHO, anyway) misconfigured system.
(In reply to Jan Kundrát from comment #4) > I wonder whether it makes any sense to filter out ICMP on lo. I don't think there is one. But it's an easy enough misconfiguration to create. Having no network support whatsoever (i.e. `ifconfig lo down`) is much more probable. > Perhaps it's not worth the risk of future breakage to support a (IMHO, > anyway) misconfigured system. That's why I asked, but I'm feeling adventurous. The syntax seems to be the same everywhere, and I'm going to leave a note in the ebuild mentioning this bug. So if anyone has a problem I'll just quickly revert it.
Whee: *nagios-plugins-2.0.3-r1 (26 Nov 2014) 26 Nov 2014; Michael Orlitzky <mjo@gentoo.org> +nagios-plugins-2.0.3-r1.ebuild: Revbump to fix bug #468296 and bug #481926. I left the previous ebuild there so that people can still build it if this one's broken.
