Via. The verdict.

Sloth

Well it's been 2 weeks now since I got ADSL off Via and I've finally found the weakest link in the whole thing -Eircom. Basically Eircom have mucked up the exchange for ADSL users (RADSL users are unaffected) in Blanchardstown. At the moment I'm getting........wait for this........
600 BYTES a second from downloads. Wow.
Via had been in contact with the engineer at the exchange today trying to fix the problem and what did the bloody Eircom engineer do? Go home for the weekend early of course. God damn it, I'm now stuck with a connection of about a 14k modem (60 times slower downloads than yesterday) for the weekend until hopefully the exchange is fixed some time next week. At least I can take some solace from the fact that it's not my lines that are the problem it's the exchange but it's not much comfort atm tbh.

ando

I've just got my link up and running with a D LInk DSL 504 router. Hmm, not quite as good as I was expecting:

C:\>tracert clarity.jolt.co.uk

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <10 ms 10 ms <10 ms 192.168.0.11
2 160 ms 130 ms 101 ms rt004dub.netsource.ie [213.79.63.254]
3 20 ms 20 ms 20 ms rt001dub.netsource.ie [212.17.32.97]
4 351 ms 350 ms 281 ms rt001kil.netsource.ie [212.17.32.101]
5 150 ms 120 ms 221 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
6 191 ms 350 ms 280 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.107.241]

7 200 ms 341 ms 200 ms pos2-0-622M.ar2.LON2.gblx.net [208.49.136.58]
8 131 ms 100 ms 70 ms lon1-9.nildram.net [195.66.224.59]
9 120 ms 131 ms 120 ms jolt-gw.nildram.net [195.149.20.126]
10 50 ms 40 ms 60 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=60ms TTL=247
Reply from 195.149.21.11: bytes=32 time=180ms TTL=247
Reply from 195.149.21.11: bytes=32 time=140ms TTL=247
Reply from 195.149.21.11: bytes=32 time=191ms TTL=247

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

C:\>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=40ms TTL=247
Reply from 195.149.21.11: bytes=32 time=300ms TTL=247
Reply from 195.149.21.11: bytes=32 time=80ms TTL=247
Reply from 195.149.21.11: bytes=32 time=191ms TTL=247

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

C:\>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=210ms TTL=247
Reply from 195.149.21.11: bytes=32 time=131ms TTL=247
Reply from 195.149.21.11: bytes=32 time=350ms TTL=247
Reply from 195.149.21.11: bytes=32 time=50ms TTL=247

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

C:\>tracert clarity.jolt.co.uk

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.11
2 40 ms 20 ms 31 ms rt004dub.netsource.ie [213.79.63.254]
3 240 ms 221 ms 120 ms rt001dub.netsource.ie [212.17.32.97]
4 531 ms 220 ms 140 ms rt001kil.netsource.ie [212.17.32.101]
5 40 ms 60 ms 60 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
6 60 ms 90 ms 81 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.107.241]

7 100 ms 60 ms 40 ms pos2-0-622M.ar2.LON2.gblx.net [208.49.136.58]
8 40 ms 60 ms 50 ms lon1-9.nildram.net [195.66.224.59]
9 160 ms 100 ms 51 ms jolt-gw.nildram.net [195.149.20.126]
10 250 ms 231 ms 190 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

I heard some were having touble with pings on netsource 1 or 2 days ago. I'm hoping this is just a once off and I'll be getting the true performance soon enough ???

Sloth

Originally posted by carbsy
That's RADSL for ya!

There will be many more people over the coming months with similar sob stories.....you must remember that it's a rate adaptive service and a lot of people will not be able to get speeds anywhere close to 512kbps.

carb.

ando

jesus, i'd be better off playing online games with Utv, thats how bad it is

Sloth

What exchange are you on? From what I'm seeing your getting similar (if slightly better) results than the ones I was getting up until yesterday.

bk

