The all-zeroes broadcast address was de rigeur for SunOS 4.x systems, and
systems of later vintage than that typically used all-ones. As I recall,
many modern systems won't recognize all-zero as a broadcast address unless
they're instructed to. This may explain the different outcomes on different
systems.
I'd also suggest you double-check your netmasks - a packet to
192.168.128.255 won't be responded to unless the receiving system's netmask
is such that the left half of the origin address matches its idea of the
network, and the right half is all-1.
-Michael Pelletier.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Lussier
Sent: Friday, September 05, 2008 10:04 AM
To: gnhlug-discuss@mail.gnhlug.org
Subject: Linux network behavior wierdness
Hi all,
I have a wierd problem where some hosts respond to a broadcast ping packet
and others don't.
I have some hosts which, when I do a ping -b 10.95.0.0 everything answers.
On other hosts, doing exactly the same thing, I get no response.
A reboot resets a "broken" host, but over time it will re-develop the
problem.
And I can't seem to figure out how to make the problem occur...
I can't figure out if it's something we're doing which is causing this
change, or if it's a kernel thing where some threshold is reached and it
just stops.
Fwiw, we're running Debian/Etch with a 2.6.18 kernel. Most NICs are Intel
e1000, though some are broadcom. In general, I've seen it happen across our
lab on different hardware platforms with different motherboards and nics.
Any insights would be most appreciated.
--
Seeya,
Paul
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
