Gateway Checker Update

[#1]

Mines this.
You are currently connected to gateway pcl-ag03.

[#2]

Quote from: spraxyt

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.

Everything in this thread seems to point to a single IP/gateway being out of kilter:

~$ host 195.166.130.202
202.130.166.195.in-addr.arpa domain name pointer 202.core.plus.net.

Happy to get it raised internally. Is this thread the only place you reported the issue David?

[#3]

Quote from: Bob

Happy to get it raised internally. If this thread the only place you reported the issue David?

No, there's a topic with more information (possibly an outbound rDNS issue too) in the UserGroup Technical Focus forum.  I won't post the link here since access is restricted.
David

[#4]

I've raised an internal problem and asked for the rDNS entries to be updated (ref: 85652).
For info, I can see three entries in the traceroute here that need updating:

202.core.plus.net [195.166.130.202] <--- This is wrong, should be PTW-BNG02
gi12-1-2-161.pcl-ag01.plus.net [84.93.255.80] < --- This is wrong, should be another PTW-BNG02 hop
lts2.bt622-12.plus.net [212.159.1.194] <--- This is wrong, should be a core gateway hop

[#5]

Can anyone explain this result (more rDNS errors?)

Quote

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. ae2.ptw-cr02.plus.net (195.166.129.5) 7.149 ms ae1.pcl-cr02.plus.net (195.166.129.3) 3.021 ms link12-central10.pcl-gw02.plus.net (84.93.249.118) 2.449 ms

Quote

Tracing route to bbc.co.uk [212.58.244.18] over a maximum of 30 hops:   1    1 ms    <1 ms    <1 ms  192.168.1.1   2    10 ms    9 ms    9 ms  179.core.plus.net [195.166.130.179]   3    10 ms    11 ms    9 ms  irb.12.pcl-cr01.plus.net [84.93.249.113]   4    10 ms    9 ms    9 ms  ae1.ptw-cr01.plus.net [195.166.129.0]   5    10 ms    9 ms    9 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]   6    *        *        *    Request timed out.   7    *        *        *    Request timed out.   8    11 ms    9 ms    9 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]   9    11 ms    10 ms    9 ms  132.185.255.149 10    10 ms    9 ms    9 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18] Trace complete.

[#6]

Quote from: frogfoot

Can anyone explain this result (more rDNS errors?)

These two hops are wrong (should be pcl-bng04):

link12-central10.pcl-gw02.plus.net (84.93.249.118) 2.449 ms

  2    10 ms     9 ms     9 ms  179.core.plus.net [195.166.130.179]

I'll ask for them to be updated.

[#7]

In other news...


Quote from: spraxyt

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.


A new range of IP's will be released to the masses shortly - 146.198.0.0/16.
Do you need to update the script so it recognises these David?

[#8]

Quote from: Bob

A new range of IP's will be released to the masses shortly - 146.198.0.0/16. Do you need to update the script so it recognises these David?

Thanks for the heads up. I've updated the script.
Testing (using a random IP in the range) now gives

IP 146.198.222.18 is a Plusnet IP

David

[#9]

Hi I've been doing the gateway checker and this came up (page below) is this how it should be please? Thanks

[#10]

Yes, that output is the correct format. It says your gateway is pcl-ag05.
David

[#11]

Thank you so much for your reply. I appreciate very much.

[#12]

Gateway IP will not resolve to a hostname.
Which gateway is this?

Quote

Which 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. acc1-10GigE-0-1-0-2.l-far.21cn-ipp.bt.net (109.159.249.20) 2.462 ms peer2-ae-1.redbus.ukcore.bt.net (195.99.126.97) 2.928 ms ae1.ptw-cr01.plus.net (195.166.129.0) 11.972 ms link4-central10.pcl-gw02.plus.net (84.93.249.38) 4.643 ms

[#13]

Thanks.
It looks like Plusnet need to change the rDNS entry for 84.93.249.38 to reflect that it is now a gateway.
I assume this results from the capacity increases made yesterday morning.
David

[#14]

It's ptn-bng02.
I'll have somebody look at the rDNS again (ref: 85652)

[#15]

Just got the following response (after reloaing the router with an old configuration):

Quote

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.    peer6-te0-0-0-17.telehouse.ukcore.bt.net (109.159.254.140) 3.970 ms    195.99.126.183 (195.99.126.183) 2.654 ms    ae1.pcl-cr02.plus.net (195.166.129.3) 2.931 ms    link3-central10.pcl-gw01.plus.net (84.93.249.164) 4.050 ms

Phil
corrected the "end quote"