[KM]Pugless wrote:
Tracing route to 212.187.246.114 over a maximum of 30 hops

1 182 ms 87 ms 130 ms 217.47.250.186
2 188 ms 230 ms 255 ms 217.47.200.161
3 110 ms 87 ms 249 ms 217.41.170.17
4 62 ms 76 ms 15 ms 217.41.170.114
5 147 ms 228 ms 220 ms 217.41.170.34
6 204 ms 116 ms 40 ms 213.120.192.90
7 83 ms 31 ms 38 ms core1-pos6-1.ilford.ukcore.bt.net [194.72.20.197
]
8 339 ms 470 ms 280 ms transit2-pos5-0.ilford.ukcore.bt.net [194.72.20.
154]
9 80 ms 17 ms 103 ms t2c2-p3-0.uk-ilf.eu.bt.net [166.49.168.105]
10 163 ms 126 ms 77 ms 195.50.91.117
11 212 ms 21 ms 154 ms ge-11-0.ipcolo2.London1.Level3.net [4.68.116.42]

12 69 ms 41 ms 21 ms 212.187.246.114

Trace complete.

Dunno what thats all about, good or bad, maybe you mite be able to shed some light on it

Very interesting trace indeed... Your ping is random throughout, it oscillates from almost 500 ms to 15 ms...

I looked up the IPs, and they look... Hm...

1 182 ms 87 ms 130 ms BT MIDBAND IP
2 188 ms 230 ms 255 ms BT MIDBAND IP
3 110 ms 87 ms 249 ms BT MIDBAND IP
4 62 ms 76 ms 15 ms BT MIDBAND IP
5 147 ms 228 ms 220 ms BT MIDBAND IP
6 204 ms 116 ms 40 ms BT MIDBAND IP
7 83 ms 31 ms 38 ms BT, Hertfordshire
8 339 ms 470 ms 280 ms BT, Hertfordshire
9 80 ms 17 ms 103 ms BT, Amsterdam (!!!)
10 163 ms 126 ms 77 ms Level3
11 212 ms 21 ms 154 ms Level3, London
12 69 ms 41 ms 21 ms Final Destination

This is obviously a shit route. Going to Europe and back, WTF?

2 Frog, can this be because you block tracert, or maybe this is BT fucking up?

2 Pug, it is almost certain that the problem is in your Internet connection. You also mentioned high choke. This might be the case... Try tracing two more IPs and paste them like you did with this one.

Try:

tracert bbc.co.uk
tracert 194.72.20.197

Then to do:

ping bbc.co.uk
ping 212.187.246.114
ping 194.72.20.197

For ping commands just paste the summary, no need for the whole table.

Post edited by: sneg_, at: 20/03/2006 12:15

I always wanted to go to amsterdam, but leave me ping at home and go there meself.

Is this defult route then, is there no way you can change the it at all?

The route is determined by the network equipment BT sets up and controls. Do the traces I mentioned above, just to see whether you have the same problem for any address or it's only KM server.

The only way to change the route is phone up BT and tell them that you are experiencing problems connecting to a server.

We had a guy in Ukraine with 2 Mbit/s who was having 500 ms ping on a server, which is 15 mins walk from him. In the end it turned out he was connecting to it through Sweden...

Post edited by: sneg_, at: 20/03/2006 12:19

Here is another server


Tracing route to 212.187.209.43 over a maximum of 30 hops

