File: NEWS

package info (click to toggle)
iputils 3%3A20240905-3
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 1,700 kB
  • sloc: ansic: 6,002; xml: 1,797; sh: 538; makefile: 28
file content (26 lines) | stat: -rw-r--r-- 1,312 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
iputils (3:20240905-2) unstable; urgency=medium

  Ping is no longer installed with access to the CAP_NET_RAW linux
  capability, but instead uses ICMP_PROTO datagram sockets for network
  communication.  Access to these sockets is controlled by GID based on the
  net.ipv4.ping_group_range sysctl.  In normal installations, the
  linux-sysctl-defaults package will set this variable to a broadly permissive
  value, allowing unprivileged users to use ping as expected.  See
  /usr/lib/sysctl.d/50-default.conf and
  https://docs.kernel.org/networking/ip-sysctl.html#ip-sysctl for more
  information on the semantics of this variable.

 -- Noah Meyerhans <noahm@debian.org> Mon, 21 Apr 2025 07:29:28 -0400

iputils (3:20150815-1) unstable; urgency=medium

  As of 3:20150815-1, the ping and ping6 commands are unified in a single
  binary that can communicate with targets of either address family. In 
  order to force the use of a specific address family, you need to either 
  pass the argument -4 or -6 on the command line, or call the program via 
  one of the ping4 or ping6 names.

  You will need to be particularly aware of this change if you're invoking ping
  via a script as part of a monitoring or other such automated system.

 -- Noah Meyerhans <noahm@debian.org>  Fri, 19 Feb 2016 22:26:30 -0800