I think we may have red-herringed on the OS thing -- if RH6.2, as
deployed, had this sort of problem, I think we would have run across it
before this, no? The inclusion of a FreeBSD-4.2-STABLE in the mix seems
to nix a RH specific bug as well (althought it obviously does not rule
it out entirely*). Perhaps we're overlooking some other, more subtle
commonality between these four setups?
Could at least two of the OP's please detail (for me, if not for the
list, at least) the devices that sit between the NIC of the host in
question and the Big Bad Internet? Routers, hubs, transparent firewalls,
everything?
*I highly recommend that the FreeBSD-4.2-STABLE user at least upgrade to
4.3R -- I'm not sure at which point in 4.2-STABLE you froze your local
tree, but a whole bunch of fixes made it into 4.3, and it's been running
great for me.
--
Greg White
