NTL lag

S

Sharma

Guest
Connection still experiances massive packetloss, im gonna ave to mail merge a massive rant to those addresses listed earlier
 
T

tris-

Guest
i think they are taking the piss or something, i have a feeling they arnt gonna do jack shit about it. but the thing is level of serviceis not guaranteed so we cant take them to court or complain to anyone else etc :rolleyes:
 
T

TocaTank

Guest
write to a magazine ?

Pczone or sommit...ive sent three emails to different peeps, sprint, cablemodem ntl, and to another. Or was that my porn subscription :eek:

ahh well, hope it gets resolved soon.
 
T

tanoin

Guest
I'm getting massive packet loss on NTL, i've put in a question on Rightnow but i'm not sure what else i can do... the problem seems to be with the Opentransit routers in france, but for now this game is unplayable for me.
 
D

darbey

Guest
Anyone else got any ideas? While were on might be handy if u can post your ping/traceroutes/pingplots on here so we can compare. Il post mine when i get home.
This whole affair is really starting to piss me off.
 
S

spydor

Guest
OK the main 2 bad routers for me are:
193.251.241.118 <- 20 to 40% PacetLoss.
193.252.122.10 <- 30 to 50% PacketLoss.

I have done a "whois" to see who owns these routers and have managed to get contact email addresses.

The first is owned by opentransit & frenchtelecom (part of same franchise I think), e-mail Addresses are:

info.europe@francetelecom.com
admin@opentransit.net

The Second is owned by Wanadooportails who own the last router before the game server (193.252.122.10) & the gameserver one itself. email Address is:

noc@wanadooportails.com


I have sent e-mails with Traces to all of these addresses, I suggest others with problems do the same.
 
F

F.I.V

Guest
193.251.241.169 - P13-0.PASCR2.Pastourelle.opentransit.net = 50% Packetloss

193.251.241.97 - P11-0.PASCR1.Pastourelle.opentransit.net = 20% Packetloss

193.251.241.118 - P4-0.BAGCR3.Bagnolet.opentransit.net = 50% Packetloss

193.252.122.10 - ----------- = 50% Packetloss

So basically, I'm fucked :(

Definately seems like it's Opentransit tho, whatever bullshit they claim
 
F

F.I.V

Guest
Here's that in tech language ;)

Target Name: N/A
IP: 193.252.123.33
Date/Time: 27/04/2003 16:23:15 to 27/04/2003 16:25:30

1 10 ms 6 ms 39 ms 10 ms 21 ms 8 ms 8 ms 11 ms 7 ms 7 ms [10.110.16.1]
2 94 ms 18 ms 14 ms 7 ms 7 ms 9 ms 7 ms 7 ms 7 ms 13 ms oldh-t2cam1-a-ge-wan42-112.inet.ntl.com [80.5.164.49]
3 74 ms 9 ms 8 ms 7 ms 35 ms 50 ms 46 ms 10 ms 12 ms 111 ms man-t2core-a-ge-wan62.inet.ntl.com [213.104.242.41]
4 66 ms 8 ms 7 ms 17 ms 24 ms 43 ms 33 ms 9 ms 7 ms 11 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
5 46 ms 12 ms 11 ms 8 ms 25 ms 15 ms 8 ms 8 ms 8 ms 13 ms man-bb-b-ge-220-0.inet.ntl.com [62.253.187.178]
6 42 ms 32 ms 35 ms 26 ms 21 ms 16 ms 19 ms 15 ms 16 ms 19 ms [213.206.159.245]
7 18 ms 29 ms 26 ms 30 ms 37 ms 30 ms 24 ms 22 ms 16 ms 44 ms sl-bb20-lon-11-0.sprintlink.net [213.206.128.56]
8 38 ms 23 ms 25 ms 22 ms 56 ms 26 ms 42 ms 34 ms 22 ms 23 ms sl-bb21-par-14-0.sprintlink.net [213.206.129.70]
9 26 ms 23 ms 30 ms 23 ms 43 ms 27 ms 28 ms 24 ms 21 ms 23 ms sl-gw10-par-15-0.sprintlink.net [217.118.224.42]
10 43 ms 23 ms 35 ms 24 ms 23 ms 40 ms 24 ms 23 ms 22 ms 55 ms sle-franc1-1-0.sprintlink.net [213.206.131.42]
11 * 28 ms * 27 ms 41 ms 37 ms 35 ms * 37 ms 47 ms P13-0.PASCR2.Pastourelle.opentransit.net [193.251.241.169]
12 * 27 ms 28 ms 30 ms 30 ms 36 ms 43 ms 35 ms 27 ms 27 ms P11-0.PASCR1.Pastourelle.opentransit.net [193.251.241.97]
13 * * * 91 ms 44 ms 53 ms * 47 ms 27 ms 57 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
14 28 ms 43 ms 23 ms 79 ms 31 ms 30 ms 24 ms 33 ms 27 ms 45 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
15 39 ms 24 ms 23 ms 52 ms 23 ms 24 ms 23 ms 50 ms 25 ms 24 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
16 31 ms * 29 ms 52 ms 36 ms * * 42 ms 33 ms * [193.252.122.10]
17 34 ms 45 ms 28 ms 49 ms 52 ms 43 ms 28 ms 37 ms 31 ms 30 ms [193.252.123.33]