Originally posted by ando
jesus, i'd be better off playing online games with Utv, thats how bad it is

Yes, when DSL works well it is brilliant, but there will always be a few people for whom it just doesn't work out.

At least with Netsource you only have a two month contract, so at least you can get out of it.

For people that DSL pings don't work out and who are gamers, then ISDN + Friaco is probably best.

Sloth

Well wouldn't that still be pay per minute? I'd stick with what you have ando, it's a lot better than mine and your off the hook with phone bills from now on. Have faith and ring up tech support when you get a chance.
bk, whats friaco btw?

ando

yea, I was watching a bit of broadband tv which was pretty cool I taught, after that my ping was pretty stable 40 or 50 constanly to jolt, but after about 5 mins of playing, up she went to 100... 150 ... spikes all over the place

I was looking at the Line condition :



I'm getting a few line error's, could this be the cause? I'm not to sure what the norm is for Radsl in terms of errors

[EDIT] oh btw, i'm on the belcamp exchange

STaN

here's mine. I get jumpy pings also

Obo

The connection was pretty bad today. Download times almost cut in half earlier on, compared to yesterday. It seems a bit better now.

Anyway some pings...

C:\>ping -t clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=60ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=70ms TTL=248
Reply from 195.149.21.11: bytes=32 time=61ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=131ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=70ms TTL=248
Reply from 195.149.21.11: bytes=32 time=120ms TTL=248
Reply from 195.149.21.11: bytes=32 time=70ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=60ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=90ms TTL=248
Reply from 195.149.21.11: bytes=32 time=60ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=70ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=30ms TTL=248
Reply from 195.149.21.11: bytes=32 time=60ms TTL=248
Reply from 195.149.21.11: bytes=32 time=70ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=80ms TTL=248
Reply from 195.149.21.11: bytes=32 time=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=51ms TTL=248

Ping statistics for 195.149.21.11:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 131ms, Average = 58ms
Control-C
C:\>tracert clarity.jolt.co.uk

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 60 ms 40 ms 30 ms rt004dub.netsource.ie [213.79.63.254]
2 30 ms 30 ms 40 ms rt001dub.netsource.ie [212.17.32.97]
3 40 ms 30 ms 51 ms rt001kil.netsource.ie [212.17.32.101]
4 50 ms 30 ms 50 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
5 61 ms 60 ms 60 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.107.241]
6 50 ms 50 ms 60 ms pos2-0-622M.ar2.LON2.gblx.net [208.49.136.58]
7 50 ms 70 ms 50 ms lon1-9.nildram.net [195.66.224.59]
8 70 ms 60 ms 51 ms jolt-gw.nildram.net [195.149.20.126]
9 60 ms 50 ms 60 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

The results from earlier were a lot worse.
Castle Avenue (Clontarf) exchange btw.

ando

going by stans results, I do have a problem with the line then?

bk

Originally posted by Sloth
Well wouldn't that still be pay per minute? I'd stick with what you have ando, it's a lot better than mine and your off the hook with phone bills from now on. Have faith and ring up tech support when you get a chance.
bk, whats friaco btw?

FRIACO stands for Flat Rate Internet Access Call Origination and that should also answer the first part of your question.

FRIACO is the other part of what we in IOFFL have been campaigning for (and is likely the reason for the new "cheaper" RADSL products).

It basically means 24/7 (but not always on) access through 56k or ISDN for a fixed monthly fee. So in other words he wouldn't have to pay per minute, he would just pay EUR 25 - 30 per month (plus ISDN line rental of course).

These products are expected to be realised in June, probably by UTV, Esat (and maybe Eircom).

STaN

Originally posted by ando
going by stans results, I do have a problem with the line then?

As far as i know, RADSL doesn't need a perfect line. I'd quote your results to netsource

Sloth

On my ADSL connection I average about 84ms. I know that might seem high but even with my crappy connection atm it seems more stable than the results that ando is getting which are all over the place. Tech support time ando I'm afraid

