To follow up on myself (I seem to do that a lot) see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109709. The problem that this patch tries to fix is sort of real (but see below), but the patch is plain wrong. Yes it fixes that issue, but introduces this new bug.
Which one is more serious? I think this bug is more serious and the patch should be (maybe partially) reverted. The original bug can be avoided (I think) by simply using the -n switch, so it's even a solution to a non-problem. This bug has no workaround. ** Bug watch added: Debian Bug tracker #109709 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405232 Title: ping reports wrong IP responding under certain conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1405232/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
