topic Re: Gateway Checker Update in Community Announcements

Gateway Checker Update

spraxyt — Wed, 10 Dec 2014 14:08:02 GMT

Changes have been made to the Gateway Checker to extend functionality and provide additional information which will help diagnosis of certain problems.
More detail on the changes:

it now works on phones/tablets browsing (at home) via the Chrome compression proxy;

(up to) three attempts are made to determine the gateway (in case successive trace hops follow different routes on a busy network);

the "failed to identify gateway" message now lists the trace and suggests action to take to draw the problem to our attention (see quote 1);

the "not on a Plusnet connection" message suggests action to take if that diagnosis is not correct (see quote 2)

[quote=1 failed to identify gateway]
Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.
Posting the following information as a reply to the Gateway Checker Update topic in the Community Announcements forum will help us to diagnose the problem.
te8-1.ptw-gw01.plus.net (212.159.0.241) 3.120 ms
(212.159.2.145) 3.597 ms
[quote=2 not on a Plusnet connection]
Your IP address seems not to be from a Plusnet brand, hence we cannot detect your gateway.
If this is not correct posting the first three octets of your IP address (208.67.220.*) as a reply to the Gateway Checker Update topic in the Community Announcements forum will help us to diagnose the problem.
Note 1: The Gateway Checker Update text is linked to this topic for posting replies.
Note 2: Nothing included in the diagnostic information presented is sufficient to identify individual users.
Please reply below with questions or suggestions to improve the tool.
David

Re: Gateway Checker Update

Oldjim — Fri, 12 Dec 2014 11:06:48 GMT

Note - for those of you who spot the posted date as being a couple of days ago - this has just been moved from the hidden boards

Re: Gateway Checker Update

Chris — Fri, 12 Dec 2014 11:34:39 GMT

Thanks guys, good update and more useful information now

Re: Gateway Checker Update

rongtw — Sun, 11 Jan 2015 13:10:51 GMT

I have just got this
Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.
Posting the following information as a reply to the Gateway Checker Update topic in the Community Announcements forum will help us to diagnose the problem.
lts3.bt622-12.plus.net (212.159.1.195) 1.747 ms
gi1-1-163.pcl-gw02.plus.net (84.93.255.85) 1.694 ms

Re: Gateway Checker Update

spraxyt — Sun, 11 Jan 2015 13:47:13 GMT

Thanks. I wonder if Plusnet are introducing more gateways. What gateway does it show (usually second hop) if you do tracert ntp.plus.net at a command prompt on your own computer?
David

Re: Gateway Checker Update

rongtw — Sun, 11 Jan 2015 14:40:31 GMT

here ya go

Re: Gateway Checker Update

spraxyt — Sun, 11 Jan 2015 16:20:44 GMT

Thanks. That shows pcl-ag01 which is the older type.
David

Re: Gateway Checker Update

ejs — Sun, 11 Jan 2015 16:48:29 GMT

I suspect it's a new gateway, possibly will be ptw-bng03 once the reverse DNS entries are updated.

Re: Gateway Checker Update

rongtw — Tue, 13 Jan 2015 08:37:42 GMT

I haven't changed anything , no reboot or gateway hops but now it says i am on " You are currently connected to gateway pcl-ag08. "

Re: Gateway Checker Update

Anotherone — Tue, 13 Jan 2015 08:58:24 GMT

Can you repeat the tracert please?

Re: Gateway Checker Update

rongtw — Tue, 13 Jan 2015 09:09:28 GMT

NP Anotherone

Re: Gateway Checker Update

rongtw — Tue, 13 Jan 2015 09:26:46 GMT

now thats weird i just checked my TBB and looks like something happened about 08.15 .
Router log said internet disconnected at 08.15 ?? but wasnt me and no power outage .

Re: Gateway Checker Update

Anotherone — Tue, 13 Jan 2015 12:13:10 GMT

