NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PowerConnect 2816
Seems to be working fine though for some reason I am still unable to ping it with jumbo frame-sized packets... any idea from other 28xx users?
2 Replies
- OK, so it so far does not work with any oversized packet...
Now the only setting on my switch' web UI mgmt page is under Advanced Settings/General is Enable or Disable JF at next boot; currently it's on. - Weird. Sometimes it's working one way then stops...
naspro:/c# ping -s 9000 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 9000(9028) bytes of data.
9008 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=2.11 ms
9008 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=2.16 ms
9008 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=2.14 ms
9008 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=2.19 ms
9008 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=1.41 ms
9008 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=2.11 ms
9008 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=2.15 ms
9008 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=2.18 ms
9008 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=2.17 ms
9008 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=1.53 ms
9008 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=2.33 ms
9008 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=1.50 ms
^C
--- 192.168.1.2 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11012ms
rtt min/avg/max/mdev = 1.412/2.003/2.333/0.304 ms
Time to give up, almost 4AM - I'll call Dell tomorrow morning.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
