latency troubleshooting

[Graham Vincent]

Hello.

We got switched over to Orcon UBS last week and things are looking
pretty good. The main reason for moving was to try and resolve high ping
times for my son's gaming so I was disappointed when he told me his ping
was still worse than his friends.

A quick traceroute however shows the problem now seems to be either on
my linux firewall/masquerading box or the DSE XH1149 (latest firmware)
router:

traceroute to 203.96.92.75 (203.96.92.75), 30 hops max, 38 byte packets
1 firewall (192.168.1.1) 0.502 ms 0.313 ms 0.306 ms
2 router (192.168.2.1) 75.613 ms 73.594 ms 73.948 ms
3 219.88.242.171 (219.88.242.171) 77.973 ms 76.143 ms 77.859 ms
4 fe-ape-core.nct.orcon.net.nz (219.88.242.252) 76.092 ms 77.251 ms
75.990 ms
5 xtra.ape.net.nz (192.203.154.60) 80.124 ms 80.816 ms 77.892 ms
6 v512.XTRAK1-B1.xtra.co.nz (202.27.176.225) 80.043 ms 79.277 ms
78.150 ms
7 tribes2.games.xtra.co.nz (203.96.92.75) 81.825 ms 79.317 ms 78.004 ms

Can anyone help me out with some information on what a typical response
time from the XH1149 is and any suggestions for identifying how long
packets are taking to get through each part of my firewall i.e. in
through eth0, through the firewall program and then out through eth1 to
the router?

Thanks,

Graham

[Brian Gibbons]

Post by Graham Vincent
A quick traceroute however shows the problem now seems to be either on
my linux firewall/masquerading box or the DSE XH1149 (latest firmware)
traceroute to 203.96.92.75 (203.96.92.75), 30 hops max, 38 byte packets
1 firewall (192.168.1.1) 0.502 ms 0.313 ms 0.306 ms
2 router (192.168.2.1) 75.613 ms 73.594 ms 73.948 ms

That's fairly bizzare...

Post by Graham Vincent
3 219.88.242.171 (219.88.242.171) 77.973 ms 76.143 ms 77.859 ms

However the jump in latency across the DSL is only a few milliseconds, this
suggests your traceroute is not accurate.

What result do you get if you ping each of the hops?

Perhaps connect directly to the router then tracerroute.

Cheers

BG