Can't spot any obvious cause unless it was due to local disturbance or exchange issue.
What I find a bit odd though, is that on the previous tracert the gateway appeared to be on the 3rd line rather than the 2nd line of the tracert.

Re: Gateway Checker Update

chrcoluk — Tue, 13 Jan 2015 12:39:46 GMT

Quote from: Oldjim
Note - for those of you who spot the posted date as being a couple of days ago - this has just been moved from the hidden boards

whats in the hidden boards and who has access?

Re: Gateway Checker Update

Anotherone — Tue, 13 Jan 2015 12:52:24 GMT

They are the boards where only the mods and PN staff have access, often used for where sensitive and personal data may be posted as well as drafts of some posts before they are put on the main forum board.

Re: Gateway Checker Update

chrcoluk — Tue, 13 Jan 2015 13:37:24 GMT

The op isnt a mod or pn staff tho.

Re: Gateway Checker Update

Oldjim — Tue, 13 Jan 2015 13:42:03 GMT

no but there is another hidden board where the UserGroup can post for viewing by staff and moderators

Re: Gateway Checker Update

ejs — Tue, 13 Jan 2015 18:40:25 GMT

Comparing some traceroutes, 195.166.130.202 is probably a PTW gateway.
[tt]traceroute to 195.166.130.202 (195.166.130.202), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.366 ms
2 lo0-central10.pcl-ag07.plus.net (195.166.128.188) 20.172 ms
3 link-a-central10.pcl-gw01.plus.net (212.159.2.184) 19.977 ms
4 xe-9-0-0.pcl-cr01.plus.net (212.159.0.216) 21.708 ms
5 ae1.ptw-cr01.plus.net (195.166.129.0) 19.646 ms
6 lts5.bt622-12.plus.net (212.159.1.197) 19.921 ms
7 202.core.plus.net (195.166.130.202) 21.384 ms
traceroute to 195.166.130.201 (195.166.130.201), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 12.865 ms
2 lo0-central10.pcl-ag07.plus.net (195.166.128.188) 29.723 ms
3 link-a-central10.pcl-gw01.plus.net (212.159.2.184) 56.698 ms
4 xe-9-0-0.pcl-cr01.plus.net (212.159.0.216) 20.407 ms
5 ae1.ptw-cr01.plus.net (195.166.129.0) 38.759 ms
6 po2.ptw-gw01.plus.net (195.166.129.37) 19.234 ms
7 lo0.default.ptw-bng02.plus.net (195.166.130.201) 21.526 ms
traceroute to 195.166.128.182 (195.166.128.182), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.359 ms
2 lo0-central10.pcl-ag07.plus.net (195.166.128.188) 42.907 ms
3 link-a-central10.pcl-gw01.plus.net (212.159.2.184) 20.225 ms
4 xe-9-0-0.pcl-cr01.plus.net (212.159.0.216) 20.366 ms
5 po2.pcl-gw01.plus.net (195.166.129.41) 32.152 ms
6 lo0-central10.pcl-ag01.plus.net (195.166.128.182) 21.354 ms[/tt]

Re: Gateway Checker Update

Anotherone — Tue, 13 Jan 2015 23:21:30 GMT

Another tracert
>tracert 195.166.130.202
Tracing route to 202.core.plus.net [195.166.130.202]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 34 ms 36 ms 38 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 34 ms 33 ms 33 ms link-a-central10.ptn-gw01.plus.net [212.159.2.132]
4 34 ms 33 ms 33 ms xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
5 35 ms 33 ms 34 ms lts1.bt622-12.plus.net [212.159.1.193]
6 34 ms 33 ms 33 ms 202.core.plus.net [195.166.130.202]
tracert to 195.166.130.200 & also to 201 & 203 all resolve to ptw-bng02

Re: Gateway Checker Update

rongtw — Sat, 11 Apr 2015 19:13:51 GMT

mmm i just got this