[ previous ] [ next ] [ threads ]
 
 From:  Cameron Showalter <cameron at gwschool dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  OT - DUP! ping
 Date:  Wed, 21 Sep 2005 07:08:38 -0700
hey folks,
this may be off topic to m0n0 discussion, but this started happening 
after I made some additions to the dns forwarder on my m0n0 box.   it 
happens on both the live and private IP address for one remote site.  
the remote vpn endpoint is a symantec fw/vpn 100 appliance.   and this 
is one of 8 remote locations and the only one getting this response.

from any box on subnet 192.168.1.0 trying to ping any box on 
192.168.80.0 I get:
64 bytes from store80 (192.168.80.2): icmp_seq=1 ttl=63 time=217 ms (DUP!)
64 bytes from store80 (192.168.80.2): icmp_seq=1 ttl=63 time=222 ms (DUP!)
64 bytes from store80 (192.168.80.2): icmp_seq=1 ttl=63 time=227 ms (DUP!)
64 bytes from store80 (192.168.80.2): icmp_seq=1 ttl=63 time=231 ms (DUP!)
64 bytes from store80 (192.168.80.2): icmp_seq=1 ttl=63 time=237 ms (DUP!)

--- 192.168.80.3 ping statistics ---
1 packets transmitted, 1 received, +19 duplicates, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 162.006/204.225/246.870/25.531 ms

and from any box on 192.168.80.0  back to 192.168.1.0 I get
64 bytes from gwshq (192.168.1.50): icmp_seq=1 ttl=62 time=372 ms (DUP!)
64 bytes from gwshq (192.168.1.50): icmp_seq=1 ttl=62 time=395 ms (DUP!)
64 bytes from gwshq (192.168.1.50): icmp_seq=1 ttl=62 time=421 ms (DUP!)
64 bytes from gwshq (192.168.1.50): icmp_seq=1 ttl=62 time=439 ms (DUP!)
64 bytes from gwshq (192.168.1.50): icmp_seq=1 ttl=62 time=447 ms (DUP!)

--- gwshq ping statistics ---
1 packets transmitted, 1 received, +24 duplicates, 0% loss, time 0ms
rtt min/avg/max/mdev = 161.273/282.732/447.279/85.633 ms

I also get the same DUP! message when I try to ping the WAN IP of the 
router at 192.168.80.0

google doesnt really help.

thanks,
cameron