Ping statistics for 193.252.123.33
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 28ms, Maximum = 52ms, Average = 37ms
 
T

Tyrant I

Guest
Im still totally fookered here.. .. paid upfront 3 months subs too :( emailed all the above mentioned .. .fingers crossed
 
T

tris-

Guest
its NOT opentransit, its NTLs router

ren-bb-b-ge-730-0.inet.ntl.com

when they ping back the packet loss is at this router, PLUS there is people with this problem who dont even play this game OR are routed through opentransit, it IS ntls problem.


yes ping plotter will show packetloss at opentransits router because the information is coming back through them and the router infront of it thinks this is where the packetloss is and so pingplotter will show packetloss here.
 
D

dropkick

Guest
Ping the ntlhellworld site and you see the 2 ntl servers that has packet loss
 
T

tris-

Guest
anyone want to phone NTL then because that IP IS in their network.

edit: someone is telling me packetloss starts at bre-bb-b-so-200-0.inet.ntl.com now and the ren one is ok
 
T

tris-

Guest
my trace to nthell world

C:\WINDOWS>tracert nthellworld.com

Tracing route to nthellworld.com [62.253.167.55]
over a maximum of 30 hops:

1 7 ms 7 ms 29 ms 10.141.7.254
2 14 ms 11 ms 27 ms midd-t2cam1-b-v106.inet.ntl.com [213.106.238.177
]
3 27 ms 18 ms 39 ms mid-t2core-b-ge-wan61.inet.ntl.com [213.106.237.
161]
4 12 ms 15 ms 16 ms ren-bb-b-so-220-0.inet.ntl.com [62.253.187.93]
5 * 10 ms 23 ms ren-bb-a-ge-730-0.inet.ntl.com [62.253.185.189]

6 43 ms * 57 ms bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]

7 76 ms 28 ms 27 ms win-bb-a-so-400-0.inet.ntl.com [213.105.172.233]

8 24 ms 28 ms 28 ms win-dc-a-v900.inet.ntl.com [62.253.188.162]
 
T

Tenko

Guest
Ok heres my trace, I dont know how to use these things as Im a bit of a tech noob but OOH LOOK!


Target Name: N/A
IP: 193.252.123.33
Date/Time: 27/04/2003 18:35:04

(Results for 30 traces)

1) 7 ms 7 ms 8 ms 9 ms 7 ms 7 ms 7 ms 7 ms 32 ms 11 ms 25 ms 8 ms 7 ms 7 ms 8 ms 8 ms 7 ms 7 ms 8 ms 7 ms 36 ms 7 ms 20 ms 7 ms 6 ms 7 ms 59 ms 20 ms 6 ms 7 ms [######]



2) 9 ms 12 ms 8 ms 33 ms 10 ms 7 ms 26 ms 40 ms 48 ms 10 ms 75 ms 8 ms 8 ms 8 ms 13 ms 7 ms 12 ms 8 ms 9 ms 11 ms 14 ms 12 ms 8 ms 7 ms 8 ms 9 ms 33 ms 8 ms 15 ms 6 ms

