Wed Jul 24, 2013 10:55 pm
That seems a bit high, but increased ping times can be caused by a lot of different things. Are you sure there is no congestion in your network and that the RouterBoard is not under heavy load? Also, did you have similar ping times on 6.1? 6.2 is still pre-release as far as I know, so it probably shouldn't be used unless it fixes an important problem for you or you're just testing it for fun.
I'm running the 6.2 pre-release on a 493G at home which is routing between a couple of VLANs and doing some very basic firewalling. No ping issues here. My computer connects to a VLAN-aware gigabit switch, which in turn connects to the RouterBoard.
PING 172.20.10.1 (172.20.10.1) 56(84) bytes of data.
64 bytes from 172.20.10.1: icmp_req=1 ttl=64 time=0.224 ms
64 bytes from 172.20.10.1: icmp_req=2 ttl=64 time=0.197 ms
64 bytes from 172.20.10.1: icmp_req=3 ttl=64 time=0.200 ms
64 bytes from 172.20.10.1: icmp_req=4 ttl=64 time=0.177 ms
64 bytes from 172.20.10.1: icmp_req=5 ttl=64 time=0.184 ms
64 bytes from 172.20.10.1: icmp_req=6 ttl=64 time=0.186 ms
64 bytes from 172.20.10.1: icmp_req=7 ttl=64 time=0.207 ms
64 bytes from 172.20.10.1: icmp_req=8 ttl=64 time=0.185 ms
64 bytes from 172.20.10.1: icmp_req=9 ttl=64 time=0.192 ms
64 bytes from 172.20.10.1: icmp_req=10 ttl=64 time=0.209 ms
64 bytes from 172.20.10.1: icmp_req=11 ttl=64 time=0.174 ms
64 bytes from 172.20.10.1: icmp_req=12 ttl=64 time=0.186 ms
64 bytes from 172.20.10.1: icmp_req=13 ttl=64 time=0.154 ms
64 bytes from 172.20.10.1: icmp_req=14 ttl=64 time=0.206 ms
64 bytes from 172.20.10.1: icmp_req=15 ttl=64 time=0.207 ms
64 bytes from 172.20.10.1: icmp_req=16 ttl=64 time=0.197 ms
64 bytes from 172.20.10.1: icmp_req=17 ttl=64 time=0.170 ms
^C
--- 172.20.10.1 ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 15997ms
rtt min/avg/max/mdev = 0.154/0.191/0.224/0.021 ms