ping6 output too wide

Bug #1375430 reported by Adam Novak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
iputils (Ubuntu)
New
Undecided
Unassigned

Bug Description

A fully-filled-in IPv6 address is 8 groups of 4 characters each, with 7 colons, for a total of 39 characters. This is much longer than the 4 * 4 + 3 = 19 characters maximum required to represent an IPv4 address, which is what the output format that ping6 inherits from ping was designed around.

When asked to ping a full IPv6 address, ping6's output wraps just a few characters onto the next 80-character line:

anovak@hex:~$ ping6 fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95
PING fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95(fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9
c95) 56 data bytes
64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=1 ttl=42 time=89.
6 ms
64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=2 ttl=42 time=111
 ms

If something could be cut from the output format (maybe the "icmp_" in "icmp_seq", or the "from"?), the output for pinging a full IPv6 address could fit on one 80-character terminal line, just like that from pinging an IPv4 address. This would make the ping6 tool much more useable, as the round trip times would not be constantly split over two lines, and it would then be much easier to take in latency at a glance.

Please reduce the number of characters in the output format so that a ping to an IPv6 address produces <=80 characters of output per ping in this common use case.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: iputils-ping 3:20101006-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-69.103-generic 3.2.62
Uname: Linux 3.2.0-69-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.7
Architecture: amd64
Date: Mon Sep 29 12:02:49 2014
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Adam Novak (interfect) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.