oldh-t2cam1-b-ge-wan43-116.inet.ntl.com [80.5.164.193]



3) 8 ms 34 ms 11 ms 9 ms 31 ms 62 ms 8 ms 16 ms 23 ms 8 ms 48 ms 7 ms 8 ms 12 ms 7 ms 7 ms 9 ms 19 ms 7 ms 9 ms 7 ms 8 ms 7 ms 27 ms 13 ms 10 ms 8 ms 30 ms 10 ms 7 ms

man-t2core-b-ge-wan62.inet.ntl.com [213.104.242.169]



4 ) 9 ms 15 ms 7 ms 7 ms 14 ms 41 ms 8 ms 21 ms 45 ms 8 ms 23 ms 48 ms 10 ms 8 ms 8 ms 30 ms 9 ms 9 ms 8 ms 7 ms 8 ms 10 ms 14 ms 8 ms 48 ms 38 ms 9 ms 8 ms 9 ms 8 ms

man-bb-b-so-210-0.inet.ntl.com [62.253.184.61]



5 ) 30 ms 30 ms 16 ms 71 ms 17 ms 22 ms 15 ms 14 ms 26 ms 16 ms 20 ms 44 ms 16 ms 15 ms 16 ms 15 ms 33 ms 15 ms 19 ms 17 ms 15 ms 19 ms 19 ms 15 ms 28 ms 18 ms 50 ms 15 ms 14 ms 16 ms

[213.206.159.245]



6 ) 21 ms 14 ms 15 ms 46 ms 14 ms 15 ms 15 ms 15 ms 16 ms 15 ms 33 ms 18 ms 16 ms 43 ms 16 ms 15 ms 19 ms 19 ms 15 ms 22 ms 18 ms 15 ms 15 ms 47 ms 16 ms 18 ms 25 ms 55 ms 17 ms 16 ms sl-bb20-lon-11-0.sprintlink.net [213.206.128.56]

7 ) 22 ms 22 ms 21 ms 26 ms 22 ms 21 ms 23 ms 22 ms 61 ms 23 ms 71 ms 37 ms 21 ms 23 ms 24 ms 25 ms 22 ms 22 ms 49 ms 21 ms 22 ms 26 ms 21 ms 27 ms 35 ms 21 ms 23 ms 40 ms 23 ms 22 ms

sl-bb21-par-14-0.sprintlink.net [213.206.129.70]



8 ) 49 ms 23 ms 28 ms 24 ms 24 ms 22 ms 24 ms 23 ms 35 ms 60 ms 49 ms 23 ms 54 ms 23 ms 37 ms 24 ms 23 ms 24 ms 24 ms 23 ms 24 ms 23 ms 61 ms 25 ms 23 ms 29 ms 29 ms 23 ms 24 ms 24 ms

sl-gw10-par-15-0.sprintlink.net [217.118.224.42]



9 ) 44 ms 23 ms 25 ms 24 ms 41 ms 24 ms 30 ms 23 ms 27 ms 34 ms 22 ms 25 ms 27 ms 23 ms 24 ms 23 ms 24 ms 25 ms 22 ms 24 ms 25 ms 25 ms 34 ms 43 ms 29 ms 31 ms 30 ms 26 ms 23 ms 27 ms

sle-franc1-1-0.sprintlink.net [213.206.131.42]



10 ) 24 ms 25 ms 62 ms 23 ms 27 ms 28 ms 25 ms 23 ms 24 ms 23 ms 36 ms 29 ms 25 ms 22 ms 29 ms 24 ms 26 ms 24 ms 27 ms 70 ms 26 ms 29 ms 29 ms 23 ms 23 ms 23 ms 24 ms 23 ms 22 ms 76 ms

P13-0.PASCR2.Pastourelle.opentransit.net [193.251.241.169]



11) 23 ms 32 ms 38 ms 24 ms 24 ms 25 ms 24 ms 26 ms 25 ms 24 ms 23 ms 52 ms 24 ms 39 ms 24 ms 22 ms 24 ms 27 ms 23 ms 43 ms 24 ms 28 ms 26 ms 23 ms 45 ms 22 ms 25 ms 23 ms 27 ms 50 ms

