Unplayable ?

O

old.Xanthian

Guest
Is anyone else getting unplayable lag today ?

As soon as I log in I LD :(

Im on 600k NTL Cable, never had probs before.. any one else ?
Is it NTL or shitty GOA ?
 
W

Whoodoo_RD

Guest
Not been on today, but another thread somewhere mentioned the fact his ping to GOA went:

London
Calafornia
London
Paris
London

He was also on NTL world, not sure where i saw the thread, try techie section....
 
T

tris-

Guest
that would be me, im currently having a battle with some techy about what exactly is wrong, because for some reason he doesnt see 50% packet loss as a bad thing :p. join the fun, email ARSystem@above.net and tell them your on NTL world UK getting routed through California.

" I don't see a problem with this traceroute. Is this different routing than your used to seeing? NTL hands the packet to us, that's their routing decision. I'm not sure why that would be an issue. Could you clarify what the issue is? "

Code:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address      | Node Name                                | Location                             | Tzone  | ms | Graph      | Network                                    |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0   |       | 80.6.241.129    | pc2-midd3-3-xxxx.mid.cable.ntl.com    | -                                    |        |    |            | NTL Infrastructure - Middlesbrough         |
| 1   |       | 10.141.7.254    | -                                        | ...                                  |        | 10 | x--        | (private use)                              |
| 2   |       | 213.106.238.49  |xxxxx.inet.ntl.com          | -                                    |        | 8  | x----      | NTL Internet - xxxxx t2core&t2cam |
| 3   |       | 213.106.237.33  | mid-t2core-a-ge-wan61.inet.ntl.com       | -                                    |        | 13 | -x-----    | NTL Internet - xxxx t2core&t2cam |
| 4   |       | 62.253.187.89   | lee-bb-a-so-130-0.inet.ntl.com           | -                                    |        | 10 | x-         | NTL Internet                               |
| 5   |       | 62.253.185.238  | pop-bb-b-so-100-0.inet.ntl.com           | -                                    |        | 15 |  x         | NTL Internet                               |
| 6   |       | 208.185.188.41  | -                                        | ?n Fernando, #1010 San Jose CA 95113 |        | 16 |  x---      | Abovenet Communications, Inc ABOVENET-6    |
| 7   |       | 208.184.231.146 | so-0-0-0.cr2.lhr3.uk.mfnx.net            | ?n Fernando, #1010 San Jose CA 95113 |        | 15 |  x         | Abovenet Communications, Inc ABOVENET-6    |
| 8   |       | 208.185.156.1   | pos3-0.mpr2.lhr1.uk.mfnx.net             | ?n Fernando, #1010 San Jose CA 95113 |        | 16 |  x         | Abovenet Communications, Inc ABOVENET-6    |
| 9   | 10    | 193.251.154.65  | P8-3.LONBB1.London.opentransit.net       | London, UK                           | *      | 17 |  x         | France Telecom Long Distance               |
| 10  | 10    | 193.251.154.225 | P13-0.PASCR1.Pastourelle.opentransit.net | ?---                                 |        | 26 |  -x-       | France Telecom Long Distance               |
| 11  | 10    | 193.251.241.118 | P4-0.BAGCR3.Bagnolet.opentransit.net     | Bagnolet, France                     | +01:00 | 26 |   x        | France Telecom Long Distance               |
| 12  | 10    | 193.251.241.145 | P1-0.BAGBB1.Bagnolet.opentransit.net     | Bagnolet, France                     | +01:00 | 25 |  x-        | France Telecom Long Distance               |
| 13  |       | 193.251.251.58  | WanadooPortails1.GW.opentransit.net      | -                                    |        | 26 |  -x-       | France Telecom Long Distance               |
| 14  |       | 193.252.122.10  | -                                        | ?(France)                            | +01:00 | 26 |   x        | Wanadoo Portails                           |
| 15  | 10    | 193.252.123.24  | -                                        | ?(France)                            | +01:00 | 32 |  -x------- | Wanadoo Portails                           |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to 193.252.123.24, average = 32ms, min = 25ms, max = 117ms -- 22-Oct-02 12:44:19 PM
 
D

Damon_D

Guest
hehe go kick him ;)

All fine here thou , cybercity adsl
 
T

tris-

Guest
heres an update from them -

I'm not showing any packet loss from our network to the destination

