It's me pings again / tech support

Rik · Jun 10, 2009, 16:34:05

7392/448 looks real enough to me, your profile will be 6.5M. Read the 2700 thread on setting up, that should preserve you from v6. As to wireless, just disable it if you don't need it.

http://192.168.1.254/xslt?PAGE=C01&THISPAGE=B02&NEXTPAGE=C01

on mine.

ou7shined · Jun 10, 2009, 17:13:14

Thanks Rik - saved the day again.

I have disabled it for now but I'd like to get it going for my mobile connection also the Mrs wants it for Wii stuff.

Rik · Jun 10, 2009, 17:19:15

In that case:

http://home/xslt?PAGE=C01&THISPAGE=A02_POST&NEXTPAGE=C01

Click on Wireless settings > Edit settings and turn on WPA there, setting a strong key.

ou7shined · Jun 10, 2009, 17:24:55

Thanks. (had to edit http://192.168.1.254 into the address but I've got the hang of it now)

You knew this was coming....

What's the difference between WEP, WPA, WPA2, PSK etc.?

Rik · Jun 10, 2009, 17:28:50

WEP is weak and hardly worth using, WPA is stronger and pretty secure, WPA2 is stronger yet and compatible with most modern machines. PSK just refers to the fact you use a shared key to access the router.

ou7shined · Jun 12, 2009, 15:09:33

Sorted! Everything's back to normal again.

Having said that, interleaving off has taken me from a very jumpy 70~120ms back down to 40~60ms, which is a little higher than it was before all this happened with it switched on but still in the same ballpark - so presumably something's still not quite right.

I would appreciate if someone could comment on this.

My connection is syncing around the 7.2~7.4 mark (been doing a few on and offs while configuring my 2700 so presumably it hasn't settled fully) which I am over the moon about.

And I am now fairly au fait with the world of wireless. I'm glad to have taken the plunge (or been pushed into the deep end by you guys

) It's like one of those things where you know you should just come out and ask about it but everyone else seems to take it for granted so you quietly get by without it. I do have a couple of 2700 questions but I'll air them over in the 2700 thread.

Many thanks peeps.

Rik · Jun 12, 2009, 15:51:28

Hi Rich, glad you're getting there. The ping time may just indicate there's more congestion at the exchange than normal. Is the 2700 indicating it's on fast path?

ou7shined · Jun 12, 2009, 17:52:02

Is that this bit?

DSL Connection Details
DSL Line (Wire Pair): Line 1 (inner pair)
Protocol: G.DMT Annex A
Downstream Rate: 7264 kbps
Upstream Rate: 448 kbps
Channel: Fast
Current Noise Margin: 12.0 dB (Downstream) 22.0 dB (Upstream)
Current Attenuation: 31.7 dB (Downstream) 17.5 dB (Upstream)
Current Output Power: 19.8 dBm (Downstream) 12.3 dBm (Upstream)
DSLAM Vendor Information: Country: {0xB5} Vendor: {TSTC} Specific: {0x00}
PVC Info: 0/38

Internet Connection Details
Connection Type: PPPoA
Username: ********@uk.idnet.dsl4
Internet Address: 212.69.xxx.xxx
Subnet Mask: 255.255.255.255
Default Gateway: 212.69.63.55
Primary Domain Name Server: 212.69.36.3
Secondary Domain Name Server: 212.69.40.3
Domain:
Maximum Transmission Unit (MTU): 1500
Gateway Ping: Successful
DNS Communication: Successful
Configuration Server Post: Waiting for DNS information

Rik · Jun 12, 2009, 17:59:05

I've just removed your IP address, Rich. Yup, that's it, you're on fast path. I would have hoped for a better ping than 40ms. Can you try a tracert, please, ie Start > Run > CMD <enter> then type tracert www.idnet.net. Paste the result back if you would.

ou7shined · Jun 12, 2009, 18:20:59

Whoops cheers.

I did 2 for you...

Rik · Jun 12, 2009, 18:26:42

There's very little delay once you hit the IDNet network, Rich, it all seems to be in that first hop. Keep an eye on it, if it doesn't improve, have a word with support.

Incidentally, the quick way to cut'paste' from the CMD window it to right-click on the title bar, then Edit > Select All then <enter>. That's the cut done and you can paste the results as text, rather than having to go through an image editor.

Rik · Jun 12, 2009, 18:31:57

For comparison, I've just done a tracert. My line is interleaved, btw.

tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms home [192.168.1.254]
2 120 ms 37 ms 23 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 23 ms 23 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 26 ms 23 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 25 ms 21 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 24 ms 23 ms 25 ms www.idnet.net [212.69.36.10]

Trace complete.

ou7shined · Jun 12, 2009, 18:44:15

Nice tip thanks.

So it does looks a bit iffy then? What should I be looking out for? I take it the 307 and 73 are bad.

I did a few more and this one came out fairly even...

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms home [192.168.1.254]
2 40 ms 45 ms 39 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 39 ms 41 ms 39 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 41 ms 41 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 41 ms 41 ms 41 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 39 ms 39 ms 39 ms www.idnet.net [212.69.36.10]

Trace complete.

ou7shined · Jun 12, 2009, 18:50:42

Sorry for not keeping up with you.... I'm making the tea while doing this.

Rik · Jun 12, 2009, 18:53:40

They are just peak values, Rich, the third column is the average, which is pretty static. What you see in a tracert is a ping to each step of the journey, rather than a simple end to end ping. It can help identify where delays are occurring along the way, but ping traffic is usually given a low priority by the routers it passes through, so if they are busy, you'll see the high values. Hence, you need to collect them over a longish period, eg hours or a day, to see if there are any patterns developing. ATM, my best guess would be you have a fairly busy VP at the exchange, when I was running on a business package, which has priority at the exchange, my pings improved by an average of 4ms on the 24ms I normally see, and when my line was not interleaved, I saw pings of 13ms.

You're also a lot nearer my favourite butcher than my favourite ISP, so that extra distance will have an impact (ping a USA site and you'll see what I mean).