P11-0.PASCR1.Pastourelle.opentransit.net [193.251.241.97]



12) 42 ms 23 ms 24 ms 40 ms 58 ms 22 ms 23 ms 22 ms 27 ms 23 ms 23 ms 28 ms 23 ms 35 ms 30 ms 22 ms 24 ms 24 ms 23 ms 30 ms 35 ms 23 ms 23 ms 26 ms 31 ms 23 ms 27 ms 23 ms 23 ms 24 ms

P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]



13) 32 ms 28 ms 32 ms 30 ms 38 ms 37 ms 30 ms 64 ms 28 ms 27 ms * 34 ms 27 ms 30 ms 38 ms 65 ms 32 ms 27 ms 27 ms * 26 ms 65 ms 26 ms * 39 ms 39 ms 27 ms * 26 ms 30 ms

P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]



14) 32 ms 35 ms 33 ms 34 ms 35 ms 33 ms 28 ms 46 ms * 27 ms 34 ms 32 ms * * 27 ms 41 ms * 35 ms 30 ms 49 ms 34 ms 32 ms * 34 ms 29 ms 27 ms 34 ms * 27 ms 35 ms

WanadooPortails1.GW.opentransit.net [193.251.251.58]



15 ) 31 ms 28 ms 69 ms 24 ms 33 ms 30 ms 43 ms 53 ms 23 ms 25 ms 25 ms 27 ms 23 ms 24 ms 32 ms 26 ms 30 ms 27 ms 24 ms 25 ms 24 ms 31 ms 24 ms 31 ms 24 ms 66 ms 25 ms 24 ms 24 ms 24 ms

[193.252.122.10]



16 ) 35 ms 36 ms * 29 ms 27 ms 36 ms * 31 ms 29 ms 54 ms 28 ms 28 ms 70 ms 37 ms 33 ms * 42 ms 27 ms 37 ms 27 ms 29 ms 29 ms 92 ms * 39 ms * 33 ms * 37 ms 32 ms

[193.252.123.33]



Now packet loss varied overtime, though the averages are high they on occasion hit 100% (think thats the * above).

I don't know didly squat about all this but what it means in respect to DAoC is tha the game is nearly unplayable even though I've not had an LD yet.

edited for legibility
 
T

tris-

Guest
if your going to report to NTL, its best to trace to nthellworld.com because then its staying in NTLs network and there is no one else to blame.
 
T

Tenko

Guest
Well to nthellworld its no where near as bad...


Target Name: nthellworld.com
IP: 62.253.167.55
Date/Time: 27/04/2003 18:57:12

1) 12 ms 6 ms 12 ms 12 ms 7 ms 6 ms 7 ms 7 ms 11 ms 6 ms 11 ms 7 ms 11 ms 7 ms 8 ms [######]


2) 8 ms 13 ms 7 ms 7 ms 7 ms 10 ms 9 ms 13 ms 6 ms 8 ms 8 ms 7 ms 8 ms 10 ms 9 ms oldh-t2cam1-b-ge-wan43-116.inet.ntl.com [80.5.164.193]

3) 11 ms 8 ms 32 ms 9 ms 57 ms 17 ms 7 ms 8 ms 7 ms 13 ms 8 ms 7 ms 11 ms 9 ms 9 ms man-t2core-b-ge-wan62.inet.ntl.com [213.104.242.169]

4) 7 ms 29 ms 9 ms 12 ms 29 ms 8 ms 13 ms 8 ms 11 ms 9 ms 9 ms 8 ms 7 ms 14 ms 8 ms man-bb-b-so-210-0.inet.ntl.com [62.253.184.61]

5) 15 ms 14 ms 13 ms 13 ms 13 ms 28 ms 14 ms 13 ms 15 ms 17 ms 15 ms 16 ms 14 ms 14 ms 14 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

6) 43 ms 14 ms 15 ms 13 ms 13 ms 12 ms 17 ms 14 ms 51 ms 17 ms 14 ms 15 ms 17 ms 14 ms 17 ms win-dc-a-v900.inet.ntl.com [62.253.188.162]
 
T

tris-

Guest
hmmm your going through dif routers, i have to go through ren and bre to get to nthellworld
 