Lex_Diamonds

Surely peoples mileage may vary, seeing as we are talking about a rate adaptive product here?

*shrug*

Sloth

I'm not talking about a rate adaptive product when I'm talking about my connection since I have normal ADSL but with the current crappiness my download mileage is stuck at the 600 bytes mark until Monday

GUI

Surely peoples mileage may vary, seeing as we are talking about a rate adaptive product here?

exactly!
further you are from exchange less likely you will get anything near 512 kilobits per second

remember also 300kilobits is all they have to give the user on this implementation of dsl

it adapts !!!!!

thomasb

Sloth isn't on the RADSL product.

We are having an issue in that our main link is not running at optimal speed - our old link to VIA finally expired on Monday and the main link upgrade has failed twice. We're hoping to resolve this properly next week - but it does mean that throughput occassionally is going to be a bit slow. Having said that, you can still get good download speeds (see attached PNG).

I'm not sure what Sloth's problem is - we've been working on it for nearly two weeks now. I'm reasonably certain the problem is either with the connection between Sloth's exchange and the BAS, or with his own wire (I'm tending slightly to the former at the moment). Honestly Sloth - we are doing what we can to get this fixed - it is frustrating us as much as it is you.

STaN

thomasb

Any idea why the likes of this is happening:

This is a 9minute snapshot of ping times to ireland.com.

Everything that is yellow is above 200ms. Not that there was a calm period in the centre of the graph. These were ping times of 35-60. The red lines are indexes of 30% packet loss.

STaN

ando

stan, see your Line Condition screenshot, Whats the "operation mode: T1.413" ?

In my line condition, the Operation Mode is "G.DMT" ?

Sloth

Could someone try pinging www.microsoft.com and tell me what results they get?

STaN

Originally posted by Sloth
Could someone try pinging www.microsoft.com and tell me what results they get?

microsoft don't let you ping them as people to stop people trying to attack their servers

Sloth

Oh right, thanks.
Thomas, I'm quite hopeful that all the problems will get sorted next week. The fact that it's not just me with the connection problems over the SME package pretty much rules out the second option as does the numerous line tests you've done. Thank god we didn't go ahead with line replacement for the time being.
Here's to next week, hopefully a week of changed experiences.

Mr. Fancypants

Latency is by far the worst i have seen it today....

Example pings and traceroutes :



C:\Documents and Settings\Martin>ping www.netsource.ie -t

Pinging www.netsource.ie [212.17.32.48] with 32 bytes of data:

Reply from 212.17.32.48: bytes=32 time=204ms TTL=126
Reply from 212.17.32.48: bytes=32 time=248ms TTL=126
Reply from 212.17.32.48: bytes=32 time=181ms TTL=126
Reply from 212.17.32.48: bytes=32 time=126ms TTL=126
Reply from 212.17.32.48: bytes=32 time=116ms TTL=126
Reply from 212.17.32.48: bytes=32 time=164ms TTL=126
Reply from 212.17.32.48: bytes=32 time=169ms TTL=126
Reply from 212.17.32.48: bytes=32 time=183ms TTL=126
Reply from 212.17.32.48: bytes=32 time=163ms TTL=126
Reply from 212.17.32.48: bytes=32 time=173ms TTL=126
Reply from 212.17.32.48: bytes=32 time=174ms TTL=126

Ping statistics for 212.17.32.48:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 116ms, Maximum = 248ms, Average = 172ms
Control-C
^C
C:\Documents and Settings\Martin>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=180ms TTL=248
Reply from 195.149.21.11: bytes=32 time=207ms TTL=248
Reply from 195.149.21.11: bytes=32 time=200ms TTL=248
Reply from 195.149.21.11: bytes=32 time=279ms TTL=248

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


C:\Documents and Settings\Martin>tracert www.netsource.ie

