What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

GS108T ping?

Carnagerover

Senior Member
Hi all,

I have a GS108T plugged into a Netgear R6300 router, the GS108T has 5 devices plugged into it, 3 x 10/100 and 3x 100Mbps including a 1000 Mbps uplink connection to the R6300 Router. The R6300 has no other devices plugged into it other than the link to the switch.

When I ping the R6300 router I get the following:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Stu>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 41, Received = 41, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 2ms

I have never had a smart switch before but normally on any other normal switch I have had when pinging through to my router it is always <1ms. Does this seem a little high, some replies are as high as 10ms. I noticed the other night that my ping was a little erratic and the switch would seem to be the cause.

Any Ideas?
 
Last edited:
Looks like the R6300 has a part to play, I took my Ubuntu netbook downstairs and plugged a cat5.e straight into the router and got these results:

stu@stu-NC10:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=8.38 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=6.53 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=4.88 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=3.49 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=1.72 ms
64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=2.26 ms
64 bytes from 192.168.1.1: icmp_req=7 ttl=64 time=3.35 ms
64 bytes from 192.168.1.1: icmp_req=8 ttl=64 time=6.41 ms
64 bytes from 192.168.1.1: icmp_req=9 ttl=64 time=4.70 ms
64 bytes from 192.168.1.1: icmp_req=10 ttl=64 time=2.73 ms
64 bytes from 192.168.1.1: icmp_req=11 ttl=64 time=0.638 ms
64 bytes from 192.168.1.1: icmp_req=12 ttl=64 time=0.599 ms
64 bytes from 192.168.1.1: icmp_req=13 ttl=64 time=0.845 ms
64 bytes from 192.168.1.1: icmp_req=14 ttl=64 time=10.0 ms
64 bytes from 192.168.1.1: icmp_req=15 ttl=64 time=5.51 ms
64 bytes from 192.168.1.1: icmp_req=16 ttl=64 time=3.43 ms
64 bytes from 192.168.1.1: icmp_req=17 ttl=64 time=5.96 ms
64 bytes from 192.168.1.1: icmp_req=18 ttl=64 time=4.67 ms
64 bytes from 192.168.1.1: icmp_req=19 ttl=64 time=2.66 ms
64 bytes from 192.168.1.1: icmp_req=20 ttl=64 time=0.746 ms
64 bytes from 192.168.1.1: icmp_req=21 ttl=64 time=1.75 ms
64 bytes from 192.168.1.1: icmp_req=22 ttl=64 time=0.619 ms
64 bytes from 192.168.1.1: icmp_req=23 ttl=64 time=1.81 ms
64 bytes from 192.168.1.1: icmp_req=24 ttl=64 time=0.579 ms
64 bytes from 192.168.1.1: icmp_req=25 ttl=64 time=1.57 ms
64 bytes from 192.168.1.1: icmp_req=26 ttl=64 time=9.68 ms
64 bytes from 192.168.1.1: icmp_req=27 ttl=64 time=8.57 ms
64 bytes from 192.168.1.1: icmp_req=28 ttl=64 time=2.93 ms
64 bytes from 192.168.1.1: icmp_req=29 ttl=64 time=5.81 ms
64 bytes from 192.168.1.1: icmp_req=30 ttl=64 time=4.67 ms
64 bytes from 192.168.1.1: icmp_req=31 ttl=64 time=1.86 ms
64 bytes from 192.168.1.1: icmp_req=32 ttl=64 time=1.50 ms
64 bytes from 192.168.1.1: icmp_req=33 ttl=64 time=9.72 ms
64 bytes from 192.168.1.1: icmp_req=34 ttl=64 time=7.58 ms
64 bytes from 192.168.1.1: icmp_req=35 ttl=64 time=7.29 ms
64 bytes from 192.168.1.1: icmp_req=36 ttl=64 time=5.72 ms
64 bytes from 192.168.1.1: icmp_req=37 ttl=64 time=3.74 ms
64 bytes from 192.168.1.1: icmp_req=38 ttl=64 time=1.58 ms
64 bytes from 192.168.1.1: icmp_req=39 ttl=64 time=9.71 ms
64 bytes from 192.168.1.1: icmp_req=40 ttl=64 time=8.56 ms
64 bytes from 192.168.1.1: icmp_req=41 ttl=64 time=6.66 ms
64 bytes from 192.168.1.1: icmp_req=42 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_req=43 ttl=64 time=3.52 ms
64 bytes from 192.168.1.1: icmp_req=44 ttl=64 time=1.74 ms
64 bytes from 192.168.1.1: icmp_req=45 ttl=64 time=8.04 ms
64 bytes from 192.168.1.1: icmp_req=46 ttl=64 time=8.44 ms
64 bytes from 192.168.1.1: icmp_req=47 ttl=64 time=6.67 ms
64 bytes from 192.168.1.1: icmp_req=48 ttl=64 time=4.70 ms
64 bytes from 192.168.1.1: icmp_req=49 ttl=64 time=2.70 ms
64 bytes from 192.168.1.1: icmp_req=50 ttl=64 time=0.681 ms
64 bytes from 192.168.1.1: icmp_req=51 ttl=64 time=1.69 ms
64 bytes from 192.168.1.1: icmp_req=52 ttl=64 time=1.60 ms
64 bytes from 192.168.1.1: icmp_req=53 ttl=64 time=8.23 ms
64 bytes from 192.168.1.1: icmp_req=54 ttl=64 time=6.99 ms
64 bytes from 192.168.1.1: icmp_req=55 ttl=64 time=4.58 ms
64 bytes from 192.168.1.1: icmp_req=56 ttl=64 time=4.25 ms
64 bytes from 192.168.1.1: icmp_req=57 ttl=64 time=0.531 ms
64 bytes from 192.168.1.1: icmp_req=58 ttl=64 time=3.71 ms
64 bytes from 192.168.1.1: icmp_req=59 ttl=64 time=1.71 ms
64 bytes from 192.168.1.1: icmp_req=60 ttl=64 time=3.66 ms
64 bytes from 192.168.1.1: icmp_req=61 ttl=64 time=0.878 ms
64 bytes from 192.168.1.1: icmp_req=62 ttl=64 time=6.57 ms
64 bytes from 192.168.1.1: icmp_req=63 ttl=64 time=4.64 ms
64 bytes from 192.168.1.1: icmp_req=64 ttl=64 time=2.69 ms
^C
--- 192.168.1.1 ping statistics ---
64 packets transmitted, 64 received, 0% packet loss, time 63086ms
rtt min/avg/max/mdev = 0.531/4.293/10.025/2.786 ms
stu@stu-NC10:~$ ^C
stu@stu-NC10:~$

The Netbook was the only device connected as well so no idea what is going on with it now.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top