1 16 ms 17 ms 17 ms 217.47.250.186
2 135 ms 226 ms 181 ms 217.47.250.161
3 231 ms 79 ms 17 ms 217.41.170.21
4 98 ms 15 ms 81 ms 217.41.170.65
5 140 ms 68 ms 33 ms 217.41.170.114
6 153 ms 93 ms 32 ms 213.123.78.34
7 19 ms 17 ms 93 ms 217.47.23.58
8 58 ms 21 ms 19 ms core2-pos-3-1.ilford.ukcore.bt.net [194.72.20.18
2]
9 16 ms 17 ms 25 ms transit2-pos6-0.ilford.ukcore.bt.net [194.72.20.
158]
10 38 ms 15 ms 15 ms t2c2-p3-0.uk-ilf.eu.bt.net [166.49.168.105]
11 119 ms 107 ms 85 ms 195.50.91.117
12 22 ms 24 ms 91 ms ge-11-0.ipcolo2.London1.Level3.net [4.68.116.42]

13 80 ms 34 ms 87 ms 212.187.209.43

Trace complete.

Yep, once you ping Level3 address it goes through Amsterdam. Moreover, the latency throughout this route is very unstable.

Get your ISPs customer support e-mail. Stick a trace route like this into it and say that this happens for any server in London (on Level3). Say that this cannot be tolerated and you want something to be done. Hopefully, they will respond and fix this.

P.S. It is very hard to read trace route table in text, screenshot your command line prompt, cut out the window and stick it into your e-mail as an attachment. That will make it much more readable, and admins will be much more willing to help.

Post edited by: sneg_, at: 20/03/2006 12:55

cheers, for that, i'll get on there case and see if they can sort it.

One last thing, when i got my new connection with BT, i was given a router, but i had problems with it dloading stuff, so i scrapped that and went back to my old speedtouch modem what wanadoo gave me when i was with them. This wouldnt be a cause of anything wud it?

Now, that is a useful detail you have decided to mention right in the end. ^_^

How come it actually works?

Modem is a device that transforms digital signals into analogue and vice versa, so that they can be carried across a telephone line (and back).

Router is a network device that routes several computers together, so that when one computer requests a connection with another one, that connection is _routed_ to the right machine.

Are you sure you are using a modem? Even the wires you plug-in to a router and a modem are different.

I recon before contacting BT try to connect the device they provided and try to play. If the lag disappears... Then you are done. ^_^ Don't worry about download problems, I can help you set up your router so that you can use p2p at full speed. We can do that over MSN.

If the lag is still there... Then it is time contact BT. ^_^

Post edited by: sneg_, at: 20/03/2006 13:39

The router BT gave me has got ethernet and usb outputs on it, so it can connect to me comp with either, as me MB supports ethernet i used it throught that before.

To be honest, when the router was given me probs i thought there is no harm trying me old modem and it worked, i didnt think it would work.

BT gave me BT voyager 2091 wirless adsl router.

The modem what wannado gave me is a Thomson speedtouch 330.

I'll give the router a go, no harm in trying just gotta reinstall drivers and shit for it.

Done that trace test thingy again, this time with BT router, looks a lot different.......


Tracing route to 212.187.246.114 over a maximum of 30 hops

1 1 ms <1 ms 3 ms voyager.home [192.168.1.1]
2 18 ms 15 ms 19 ms 217.47.250.186
3 20 ms 17 ms 19 ms 217.47.200.161
4 17 ms 17 ms 21 ms 217.41.170.17
5 20 ms 23 ms 32 ms 217.41.170.122
6 19 ms 18 ms 16 ms 213.123.78.34
7 16 ms 16 ms 17 ms 217.47.23.42
8 26 ms 17 ms 16 ms core1-pos-3-1.ilford.ukcore.bt.net [194.72.20.17
8]
9 17 ms 17 ms 15 ms transit2-pos3-0.ilford.ukcore.bt.net [194.72.20.
250]
10 18 ms 16 ms 17 ms t2c2-p5-0.uk-ilf.eu.bt.net [166.49.168.109]
11 18 ms 18 ms 22 ms 195.50.91.117
12 19 ms 19 ms 18 ms ge-11-0.ipcolo2.London1.Level3.net [4.68.116.42]

13 19 ms 19 ms 19 ms 212.187.246.114

Trace complete.

Post edited by: [KM]Pugless, at: 20/03/2006 14:21

