DUP response in pings from SMC Business Gateway to our public ips

here is some additional info:

when i try to ping the private lan side ip of the comcast gateway FROM the gateways diagnotics tools ping.. it works fine, but there is some latency that doesn't make sense to me..

PING 192.168.69.254 (192.168.69.254): 56 data bytes
64 bytes from 192.168.69.254: seq=0 ttl=64 time=90ms
64 bytes from 192.168.69.254: seq=1 ttl=64 time=60ms
64 bytes from 192.168.69.254: seq=2 ttl=64 time=0ms
64 bytes from 192.168.69.254: seq=3 ttl=64 time=0ms

--- 192.168.69.254 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0/37/90 ms

PING 192.168.69.254 (192.168.69.254): 56 data bytes
64 bytes from 192.168.69.254: seq=0 ttl=64 time=160ms
64 bytes from 192.168.69.254: seq=1 ttl=64 time=30ms
64 bytes from 192.168.69.254: seq=2 ttl=64 time=80ms
64 bytes from 192.168.69.254: seq=3 ttl=64 time=20ms

--- 192.168.69.254 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 20/72/160 ms

if i ping the wireless AP from the same gateway web interface i get some packets dropping:

PING 192.168.69.1 (192.168.69.1): 56 data bytes
64 bytes from 192.168.69.1: seq=0 ttl=64 time=10ms
64 bytes from 192.168.69.1: seq=1 ttl=64 time=80ms
64 bytes from 192.168.69.1: seq=2 ttl=64 time=200ms

--- 192.168.69.1 ping statistics ---
4 packets transmitted, 3 packets received, 25% packet loss
round-trip min/avg/max = 10/96/200 ms 

and then a few seconds later its fine

PING 192.168.69.1 (192.168.69.1): 56 data bytes
64 bytes from 192.168.69.1: seq=0 ttl=64 time=20ms
64 bytes from 192.168.69.1: seq=1 ttl=64 time=40ms
64 bytes from 192.168.69.1: seq=2 ttl=64 time=20ms
64 bytes from 192.168.69.1: seq=3 ttl=64 time=20ms

--- 192.168.69.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 20/25/40 ms

if i ping that same wireless Ap from my laptop which is connected to that AP its fine:

Pinging 192.168.69.1 with 32 bytes of data:
Reply from 192.168.69.1: bytes=32 time=5ms TTL=64
Reply from 192.168.69.1: bytes=32 time=5ms TTL=64
Reply from 192.168.69.1: bytes=32 time=10ms TTL=64
Reply from 192.168.69.1: bytes=32 time=6ms TTL=64
Reply from 192.168.69.1: bytes=32 time=11ms TTL=64
Reply from 192.168.69.1: bytes=32 time=8ms TTL=64
Reply from 192.168.69.1: bytes=32 time=3ms TTL=64
Reply from 192.168.69.1: bytes=32 time=3ms TTL=64
Reply from 192.168.69.1: bytes=32 time=3ms TTL=64
Reply from 192.168.69.1: bytes=32 time=17ms TTL=64
Reply from 192.168.69.1: bytes=32 time=2ms TTL=64
Reply from 192.168.69.1: bytes=32 time=1ms TTL=64
Reply from 192.168.69.1: bytes=32 time=1ms TTL=64
Reply from 192.168.69.1: bytes=32 time=2ms TTL=64
Reply from 192.168.69.1: bytes=32 time=4ms TTL=64
Reply from 192.168.69.1: bytes=32 time=3ms TTL=64
Reply from 192.168.69.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.69.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 17ms, Average = 5ms

pinging the comcast SMC gateway from my laptop i drop packets:

Pinging 192.168.69.254 with 32 bytes of data:
Reply from 192.168.69.254: bytes=32 time=23ms TTL=64
Reply from 192.168.69.254: bytes=32 time=48ms TTL=64
Reply from 192.168.69.254: bytes=32 time=2ms TTL=64
Reply from 192.168.69.254: bytes=32 time=18ms TTL=64
Reply from 192.168.69.254: bytes=32 time=339ms TTL=64
Reply from 192.168.69.254: bytes=32 time=19ms TTL=64
Reply from 192.168.69.254: bytes=32 time=108ms TTL=64
Reply from 192.168.69.254: bytes=32 time=71ms TTL=64
Reply from 192.168.69.254: bytes=32 time=62ms TTL=64
Reply from 192.168.69.254: bytes=32 time=95ms TTL=64
Reply from 192.168.69.254: bytes=32 time=14ms TTL=64
Reply from 192.168.69.254: bytes=32 time=116ms TTL=64
Reply from 192.168.69.254: bytes=32 time=167ms TTL=64
Reply from 192.168.69.254: bytes=32 time=253ms TTL=64
Request timed out.
Reply from 192.168.69.254: bytes=32 time=44ms TTL=64
Reply from 192.168.69.254: bytes=32 time=17ms TTL=64
Reply from 192.168.69.254: bytes=32 time=20ms TTL=64
Reply from 192.168.69.254: bytes=32 time=112ms TTL=64
Reply from 192.168.69.254: bytes=32 time=4ms TTL=64
Reply from 192.168.69.254: bytes=32 time=141ms TTL=64
Reply from 192.168.69.254: bytes=32 time=139ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.69.254: bytes=32 time=7ms TTL=64
Reply from 192.168.69.254: bytes=32 time=9ms TTL=64
Reply from 192.168.69.254: bytes=32 time=33ms TTL=64
Reply from 192.168.69.254: bytes=32 time=19ms TTL=64

Ping statistics for 192.168.69.254:
Packets: Sent = 28, Received = 25, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 339ms, Average = 75ms

pinging to my public IP's from my laptop i also drop packets and the latency in both cases is really erratic.

Welcome Jermaine72.   Your posted data points to connectivity issues on the LAN side of the SMC.  We can schedule a service call to replace the gateway to rule out the LAN ports on the SMC. Please let us know if a service call is requested.

Thank You

Thank you, i would love to have the gateway replaced just to rule it out.  I have 5 static ip's if that matters in the request.

Thanks again