why broadcast on *.0 (network) addresses ?

Harald Koenig (koenig@tat.physik.uni-tuebingen.de)
Wed, 27 Jan 1999 15:42:30 +0100


why do I get

64 bytes from 134.2.170.66: icmp_seq=1 ttl=64 time=2.4 ms (DUP!)

when I run

ping 134.2.170.0

on another PC in the same network ? please not the broadcast setup below!
ping to `134.2.170.255' are broadcasts, but what about packages sent to `134.2.170.0' ?

this happens with both 2.0 and 2.2 kernel.
network setup for the pinged host (all PCs with same setup in one class C network) :

eth0 Link encap:10Mbps Ethernet HWaddr 00:40:05:37:B9:B2
inet addr:134.2.170.66 Bcast:134.2.170.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2982215 errors:0 dropped:0 overruns:0
TX packets:3738433 errors:3 dropped:0 overruns:2
Interrupt:10 Base address:0x7c80

thanks for any pointer,

Harald

--
All SCSI disks will from now on                     ___       _____
be required to send an email notice                0--,|    /OOOOOOO\
24 hours prior to complete hardware failure!      <_/  /  /OOOOOOOOOOO\
                                                    \  \/OOOOOOOOOOOOOOO\
                                                      \ OOOOOOOOOOOOOOOOO|//
Harald Koenig,                                         \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik                              //  /     \\  \
koenig@tat.physik.uni-tuebingen.de                     ^^^^^       ^^^^^

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/