The speedtouch is an ADSL modem, as in in converts the ADSL signal into USB2.0.. nothing wrong with the speedtouch 330, we were using one until we got a PCI card.. mind you, a bitch to set up in linux..

Will

With speedtouch 330

Tracing route to 212.187.246.114 over a maximum of 30 hops

1 182 ms 87 ms 130 ms 217.47.250.186
2 188 ms 230 ms 255 ms 217.47.200.161
3 110 ms 87 ms 249 ms 217.41.170.17
4 62 ms 76 ms 15 ms 217.41.170.114
5 147 ms 228 ms 220 ms 217.41.170.34
6 204 ms 116 ms 40 ms 213.120.192.90
7 83 ms 31 ms 38 ms core1-pos6-1.ilford.ukcore.bt.net [194.72.20.197
]
8 339 ms 470 ms 280 ms transit2-pos5-0.ilford.ukcore.bt.net [194.72.20.
154]
9 80 ms 17 ms 103 ms t2c2-p3-0.uk-ilf.eu.bt.net [166.49.168.105]
10 163 ms 126 ms 77 ms 195.50.91.117
11 212 ms 21 ms 154 ms ge-11-0.ipcolo2.London1.Level3.net [4.68.116.42]

12 69 ms 41 ms 21 ms 212.187.246.114

Trace complete.

With BT Voyager 2091

Tracing route to 212.187.246.114 over a maximum of 30 hops



1 1 ms <1 ms 3 ms voyager.home [192.168.1.1]
2 18 ms 15 ms 19 ms 217.47.250.186
3 20 ms 17 ms 19 ms 217.47.200.161
4 17 ms 17 ms 21 ms 217.41.170.17
5 20 ms 23 ms 32 ms 217.41.170.122
6 19 ms 18 ms 16 ms 213.123.78.34
7 16 ms 16 ms 17 ms 217.47.23.42
8 26 ms 17 ms 16 ms core1-pos-3-1.ilford.ukcore.bt.net [194.72.20.178]
9 17 ms 17 ms 15 ms transit2-pos3-0.ilford.ukcore.bt.net [194.72.20.250]
10 18 ms 16 ms 17 ms t2c2-p5-0.uk-ilf.eu.bt.net [166.49.168.109]
11 18 ms 18 ms 22 ms 195.50.91.117

12 19 ms 19 ms 18 ms ge-11-0.ipcolo2.London1.Level3.net [4.68.116.42]

13 19 ms 19 ms 19 ms 212.187.246.114



Trace complete.

What looks better to you???

Post edited by: [KM]Pugless, at: 20/03/2006 14:35

212.187.246.114 is hosted in london and you can ping/tracert it fine...

you seam to pay attention in your networking lessons

domestic (home) routers nearly all have modems built in.... so when he talks about a router, hes talking about a modem aswel

very few people have the old school v90- now

the lower the ms, the better your ping...

and that last trace has some nice low ms

I had SHDSL modem at home, which had to be connected to a switch in my flat. So I thought he is talking about one of those. Then the admins got rid of it and connected me straight to one of their switches, so I had my switch plugged-in to one of theirs directly. ;P Thanks, Frog, never had networking lessons, lol. ^_^

Pug, the last route (with Voyager) is much-much better. Contact me on MSN this evening and we will set your Voyager up so you can use p2p.

It is hard to say why your Speedtouch didn't work as intended. There are too many reasons I can think of, and I don't think I can explain them properly. ^_^

Congratulations on solving your lag, Pug. Hopefully I see you on the servers soon.

P.S. It still goes to Amsterdam. ^^ Who cares, though? ^_~''

Post edited by: sneg_, at: 20/03/2006 18:28

Cheers for all your help, hopefully that shud of sorted it out, well it better have, looks promising anyway. I'll be in touch later as i do need p2p as i watch a bit of live footy on the net.