Public bug reported:
In Ubuntu 14.04 Desktop, when I ping the broadcast address (in my case the eth1
is 172.22.1.65/16):
ping -Ieth1 -b 255.255.255.255
OR
ping -b 172.22.255.255
The response from multiple host are NOT reflected properly. Intead the
subsequent response are marked (DUP!) BUT stamped with the same address
of the first received response.
Ex:
rtp-lab@wks65lnx:~$ ping -Ieth1 -bc2 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) from 172.22.1.65 eth1: 56(84) bytes of
data.
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=0.634 ms
64 bytes from 172.22.0.10: icmp_seq=1 ttl=255 time=0.647 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=63 time=0.648 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=1.83 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=2 ttl=64 time=0.566 ms
>From wireshark/tcpdump, I can confirmed that those 3 duplicates packets
are coming from different hosts: 172.22.2.1, 172.22.0.10 (2 replies, not
sure why, but not important in this case), and 172.22.1.65 (itself, I
allow the node to answer broadcasted ping for this test).
rtp-lab@wks65lnx:~$ sudo tcpdump -ni eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
12:49:08.471063 IP 172.23.0.1.123 > 172.23.255.255.123: NTPv4, Broadcast,
length 48
12:49:09.000925 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 21934,
seq 1, length 64
12:49:09.001424 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 1,
length 64
12:49:09.001437 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
1, length 64
12:49:09.003996 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 1,
length 64
12:49:09.004006 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 1,
length 64
12:49:10.001551 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 21934,
seq 2, length 64
12:49:10.002093 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 2,
length 64
12:49:10.002106 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
2, length 64
12:49:10.002107 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 2,
length 64
12:49:10.003683 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 2,
length 64
The issue was NOT see in Ubuntu 12.04 Server. While those replies are
marked (DUP!) HOWEVER the 'from' address are correct.
** Affects: iputils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1547611
Title:
Response from pinging broadcast address does not reflect the actual
sender address.
Status in iputils package in Ubuntu:
New
Bug description:
In Ubuntu 14.04 Desktop, when I ping the broadcast address (in my case the
eth1 is 172.22.1.65/16):
ping -Ieth1 -b 255.255.255.255
OR
ping -b 172.22.255.255
The response from multiple host are NOT reflected properly. Intead the
subsequent response are marked (DUP!) BUT stamped with the same
address of the first received response.
Ex:
rtp-lab@wks65lnx:~$ ping -Ieth1 -bc2 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) from 172.22.1.65 eth1: 56(84) bytes of
data.
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=0.634 ms
64 bytes from 172.22.0.10: icmp_seq=1 ttl=255 time=0.647 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=63 time=0.648 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=1.83 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=2 ttl=64 time=0.566 ms
From wireshark/tcpdump, I can confirmed that those 3 duplicates
packets are coming from different hosts: 172.22.2.1, 172.22.0.10 (2
replies, not sure why, but not important in this case), and
172.22.1.65 (itself, I allow the node to answer broadcasted ping for
this test).
rtp-lab@wks65lnx:~$ sudo tcpdump -ni eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
12:49:08.471063 IP 172.23.0.1.123 > 172.23.255.255.123: NTPv4, Broadcast,
length 48
12:49:09.000925 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id
21934, seq 1, length 64
12:49:09.001424 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq
1, length 64
12:49:09.001437 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
1, length 64
12:49:09.003996 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq
1, length 64
12:49:09.004006 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
1, length 64
12:49:10.001551 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id
21934, seq 2, length 64
12:49:10.002093 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq
2, length 64
12:49:10.002106 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
2, length 64
12:49:10.002107 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq
2, length 64
12:49:10.003683 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq
2, length 64
The issue was NOT see in Ubuntu 12.04 Server. While those replies are
marked (DUP!) HOWEVER the 'from' address are correct.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1547611/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
