cancel
Showing results for 
Search instead for 
Did you mean: 

Plusnet Hub one router issue

FIXED
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Plusnet Hub one router issue

I've flagged this up internally for further investigation.

Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Mav
Moderator
Moderator
Posts: 22,371
Thanks: 4,725
Fixes: 514
Registered: ‎06-04-2007

Re: Plusnet Hub one router issue

Moderator's note:

@aramil

Your post prior to message #11 was released from the Spam Filter but as it was repeated in #11 I removed it

Forum Moderator and Customer
Courage is resistance to fear, mastery of fear, not absence of fear - Mark Twain
He who feared he would not succeed sat still

aramil
Dabbler
Posts: 10
Thanks: 1
Registered: ‎08-03-2017

Re: Plusnet Hub one router issue


@Townman wrote:

A ping / trace route is not overly helpful - the servers might well be there and alive, but that does not mean that NTP traffic is passing on port 123.


Yeah I know but best to show as much detail as possible, as they can't reproduce the issue locally.

alan659882
Rising Star
Posts: 97
Thanks: 12
Fixes: 1
Registered: ‎04-02-2011

Re: Plusnet Hub one router issue

I'm seeing the same issue, my router is cycling through four IP addresses...

 

2000-01-01 00:01:39 SNTP Unable to contact server: 212.159.13.49
2000-01-01 00:07:24 SNTP Unable to contact server: 212.159.13.50
2000-01-01 00:13:10 SNTP Unable to contact server: 212.159.6.9
2000-01-01 00:18:55 SNTP Unable to contact server: 212.159.6.10

 

 

 

 

Townman
Superuser
Superuser
Posts: 22,922
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Plusnet Hub one router issue


@aramil wrote:

@Townman wrote:

A ping / trace route is not overly helpful - the servers might well be there and alive, but that does not mean that NTP traffic is passing on port 123.


Yeah I know but best to show as much detail as possible, as they can't reproduce the issue locally.


You completely miss the point - pings add zero value here.  So "as much detail as possible" does not help in the context of the issue.  I am sure that when the covers are taken off this, its going to be the back haul network or the gateway the individual users are connected to.

If you want to add value, give the A.B.C.0 part of your IP address and the gateway you connect into - see http://usertools.plus.net/@gateway/

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Townman
Superuser
Superuser
Posts: 22,922
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Plusnet Hub one router issue

In advance of the PN guys getting on to this, can people reporting this issue please identify the A.B.C.0 part of their IP addresses and the gateway they are connected to.

Posts showing successful pings and failed NTP connections or router screen shots do not convey any context which is going to help the tech guys profile those for whom this is failing distinctly from those of us for which it works.

NTP is not broken - it would though appear that for some the access to the NTP server (or the response there from) is somehow broken.  The IP addresses being pinged are virtual IP addresses, behind which their are multiple DNS / NTP services in different data centres.  Hence the need for a context to those having this issue.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

mrben
Dabbler
Posts: 23
Thanks: 6
Registered: ‎13-12-2016

Re: Plusnet Hub one router issue

I assume this is what you're asking for? 

 

core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24)

It does say it cannot identify my gateway.

Townman
Superuser
Superuser
Posts: 22,922
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Plusnet Hub one router issue

Yes - Thanks - Indeed it does not help that for some gateways, the gateway tool has some missing information.  The PUG member who manages this tool (now also a SU) has been trying to obtain the additional data for a wee while.

What you have provided should mean enough though to those who will need to know,

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

alan659882
Rising Star
Posts: 97
Thanks: 12
Fixes: 1
Registered: ‎04-02-2011

Re: Plusnet Hub one router issue

the "Which gateway" tool for me says 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 Issues topic in the Community forums will help us to diagnose the problem.


    core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 7.054 ms

bobpullen
Community Gaffer
Community Gaffer
Posts: 16,869
Thanks: 4,950
Fixes: 315
Registered: ‎04-04-2007

Re: Plusnet Hub one router issue

Morning all. Managed to replicate this, suspect it's only affecting those connecting via certain parts of our dedicated network, particularly those that see the hop after there router time out on an outbound traceroute (which itself isn't a problem, it just indicates that you're probably on the affected route):

~$ traceroute -I community.plus.net
traceroute to community.plus.net (46.19.168.229), 30 hops max, 60 byte packets
 1  dsldevice.lan (192.168.1.254)  13.040 ms  13.043 ms  13.040 ms
 2  * * *
 3  133.hiper04.sheff.dial.plus.net.uk (195.166.143.133)  16.997 ms  18.147 ms  18.718 ms
 4  be3-3102.pcn-ir02.plus.net (195.166.143.132)  22.839 ms  26.047 ms  26.054 ms
 5  195.99.125.140 (195.99.125.140)  26.051 ms  27.922 ms  27.930 ms
 6  core3-hu0-14-0-7.faraday.ukcore.bt.net (195.99.127.64)  27.930 ms  13.297 ms  13.280 ms
 7  peer2-et-9-3-0.faraday.ukcore.bt.net (62.6.201.195)  15.406 ms  15.402 ms  17.407 ms
 8  * * *
 9  216.52.199.38 (216.52.199.38)  19.714 ms  20.952 ms  20.302 ms