the problems look like they are on the return route, when I ping back towards the origin I get pakcet loss to NTL's router 62.253.185.238

the problem is within NTL's network, I can ping cleanly to the other side of our link with them, with no packet loss

I've sent their NOC an e-mail about this packet loss, I'll update you when I hear back from them. You may want to contact them as well, as the routing decision belongs to NTL, they may be able to route your traffic over a different path, until they resolve this.




-------------------------------------------

Really i shouldnt have to sort out different network paths! i just pay to use the damn service.
 
F

FredaOfAxiom

Guest
Having the same issue here... Ran tracer and found the issue with Opentransit IE the French connection :p
 
O

old.Xanthian

Guest
What proggy u using to pull out the tracert reports newbie ?
Im just using shitty MS-Dos ;)
 
W

Whoodoo_RD

Guest
Originally posted by FredaOfAxiom
Having the same issue here... Ran tracer and found the issue with Opentransit IE the French connection :p

FS, its always this one that lets us down, get English servers n the UK ffs!
 
O

old.Xanthian

Guest
heres my DOS Reports...

Tracing route to forum.camelot-europe.com [193.252.123.35]
over a maximum of 30 hops:

1 8 ms 9 ms 12 ms 172.24.215.254
2 9 ms 8 ms 9 ms gri-cam1-b-fa00.inet.ntl.com [213.105.3.2]
3 11 ms 11 ms 16 ms lee-t2core-b-pos45.inet.ntl.com [62.252.224.217]
4 11 ms 11 ms 15 ms lee-bb-b-so-120-0.inet.ntl.com [62.253.185.21]
5 12 ms 13 ms 12 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]
6 13 ms 12 ms 14 ms man-bb-b-ge-221-0.inet.ntl.com [62.253.187.178]
7 21 ms 23 ms 21 ms 213.206.159.37
8 20 ms 21 ms 46 ms sl-bb20-lon-9-0.sprintlink.net [213.206.128.97]
9 27 ms 27 ms 28 ms sl-bb21-par-14-0.sprintlink.net [213.206.129.70]
10 27 ms 31 ms 28 ms sl-gw10-par-15-0.sprintlink.net [217.118.224.42]
11 31 ms 31 ms 54 ms 213.206.131.42
12 32 ms 93 ms 78 ms P13-0.PASCR2.Pastourelle.opentransit.net [193.251.241.169]
13 26 ms 27 ms 28 ms P11-0.PASCR1.Pastourelle.opentransit.net [193.251.241.97]
14 26 ms 28 ms 27 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
15 27 ms 30 ms 27 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
16 27 ms 29 ms 28 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
17 * 29 ms 31 ms 193.252.122.10
18 28 ms 29 ms * forum.camelot-europe.com [193.252.123.35]
19 * * * Request timed out.
20 * 30 ms * forum.camelot-europe.com [193.252.123.35]
21 29 ms 29 ms 29 ms forum.camelot-europe.com [193.252.123.35]

Trace complete.

-----------------------

Pinging forum.camelot-europe.com [193.252.123.35] with 32 bytes of data:

Reply from 193.252.123.35: bytes=32 time=48ms TTL=113
Reply from 193.252.123.35: bytes=32 time=28ms TTL=113
Reply from 193.252.123.35: bytes=32 time=28ms TTL=113
Reply from 193.252.123.35: bytes=32 time=29ms TTL=113

Ping statistics for 193.252.123.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 48ms, Average = 33ms
 
T

tris-

Guest
how come you get 0% packet loss? using DOS i get

Ping statistics for 172.24.215.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
O

old.Xanthian

Guest
Dunno
Dont really know much about tracert and crap :eek:

But from my trace im getting loss somwhere.. but 21 Hops to a server is shit..
Ive done 4 traces and it started off with 16 hobs and its now gone to 21.


SORT OUT THE FREAKING SERVERS!!!
 
T

tris-

Guest
heres another reply from them -

The traffic could be transitting two interfaces, a different one in each direction. Or sometimes one interface can have a problem with just the transmit or just the receive. They'll need to do some testing on the router to isolate the problem.
 
O

old.windforce

Guest
depends on network topology
if you are behind a firewall which blocks outgoing ICMP you get this

Matt's traceroute [v0.41] on linux is very nice for traceroutes
 
I

inqy