Rik · Jun 12, 2009, 18:54:06

Quote from: ou7shined on Jun 12, 2009, 18:50:42
Sorry for not keeping up with you.... I'm making the tea while doing this.

NP. I stopped to go and do my daily penance on the exercise bike.

ou7shined · Jun 12, 2009, 20:55:05

Quote from: Rik on Jun 12, 2009, 18:53:40...You're also a lot nearer my favourite butcher than my favourite ISP...

My pings are dear to me as a weekend gamer. I wonder if I'll ever get my 23~24ms that I was getting when I 1st joined here. Maybe as you say my exchange is just too busy now. I'll have a look at the business packs but I'm probably paying too much for the one I have as it is.

Rik · Jun 13, 2009, 09:44:49

Have a word with IDNet first, Rich, especially of you're on GW6.

ou7shined · Jun 13, 2009, 10:30:03

I think I'm on dsl4.

Rik · Jun 13, 2009, 10:32:54

The last few characters of your login will tell you. If it's dsl4, it's the same central as gw5, so that's not an issue.

ou7shined · Jun 13, 2009, 10:42:29

That's reassuring. It's good to eliminate it as the culprit.

Do you think I should give them a bell this morning to see if there's anything else they can do?

Rik · Jun 13, 2009, 10:49:59

No point, Rich, it's not an emergency and would not be dealt with until Monday.

ou7shined · Jun 13, 2009, 10:54:32

Righto

jimc · Jun 13, 2009, 14:18:25

suffering myself today
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.3.2
2 113 ms 129 ms 96 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 172 ms 137 ms 133 ms telehouse-gw3-g0-1-400.idnet.net
[212.69.63.243]

4 50 ms 49 ms 52 ms redbus-gw2-g0-1-331.idnet.net
[212.69.63.5]
5 175 ms 173 ms 51 ms redbus-gw1-fa2-0-300.idnet.net
[212.69.63.225]
6 326 ms 244 ms 188 ms www.idnet.net [212.69.36.10]

Trace complete.

ou7shined · Jun 13, 2009, 14:24:23

Here's me today......

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home [192.168.1.254]
2 51 ms 53 ms 203 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 62 ms 43 ms 98 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 39 ms 66 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 39 ms 39 ms 43 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 39 ms 41 ms 41 ms www.idnet.net [212.69.36.10]

Trace complete.