Re: [bug-inetutils] bug in ping: ip->ip_src and ip->ip_dst hold the same value

[Sam Halliday]

this one goes back a while
[http://mail.gnu.org/archive/html/bug-inetutils/2003-08/msg00001.html], sorry i
was a bit busy:

Sergey Poznyakoff wrote:
> > unfortunately i was not able to find or fix
> > this problem as i cannot even see where ip->ip_dst is being set anywhere in
> > the code, but it is clear that there is a problem somewhere.
> 
> Ip_dst is not set anywhere, it is retrieved from the IP packet header
> received from the remote station. If both ip_src and ip_dst are the
> same, this means that the same interface was sending and answering
> the requests.
> 
> If you wish a more detailed analisis, please supply some more
> information about your test, at least the exact invocation of ping and
> the first several lines of its output. Also, the information about the
> interfaces on the source machine.

ok, i am on a LAN which is served as usual by a DHCP server at 192.168.0.1, my
address being 192.168.0.2. i get the following output if i attempt to ping the
(non-existent) address 192.168.0.11 with inetutils-1.4.2

$ping -v 192.168.0.11
PING 192.168.0.11 (192.168.0.11): 56 data bytes
64 bytes from hostess (192.168.0.2): Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst Data
 4  5  c0 7000 09ed   0 0000  40  01 6f0b 192.168.0.2  192.168.0.2

(note the Dst Data is not correct), whereas i get the following from netkit-0.17

$ping -v 192.168.0.11
PING 192.168.0.11 (192.168.0.11): 56 octets data
92 octets from hostess (192.168.0.2): Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst Data
 4  5  00 5400 0000   0 0040  40  01 4bb9 192.168.0.2  192.168.0.11

which does contain the correct Dst Data.

the Src machine has a standard network card on eth0... the Dst does not exist.

cheers,
Sam

pgpdtbQYNluo8.pgp
Description: PGP signature