Jeremy D. Worrells writes:
 > Thanks all for your hints and tips. Here is some information that has been
 > requested by people:
 > 
 > For Jeremy, the output of ifconfig -a:
 > 
 > le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX>
 > 	inet 205.142.124.90 netmask 0xffffff00 broadcast 205.142.124.255
 > lo0: flags=8009<UP,LOOPBACK,MULTICAST>
 > 	inet 127.0.0.1 netmask 0xff000000 
 > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST>
 > sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST>
 > ppp0: flags=8010<POINTOPOINT,MULTICAST>
 > ppp1: flags=8010<POINTOPOINT,MULTICAST>
 > tun0: flags=10<POINTOPOINT>
 > tun1: flags=10<POINTOPOINT>
 > 
 > Also, the output from netstat -an -f inet:

Could you also produce a "netstat -rn" to get the routing table.

The DUP replies can occur if you ping on the broadcast address. You
don't appear to be doing this but if your default route is to the
broadcast address then you might see this behaviour.

So is your default route to 205.142.124.255 or 205.142.124.0 instead
of a more usual policy of having the gateway 1 in from the ends at 1
or 254.

I don't guarantee that this is the fault but here is my output:

A ping to 166.93.219.64 (Our broadcast address)
alta > ping 166.93.219.64
PING 166.93.219.64 (166.93.219.64): 56 data bytes
64 bytes from 166.93.219.79: icmp_seq=0 ttl=255 time=10.550 ms
64 bytes from 166.93.219.80: icmp_seq=0 ttl=255 time=41.028 ms (DUP!)
64 bytes from 166.93.219.66: icmp_seq=0 ttl=255 time=49.735 ms (DUP!)
64 bytes from 166.93.219.74: icmp_seq=0 ttl=64 time=50.134 ms (DUP!)
64 bytes from 166.93.219.71: icmp_seq=0 ttl=255 time=50.523 ms (DUP!)
64 bytes from 166.93.219.87: icmp_seq=0 ttl=64 time=50.876 ms (DUP!)
64 bytes from 166.93.219.82: icmp_seq=0 ttl=254 time=51.220 ms (DUP!)

Alex.

-- 
Alex Barclay			E-mail: alex@vsys.com
Vsys, Inc.
731 N.Weber, Suite 202		Tel:    +1 719 635 8066 x 17
Colorado Springs, CO 80903	Fax:    +1 719 635 1420