> /* Linux is nice -- it can tell us right away that we cannot > * reach this recipient by returning an ENETUNREACH error > * code. So, when this happens let's "down" the host NOW so > * we don't sit around waiting for this host to timeout later. > */
I can't speak for the Windows implementation ... but I thought that the Linux version of this drove some network implementations nuts (e.g., the BIND codebase), because if you send out a bunch of packets to different hosts it's impossible to match up the ICMP error with a particular packet, and depending on what you're doing you may get an error from the "wrong" server (this is why other Unixes require the use of a connected socket to get back ICMP errors). Maybe this has changed, I dunno. --Ken _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
