Re: why broadcast on *.0 (network) addresses ?

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Vito Calderone: "Kernel"
• Previous message: Romano Giannetti: "mtools and 2.2.0"
• Maybe in reply to: Harald Koenig: "why broadcast on *.0 (network) addresses ?"
• Next in thread: Nimrod Zimerman: "Re: VM performance"
• Reply: Nimrod Zimerman: "Re: VM performance"

> 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' ?

Same thing happening here.

All the machines on the LAN respond both to x.x.x.0 and x.x.x.255
These are Windows , IRIX , Linux and who-knows-what machines.
Seems to be a TCP/IP "feature".

--
David Balazic , student
E-mail   : 1stein@writeme.com     |     living in  sLOVEnija
home page: http://surf.to/stein
Computer: Amiga 1200 + Quantum LPS-340AT
--

-
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/






 Next message: Vito Calderone: "Kernel"
 Previous message: Romano Giannetti: "mtools and 2.2.0"
 Maybe in reply to: Harald Koenig: "why broadcast on *.0 (network) addresses ?"

 Next in thread: Nimrod Zimerman: "Re: VM performance"
 Reply: Nimrod Zimerman: "Re: VM performance"