Gateway Check Issues.
FIXED- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Fibre Broadband
- :
- Gateway Check Issues.
Re: Gateway Check Issues.
01-06-2016 5:52 PM - edited 01-06-2016 5:53 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Alucidnation wrote:
However, i have not disconnected/reconnected since my post on Sunday, unless you mean something else?
I must have been looking at the wrong account
I've reported the observation to the relevant team to see if there's anything that can be done to help.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Re: Gateway Check Issues.
06-06-2016 1:15 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@Alucidnation, from what I can tell this should be working for you now. Can you confirm?
C:\Windows\System32>tracert 147.147.192.215 Tracing route to 215.192.147.147.dyn.plus.net [147.147.192.215] over a maximum of 30 hops: 1 3 ms 1 ms 1 ms 10.200.200.200 2 2 ms 1 ms 1 ms vlan2877.peh-cr02.plus.net [84.93.232.109] 3 2 ms 1 ms 2 ms gi9-46.2874.peh-cr01.plus.net [84.93.232.100] 4 2 ms 2 ms 1 ms eth0-1.46.peh-efw01.plus.net [84.93.232.101] 5 2 ms 2 ms 2 ms gi8-46.2655.peh-cr01.plus.net [84.93.232.26] 6 15 ms 12 ms 13 ms po5.peh-cr02.plus.net [84.93.232.17] 7 13 ms 13 ms 13 ms 84-93-232-60.plus.net [84.93.232.60] 8 13 ms 12 ms 13 ms ae3.ptw-cr01.plus.net [195.166.129.32] 9 16 ms 16 ms 16 ms ae2.ptw-cr02.plus.net [195.166.129.5] 10 14 ms 14 ms 13 ms tunnel-ip11.psb-ir01.plus.net [195.166.129.188] 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Re: Gateway Check Issues.
06-06-2016 1:22 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
No, still the same....
Custom diagnostic check on IP 147.147.192.215
Array ( [1] => 7 core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 4.861 ms )
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.
- core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 4.861 ms
Re: Gateway Check Issues.
06-06-2016 3:22 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@bobpullen Tracing from my Plusnet connection to this target worked OK for me before, and still does - the Internet Router used in this case (for both of us) has "tunnel" on its rDNS.
When the tool is used the route is external and the Internet Router traversed after
core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24)
appears not to be responding to pings (neither ICMP echo nor UDP type).
Re: Gateway Check Issues.
07-06-2016 9:10 AM - edited 07-06-2016 9:13 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Colour me confused
This is a trace from a Voda LTE connection to one of my own lines at home:
>tracert 143.159.XXX.XXX Tracing route to 143.159.XXX.XXX over a maximum of 30 hops: 1 6 ms 5 ms 3 ms 192.168.43.1 2 * * * Request timed out. 3 36 ms 45 ms 36 ms 192.168.213.21 4 91 ms 35 ms 42 ms 192.168.213.22 5 * * * Request timed out. 6 40 ms 40 ms 58 ms 10.206.133.101 7 36 ms 46 ms 29 ms 213.185.194.173 8 80 ms 38 ms 46 ms ae18-100-xcr1.lns.cw.net [195.89.16.17] 9 46 ms 36 ms 37 ms t2c3-ae1-0.uk-lon1.eu.bt.net [166.49.211.253] 10 120 ms 43 ms 42 ms 166-49-211-243.eu.bt.net [166.49.211.243] 11 162 ms 37 ms 40 ms core2-hu0-10-0-1.southbank.ukcore.bt.net [195.99.127.12] 12 * * * Request timed out. 13 207 ms 47 ms 52 ms be2.psb-ar01.plus.net [195.166.129.181] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 152 ms 59 ms 37 ms XXX.XXX.159.143.dyn.plus.net [143.159.XXX.XXX] 18 56 ms 47 ms 48 ms XXX.XXX.159.143.dyn.plus.net [143.159.XXX.XXX]
So the IR looks to be non-responsive to ICMP, however when I visit the Gateway Checker:
You are currently connected to gateway psb-ir01. This is located in Southbank Point of Presence.
The same trace to @Alucidnation looks like this, note the IR seems to be responding to ICMP:
C:\Windows\System32>tracert 147.147.192.215 Tracing route to 215.192.147.147.dyn.plus.net [147.147.192.215] over a maximum of 30 hops: 1 6 ms 4 ms 7 ms 192.168.43.1 2 * * * Request timed out. 3 148 ms 40 ms 38 ms 192.168.213.21 4 99 ms 45 ms 50 ms 192.168.213.22 5 * * * Request timed out. 6 149 ms 45 ms 76 ms 10.206.133.101 7 216 ms 45 ms 38 ms 213.185.194.173 8 110 ms 35 ms 37 ms ae18-100-xcr1.lns.cw.net [195.89.16.17] 9 99 ms 38 ms 39 ms t2c3-ae1-0.uk-lon1.eu.bt.net [166.49.211.253] 10 53 ms 47 ms 39 ms 166-49-211-239.eu.bt.net [166.49.211.239] 11 54 ms 29 ms 45 ms core1-hu0-18-0-1.southbank.ukcore.bt.net [62.172 .103.22] 12 431 ms 37 ms 38 ms be10.psb-ir01.plusnet.bt.net [195.99.125.131] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * ^C
Yet the Gateway Checker doesn't work
It's as if ICMP response is selective dependent on the origin.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Re: Gateway Check Issues.
07-06-2016 10:30 AM - edited 07-06-2016 10:34 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
For the 147.147.x.x traces, if one looks closely at the routes they are not the same. All three probes using LTE go through
core1-hu0-18-0-1.southbank.ukcore.bt.net [62.172.103.22] be10.psb-ir01.plusnet.bt.net [195.99.125.131]
(times omitted for clarity). Note that it's "core1" on the left and the IP ends with "22".
The probe from the Gateway Checker goes through
core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24)
Here it's "core2" and "24". There will be "time out/no response" asterisks following that but the Gateway Checker doesn't print the terminal chain of these.
For your IP at home if you do http://usertools.plus.net/@gateway_custom it will print the trace.
Re: Gateway Check Issues.
07-06-2016 11:59 AM - edited 07-06-2016 11:59 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
My diagnostic trace goes through core1 and looks to be responsive:
Array ( [1] => 7 core1-hu0-9-0-1.southbank.ukcore.bt.net (195.99.127.2) 4.494 ms [2] => 8 be10.psb-ir01.plusnet.bt.net (195.99.125.131) 5.201 ms [3] => 9 be2.psb-ar01.plus.net (195.166.129.181) 4.502 ms [4] => 10 * [5] => 11 * [6] => 12 * [7] => 13 XXX.XXX.159.143.dyn.plus.net (143.159.XXX.XXX) 13.887 ms [8] => 14 XXX.XXX.159.143.dyn.plus.net (143.159.XXX.XXX) 23.363 ms )
Fits with your theory though.
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
Re: Gateway Check Issues.
15-06-2016 2:39 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
And still the same...
Custom diagnostic check on IP 147.147.192.215
Array ( [1] => 7 core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 4.560 ms )
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.
- core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 4.560 ms
Re: Gateway Check Issues.
15-06-2016 4:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I've also received a similar report concerning routing through Colindale
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.
- core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.503 ms
- *
- *
Re: Gateway Check Issues.
17-06-2016 12:07 PM - edited 17-06-2016 12:20 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Thanks for notifying the mods about the thread not being able to write to for normal users @spraxyt
Yes I had that report, and I noticed that I was moved on the new network just last week. (no longer an ag 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.
- core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.503 ms
- *
- *
And on the ntp trace route
C:\Users\Henri>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.13.49]
over a maximum of 30 hops:1 1 ms <1 ms 1 ms LINKSYSHOME [192.168.1.1]
2 * * * Request timed out.
3 * * 14 ms 129.hiper04.sheff.dial.plus.net.uk [195.166.143.129]
4 13 ms 13 ms 13 ms be3-3100.pcn-ir01.plus.net [195.166.143.128]
5 13 ms 12 ms 12 ms cdns01.plus.net [212.159.13.49]Trace complete.
Custom diagnostic check
Which gateway
Custom diagnostic check on IP 143.159.###.##
Array ( [1] => 7 core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.773 ms [2] => 8 * [3] => 9 * [4] => 10 48.185.159.143.dyn.plus.net (143.159.###.##) 20.561 ms
Thanks,
Swiss Army Knife for diagnosing all your issues
Re: Gateway Check Issues.
07-07-2016 10:44 PM - edited 07-07-2016 10:47 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Now on different IP assignment, still the same...
- core1-hu0-9-0-1.colindale.ukcore.bt.net (195.99.127.18) 4.139 ms
- 195.99.125.141 (195.99.125.141) 4.155 ms
- *
Speaking of which, I am now assigned with a BT IP instead of the Plusnet one, any changes needed? I have noticed a increase in sync speed from the general 69.4Mbps to 72.73Mbps (Bras Profile checks before and after). Also a decrease in latency, 18ms to 11ms
All since I was pluging and unpluging ethernet cables and sorting out cable management all day today. Must have given that BT DLM a kick (for good hehe).
Custom
Array ( [1] => 7 core1-hu0-9-0-1.colindale.ukcore.bt.net (195.99.127.18) 4.392 ms [2] => 8 195.99.125.141 (195.99.125.141) 4.538 ms [3] => 9 * [4] => 10 XX.XXX.XXX.146.dyn.plus.net (146.198.XXX.XX) 11.707 ms )
Tracert
C:\Users\Henri>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms LINKSYSHOME [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 13 ms 13 ms 13 ms be3-3100.pcn-ir01.plus.net [195.166.143.128]
5 12 ms 11 ms 11 ms cdns02.plus.net [212.159.6.10]
Trace complete.
Swiss Army Knife for diagnosing all your issues
Re: Gateway Check Issues.
08-07-2016 8:15 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Still the same here, although now with a different ip etc..
Custom diagnostic check on IP 146.198.119.229
Array ( [1] => 7 core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.086 ms )
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.
- core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.086 ms
Re: Gateway Check Issues.
17-07-2016 7:02 PM - edited 17-07-2016 11:02 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Thanks,
http://usertools.plus.net/@gateway/
Now reporting:
You are currently connected to gateway pcn-ir01.
This is located in Colindale Point of Presence.
Swiss Army Knife for diagnosing all your issues
Re: Gateway Check Issues.
17-07-2016 8:54 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Same here on the same gateway, although i'm wondering if this has contributed to the DNS issues?
Re: Gateway Check Issues.
17-07-2016 11:06 PM - edited 17-07-2016 11:10 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
This was just a bug on a separate website, Plusnet Tools where we can identify which gateway we're connected to.
This website is a community based one which has no correlation to the official Plusnet network engineers. It was based to give us information like the services of 21cn in exchanges or the gateway through a trace route done by a web server.
On the old network there was some gateways that were terrible which is why many would resync until they got their preferred gateway.
On the new network the gateway changes between resync happen less often. And with the new capacity from the new network; there is no reason to hop onto gateways.
This DNS issue lies within the configuration of the new network routing. Moving to a static ip is a workaround and not a solution; you're simply reverting to the old network when doing so.
Swiss Army Knife for diagnosing all your issues
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page