10  core1.be3.ams004.pnap.net (216.52.199.50)  23.756 ms  23.945 ms  21.467 ms
11  border3.ae1-bbnet1.ams004.pnap.net (95.172.78.38)  21.443 ms  19.641 ms  19.607 ms
12  lithiumtechinc-5.edge1.ams004.pnap.net (95.172.78.146)  20.135 ms  17.713 ms  18.019 ms
13  aptgm87544.lithium.com (46.19.168.229)  18.435 ms  18.755 ms  20.421 ms

We've an incident raised and our engineers are currently looking into it (ref: 100657)...

 

 

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

bobpullen
Community Gaffer
Community Gaffer
Posts: 16,869
Thanks: 4,950
Fixes: 315
Registered: ‎04-04-2007

Re: Plusnet Hub one router issue

Should be on the mend now folks Smiley

~$ ntpdate -d ntp.plus.net
10 Jul 11:36:00 ntpdate[7240]: ntpdate 4.2.8p4@1.3265-o Wed Jun 28 18:08:13 UTC 2017 (1)
Looking for host ntp.plus.net and service ntp
212.159.13.50 reversed to cdns02.plus.net
cdns02.plus.net forward check lookup fail: Name or service not known
host found : 212.159.13.50 (cdns02.plus.net)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.9)
receive(212.159.6.9)
transmit(212.159.13.50)
receive(212.159.13.50)
transmit(212.159.6.10)
receive(212.159.6.10)
transmit(212.159.13.49)
receive(212.159.13.49)
transmit(212.159.6.9)
receive(212.159.6.9)
server 212.159.13.50, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.13.50], delay 0.03423, dispersion 0.00008
transmitted 4, in filter 4
reference time:    dd0dd304.977335a0  Mon, Jul 10 2017 11:18:44.591
originate timestamp: dd0dd717.60ab57a6  Mon, Jul 10 2017 11:36:07.377
transmit timestamp:  dd0dd717.62c05556  Mon, Jul 10 2017 11:36:07.385
filter delay:  0.03522  0.03423  0.03430  0.03458 
         0.00000  0.00000  0.00000  0.00000 
filter offset: -0.01251 -0.01278 -0.01273 -0.01263
         0.000000 0.000000 0.000000 0.000000
delay 0.03423, dispersion 0.00008
offset -0.012786

server 212.159.6.10, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.6.10], delay 0.03383, dispersion 0.00055
transmitted 4, in filter 4
reference time:    dd0dd355.eea58140  Mon, Jul 10 2017 11:20:05.932
originate timestamp: dd0dd717.93c2492f  Mon, Jul 10 2017 11:36:07.577
transmit timestamp:  dd0dd717.95f4b72e  Mon, Jul 10 2017 11:36:07.585
filter delay:  0.03584  0.03383  0.04024  0.03392 
         0.00000  0.00000  0.00000  0.00000 
filter offset: -0.01208 -0.01272 -0.00963 -0.01274
         0.000000 0.000000 0.000000 0.000000
delay 0.03383, dispersion 0.00055
offset -0.012720

server 212.159.13.49, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.13.49], delay 0.03506, dispersion 0.00029
transmitted 4, in filter 4
reference time:    dd0dd304.977335a0  Mon, Jul 10 2017 11:18:44.591
originate timestamp: dd0dd717.c6f0dc57  Mon, Jul 10 2017 11:36:07.777
transmit timestamp:  dd0dd717.c927a7c2  Mon, Jul 10 2017 11:36:07.785
filter delay:  0.03630  0.03545  0.03571  0.03506 
         0.00000  0.00000  0.00000  0.00000 
filter offset: -0.01279 -0.01309 -0.01314 -0.01340
         0.000000 0.000000 0.000000 0.000000
delay 0.03506, dispersion 0.00029
offset -0.013400

server 212.159.6.9, port 123
stratum 2, precision -21, leap 00, trust 000
refid [212.159.6.9], delay 0.03413, dispersion 0.00029
transmitted 4, in filter 4
reference time:    dd0dd355.eea58140  Mon, Jul 10 2017 11:20:05.932
originate timestamp: dd0dd717.fa4a12a2  Mon, Jul 10 2017 11:36:07.977
transmit timestamp:  dd0dd717.fc5a7e9e  Mon, Jul 10 2017 11:36:07.985
filter delay:  0.03526  0.03413  0.03526  0.03444 
         0.00000  0.00000  0.00000  0.00000 
filter offset: -0.01260 -0.01277 -0.01221 -0.01249
         0.000000 0.000000 0.000000 0.000000
delay 0.03413, dispersion 0.00029
offset -0.012777

10 Jul 11:36:07 ntpdate[7240]: adjust time server 212.159.6.10 offset -0.012720 sec

 

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

aramil
Dabbler
Posts: 10
Thanks: 1
Registered: ‎08-03-2017

Re: Plusnet Hub one router issue

Good job all round!

woohooo.PNG

alan659882
Rising Star
Posts: 97
Thanks: 12
Fixes: 1
Registered: ‎04-02-2011

Re: Plusnet Hub one router issue

Mine finally connected at about 1035am.

Thanks.

 

mort7890
Pro
Posts: 580
Thanks: 92
Fixes: 4
Registered: ‎28-06-2007

Re: Plusnet Hub one router issue

10:33:28, 10 Jul. (251197.660000) NTP synchronization success!
mrben
Dabbler
Posts: 23
Thanks: 6
Registered: ‎13-12-2016

Re: Plusnet Hub one router issue

All good for me too. Thanks for sorting it out.