Gateway Checker Update

[#1]

The op isnt a mod or pn staff tho.

[#2]

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

[#3]

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]

[#4]

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

[#5]

mmm  i just got this

[#6]

I think there is something wrong with your account (unless that is a new gateway) and this might explain your problems.

[#7]

rongtw do an outbound tracert, the first external hop shows the gateway.
e.g. tracert bbc.co.uk

[#8]

Quote from: rongtw

mmm  i just got this

Thanks. I think that problem reflects some reassignment of IPs that Plusnet did in January 2015. Plusnet need to change the reverse DNS entries for those IPs. I reported this to Plusnet at the time but it hasn't been actioned.
David

[#9]

Quote from: AndyH

I think there is something wrong with your account (unless that is a new gateway) and this might explain your problems.

This has to be one of the most stupid suggestions I've seen posted on here in a long time!

[#10]

I'm afraid I have to agree with that remark  The whole point of the change to the checker was to produce output like that so that relevant rDNS entries could be sorted out.

[#11]

Quote from: jelv

This has to be one of the most stupid suggestions I've seen posted on here in a long time!

I take offence at this comment.
The reason I made my statement was:
1) rongtw is seeing an issue of packet loss/high latency to some addresses and not others (latency/packet loss only seem to be an issue on the connection from him rather than to him).  This is consistent with an account issue that someone else had a little while ago and the same Plusnet did the same dial in test (which came back ok). Every single trace route he's posted, is to a lo0-central.x address and there are at least 5 different ones he's posted.
2) The second hop IP on his latest trace route does not appear to be consistent with any of the IPs already flagged up as having incorrect rDNS.
I did also say that it might be a new gateway, but in view of rongtw's problems, I looked at another possible cause.

[#12]

Quote from: AndyH

I take offence at this comment.

Well it's a good job you didn't see any of the first four drafts before I toned it down to that!

[#13]

it probably is a new gateway, at least one of the bng's had a weird rdns when it first got launched, I posted such a thing a year or so ago on kitz forum and a plusnet staff member at the time confirmed it was a new gateway, it did eventually get updated to the standard rdns format plusnet use.
to suggest its a broken account is baffling and I see nothing wrong with jelv's comment.

[#14]

Can someone explain what the relevance of the different gateway names are? For example I hear people talking of "the bng gateways" - what does this actually mean?

[#15]

In simple terms the Gateway names just identify which Data Centre they are in and also the type of hardware being used. The bng Gateways are using some of the latest Juniper hardware.