On Tue, Aug 02, 2005 at 09:37:40PM +0800, Lars Hansson wrote: > Pinging from 2 w2k workstations thru a NAT'ing openbsd 3.4 (yes, it's old > i know) to 66.94.230.34 (www.yahoo.com) I can reproduce this problem. > The second workstation gets "destination unreachable" until a while after > the first stops (for states to time out, i presume).
Yes, Windows' ping tool is stupid, also see http://cert.uni-stuttgart.de/archive/bugtraq/2001/05/msg00028.html (they use constant ICMP IDs per OS revision, instead of using some process ID or a random per-invokation value, like everyone else) I like Pejman's idea of translating the ICMP ID like a (TCP/UDP) port in NAT, added to the to-do list. At the very bottom. For manual invokations, this is hardly a problem (if even a nuisance). And if you use ICMP for automatic checks, use a sane tool or OS. :) Daniel
