ping-announced IP as GW's IP, i.e. wrong if target is down and then boots up and starts responding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iputils (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ping-announced IP address as source host's IP, i.e. wrong, when target is down and when the target then boots up and starts responding, the response is noted to come from (still) the host itself:
The lines with the response times say the responding IP is the one of the pinging host itself, instead of the target that was originally being pinged:
root@ASDF:~# ping 10.200.0.71
PING 10.200.0.71 (10.200.0.71) 56(84) bytes of data.
From 10.200.0.70 icmp_seq=1 Destination Host Unreachable
From 10.200.0.70 icmp_seq=2 Destination Host Unreachable
...
From 10.200.0.70 icmp_seq=54 Destination Host Unreachable
64 bytes from 10.200.0.70: icmp_seq=55 ttl=64 time=775 ms
64 bytes from 10.200.0.70: icmp_seq=56 ttl=64 time=0.311 ms
...
64 bytes from 10.200.0.70: icmp_seq=78 ttl=64 time=0.250 ms
^C
--- 10.200.0.71 ping statistics ---
78 packets transmitted, 24 received, +40 errors, 69% packet loss, time 77000ms
rtt min/avg/max/mdev = 0.161/32.
root@ASDF:~# ping 10.200.0.71
PING 10.200.0.71 (10.200.0.71) 56(84) bytes of data.
64 bytes from 10.200.0.71: icmp_seq=1 ttl=64 time=0.220 ms
64 bytes from 10.200.0.71: icmp_seq=2 ttl=64 time=0.198 ms
64 bytes from 10.200.0.71: icmp_seq=3 ttl=64 time=0.214 ms
64 bytes from 10.200.0.71: icmp_seq=4 ttl=64 time=0.171 ms
^C
--- 10.200.0.71 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.171/0.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: iputils-ping 3:20121221-
ProcVersionSign
Uname: Linux 3.16.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Thu Jan 21 14:11:04 2016
InstallationDate: Installed on 2016-01-15 (5 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)