Guest
Eeek at the packetloss. :/
Code:
================================================
=== VisualRoute report on 22-Oct-02 15:26:18 ===
================================================

Report for 193.252.123.24

Analysis: '193.252.123.24'  was found in 14 hops (TTL=240). 

---------------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address      | Node Name                                | Location         | Tzone  | ms | Graph      | Network                            |
---------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0   |       | 192.168.0.2     | omega                                    | ...              |        |    |            | (private use)                      |
| 1   |       | 192.168.0.1     | -                                        | ...              |        | 1  | x          | (private use)                      |
| 2   |       | 172.28.23.254   | -                                        | ...              |        | 13 |  x-----    | (private use)                      |
| 3   |       | 80.4.118.5      | ltn-t2cam1-a-s600.inet.ntl.com           | -                |        | 18 |  -x-----   | NTL Luton - CABLE HEADEND          |
| 4   |       | 213.107.47.65   | ltn-t2core-a-ge-wan61.inet.ntl.com       | -                |        | 33 |  ---x----  | NTL Luton - CABLE HEADEND          |
| 5   |       | 62.253.188.185  | pop-bb-a-so-300-0.inet.ntl.com           | -                |        | 30 |  ---x--    | NTL Internet                       |
| 6   |       | 212.113.14.129  | POS7-0.hsipaccess2.London1.Level3.net    | London, UK       | *      | 14 |  -x----    | Customer Serial Link               |
| 7   |       | 212.187.131.166 | gige1-2.core2.London1.Level3.net         | London, UK       | *      | 27 |  --x------ | 2nd London1 Gateway infrastructure |
| 8   | 20    | 193.251.240.217 | P7-0.LONBB1.London.opentransit.net       | London, UK       | *      | 31 |   --x--    | France Telecom Long Distance       |
| 9   | 30    | 193.251.154.225 | P13-0.PASCR1.Pastourelle.opentransit.net | ?---             |        | 40 |    --x---  | France Telecom Long Distance       |
| 10  | 40    | 193.251.241.118 | P4-0.BAGCR3.Bagnolet.opentransit.net     | Bagnolet, France | +01:00 | 28 |    -x--    | France Telecom Long Distance       |
| 11  | 40    | 193.251.241.145 | P1-0.BAGBB1.Bagnolet.opentransit.net     | Bagnolet, France | +01:00 | 37 |    --x-    | France Telecom Long Distance       |
| 12  | 40    | 193.251.251.58  | WanadooPortails1.GW.opentransit.net      | -                |        | 30 |    -x----  | France Telecom Long Distance       |
| 13  | 40    | 193.252.122.10  | -                                        | ?(France)        | +01:00 | 30 |    -x-     | Wanadoo Portails                   |
| 14  |       | 193.252.123.24  | -                                        | ?(France)        | +01:00 | 34 |    -x----  | Wanadoo Portails                   |
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to 193.252.123.24, average = 34ms, min = 24ms, max = 62ms -- 22-Oct-02 15:26:18
 
T

tris-

Guest
Ive emailed NTL world now i found there customer service adress so i will update you when they tell me something.
 
I

inqy

Guest
I'm now getting an average of 60% packetloss. Vis Route claims it's in the France telecom network. But I'll wait til I hear more news.

DaoC perf is showing red almost constant with the occassional flick to yellow. I don't dare to pull, took me 10 seconds to jump off a horse :/
 
O

old.Xanthian

Guest
neeeeed daoc!!!

this means im gonna have to resort to doing Uni work in the meantime !!!

:mad:
 
T

tris-

Guest
"Please give us more informations such as your source IP address, destination IP address you try to join, traceroute and statistics for loss of packets and send informations directly to noc@opentransit.net
Thanks"

off someone at opentransit

did as they asked and no reply yet.



"I seem to be getting packet loss at 193.251.154.225
193.251.251.58 is there a problem with your network?
----------------------------
no,

you can check with our looking glass

http://www.opentransit.net/lg.htm "

so everyones blaming it on each other and the people getting blamed say there is no problem.
 
T

tris-

Guest
i wouldnt bet on it being solved tonight, if it all. if no one sees a problem then they arnt gonna do anything, plus NTL dont support multiplayer games so if they know its that then they wont do anything even if something is wrong.


edit: oopsie, they fixed it now. the last guy i emailed must of pulled his finger out.
 

Users who are viewing this thread

Top Bottom