Tracing route to www.netsource.ie [212.17.32.48]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.mshome.net [192.168.0.1]
2 189 ms 149 ms 149 ms rt004dub.netsource.ie [213.79.63.254]
3 241 ms 201 ms 204 ms aurora.medianet.ie [212.17.32.48]

Trace complete.

C:\Documents and Settings\Martin>tracert clarity.jolt.co.uk

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.mshome.net [192.168.0.1]
2 160 ms 221 ms 228 ms rt004dub.netsource.ie [213.79.63.254]
3 231 ms 203 ms 227 ms rt001dub.netsource.ie [212.17.32.97]
4 252 ms 286 ms 326 ms rt001kil.netsource.ie [212.17.32.101]
5 269 ms 242 ms 210 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
6 248 ms 247 ms 204 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.107.241]

7 233 ms 247 ms 231 ms pos6-1-622M.ar2.LON2.gblx.net [67.17.92.150]
8 206 ms 201 ms 209 ms lon1-9.nildram.net [195.66.224.59]
9 * 97 ms 98 ms jolt-gw.nildram.net [195.149.20.126]
10 208 ms 240 ms 177 ms clarity.jolt.co.uk [195.149.21.11]

disco_rob_funk

I just noticed, those who posted their stat screens; the SNR was typically 5-6 dB.

My Netsource link has been tip-top from day one (512/8*90% = 57.6 KB/s and good pings), and my SNR has never been out of the 17 (+-2) dB range.

Might want to check the lines again?

flav0rflav

Nothing wrong with the dsl lines, network is problem.

C:\Program Files\Support Tools>tracert www.netsource.ie

Tracing route to www.netsource.ie [212.17.32.48]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Fast.Start [192.168.100.1]
2 235 ms 241 ms 229 ms rt004dub.netsource.ie [213.79.63.254]
3 165 ms 187 ms 196 ms aurora.medianet.ie [212.17.32.48]

ando

C:\>tracert www.netsource.ie

Tracing route to www.netsource.ie [212.17.32.48]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 200 ms 190 ms 190 ms rt004dub.netsource.ie [213.79.63.254]
3 240 ms 220 ms 201 ms aurora.medianet.ie [212.17.32.48]

Trace complete.

Sloth

ADSL pings seem grand for me atm even if everything else is unusable.

C:\DOCUME~1\KEVINO~1>ping www.netsource.ie

Pinging www.netsource.ie [212.17.32.48] with 32 bytes of data:

Reply from 212.17.32.48: bytes=32 time=66ms TTL=126
Reply from 212.17.32.48: bytes=32 time=62ms TTL=126
Reply from 212.17.32.48: bytes=32 time=77ms TTL=126
Reply from 212.17.32.48: bytes=32 time=62ms TTL=126

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

C:\DOCUME~1\KEVINO~1>tracert www.netsource.ie

Tracing route to www.netsource.ie [212.17.32.48]
over a maximum of 30 hops:

1 65 ms 62 ms 62 ms rt004dub.netsource.ie [213.79.63.254]
2 62 ms 62 ms 77 ms aurora.medianet.ie [212.17.32.48]

Trace complete.

Obo

More of the same

C:\>tracert www.netsource.ie

Tracing route to www.netsource.ie [212.17.32.48]
over a maximum of 30 hops:

1 234 ms 281 ms 313 ms rt004dub.netsource.ie [213.79.63.254]
2 329 ms 312 ms 266 ms aurora.medianet.ie [212.17.32.48]

Trace complete.

C:\>ping www.netsource.ie

Pinging www.netsource.ie [212.17.32.48] with 32 bytes of data:

Reply from 212.17.32.48: bytes=32 time=312ms TTL=127
Reply from 212.17.32.48: bytes=32 time=297ms TTL=127
Reply from 212.17.32.48: bytes=32 time=235ms TTL=127
Reply from 212.17.32.48: bytes=32 time=297ms TTL=127

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