S

Sharma

Guest
n3wbie, your sig quote does more than enough to describe NTL in 4 words
 
T

tris-

Guest
anyone any luck yet? there is someone on NTHell who doesnt play DAOC but got the same prob. he managed to tell them the router names and they say they will phone him back. :rolleyes:
 
S

spydor

Guest
Sounds promising newbie - think I've had 50 LD's today :(

Cant fight with pet, at this rate I'm gunna be a master spellcrafter :p
 
T

tris-

Guest
can also try to phone - 01483 875105 which is direct to their network managment centre, i tryed all weekend but no answer but i will try tomorrow.
 
F

F.I.V

Guest
I hope you have better luck than I have n3wbie m8, like talking to a brick wall when you talk to half of the people that work at NTL.
 
T

tris-

Guest
i give up with tech support incase my ears bleed from all their bull shit :(
 
T

tris-

Guest
some bod in chat room has phoned the operations centre he said " they are aware, fighting, fixing but if its a big job dont except anything soon, it might need doing in a scheduled maintenance" so nowt to do but sit and wait :/
 
L

Lanquid

Guest
My pingplotter investigations

Have tried connecting via modem to Daoc no problem.

However with my NTL cable connection from Stockport (near Manchester UK) which routes via opentransit.net I get bad packet loss.


I have a number of traces of pingplotter which might be of interest.


Pingplot to goa:
http://www.hazel-grove.net/daoc/www.goa.com.png



I reckon its the link between spintlink and opentransit.

pingplot to opentransit
http://www.hazel-grove.net/daoc/www.opentransit.net.png


Just accesing opentransit.net gets massive packet loss so its not GOA this time.


Connection to spintlink.net is perfect
pingplot to spintlink:
http://www.hazel-grove.net/daoc/www.sprint.net.png

Hope this helps those calling the network staff..
 
T

tris-

Guest
http://homepage.ntlworld.com/lesley.bruce1/nthellworld.jpg shows it is 2 routers inside NTLs network.

ren = Renfrew
bre = Brentford

try pinging back from opentransit at -
http://www.opentransit.net/lg.htm
put router as pastourelle-backbone1
click trace and put your IP.

this is what i get -

1 P4-0.PASCR3.Pastourelle.opentransit.net (193.251.241.162) 0 msec 0 msec 0 msec
2 P9-0.PASCR1.Pastourelle.opentransit.net (193.251.129.61) 4 msec 0 msec 0 msec
3 Level.GW.opentransit.net (193.251.240.214) 0 msec 0 msec 0 msec
4 ae0-15.mp1.Paris1.Level3.net (212.73.240.65) [AS 3356] 0 msec 0 msec 4 msec
5 so-3-0-0.mp1.London2.Level3.net (212.187.128.46) [AS 3356] 8 msec 8 msec 8 msec
6 pos4-0.hsipaccess1.London2.Level3.net (212.187.129.250) [AS 3356] 8 msec 12 msec 8 msec
7 195.50.116.134 [AS 3356] 8 msec 12 msec 8 msec
8 ren-bb-a-so-100-0.inet.ntl.com (62.253.185.165) [AS 5089] 20 msec 24 msec 20 msec
9 *
ren-bb-b-ge-730-0.inet.ntl.com (62.253.185.190) [AS 5089] 16 msec 16 msec

* = packetloss

starts at renfrew router again, coming BACK from opentransit, same as when i trace an IP in NTL network.
 
L

Lanquid

Guest
Just checked modem connection to one of these routers

getting 14%+ packet loss ping from ren-bb-b-ge-730-0.inet.ntl.com via modem connected via tscali.

However this router pings perfectly from my NTL cable connection.

Looking back on the other traces though, it must be more than just those routers though as my opentransit trace doesnt include them
http://www.hazel-grove.net/daoc/www.opentransit.net.png

Its certainly a mightly difficult mess.
 
T

tris-

Guest
thats because tiscali dont route through that router. when you just ping the renfrew router it says no probs but do a reverse trace or have someone who doesnt route through there and ping it they will see the packetloss. btw traceing to sprintlink.net is ok because its not the same routers.
 

Users who are viewing this thread

Top Bottom