Is Plusnet Down Again?

[#1]

Quote from: AndyH

According to BT SINet 472 (http://www.sinet.bt.com/sinet/SINs/pdf/472v2p6.pdf), session/idle timeouts are set at least 120 minutes BT's end (RADIUS):

But the >= 7200 second timeout is in the section for PTA mode, which doesn't apply to Plusnet using L2TP.

[#2]

Slightly OT given the last few pages of discussion, but...

Quote from: w23

Quote from: DaveyH Interestingly though, on checking the gateway I get "Sorry, records show your IP address is not from the Plusnet brand and as such, we cannot detect your gateway." Strange given I'm using the static IP I've had for nearly 2 years I'm getting exactly the same thing on the gateway checker, also on a long-standing pn static ip.

We've updated the rDNS of some of the newer end points and various issues have been fixed following the migration of the Usertools box to a new environment. If anybody is still experiencing problems with the gateway checker then please make yourself heard.

[#3]

Thanks for the info Bob.

[#4]

+1 & cheers BOB
After  posting in gateway checker down ? where using both the http://usertools.plus.net/@gateway/ & http://usertools.plus.net/@gateway_custom/?debug-ip were not working
They are now showing the Gateway for me

[#5]

Still getting
'Sorry, records show your IP address is not from the Plusnet brand and as such, we cannot detect your gateway.'  Using http://usertools.plus.net/@gateway/
And
"You are using a debugging mode - and checking IP 66.***.***.**
Array
(
   [1] =>  8  209.85.253.196 (209.85.253.196)  1.953 ms
   [2] =>  9  72.14.242.220 (72.14.242.220)  7.614 ms
   [3] => 10  216.239.47.75 (216.239.47.75)  7.381 ms
   [4] => 11  *
   [5] => 12  google-proxy-66-249-93-3.google.com (66.249.93.3)  7.352 ms
)
Sorry, records show your IP address is not from the Plusnet brand and as such, we cannot detect your gateway."
Using http://usertools.plus.net/@gateway_custom/?debug-ip
Edit - completely wrong IP btw

[#6]

What does this tell you? (you can edit out your IP address when replying if you like)
Edit: Ignore me.
Edit again: 66.249.93.3 is not a Plusnet IP address. It looks to me like you're connecting through some sort of proxy?

[#7]

Sussed it.
Some how had Chrome for Android data saving feature enabled. Disabled it and now reporting correct IP.

[#8]

Excellent. I was stumbling around the desktop version trying to find a similar feature. Didn't think to check the mobile variant

[#9]

Quote from: Bob

We've updated the rDNS of some of the newer end points and various issues have been fixed following the migration of the Usertools box to a new environment. If anybody is still experiencing problems with the gateway checker then please make yourself heard.

Does this mean I can remove the bng specific hack from my uptime sig image?

$gateway_host = gethostbyaddr($gateway_ip);
$gateway_host_parts = explode(".",$gateway_host);
if (preg_match('/bng/',$gateway_host) == 1) {
  $gateway_id = $gateway_host_parts[3];
} else {
  $gateway_id = $gateway_host_parts[1];
}

[#10]

I'd imagine so. There's likely to be more end points added in the not-too-distant future though, and I'd be lying if I said this was the first time we'd neglected to update the rDNS in a timely fashion.

[#11]

Quote from: DaveyH

Sussed it. Some how had Chrome for Android data saving feature enabled. Disabled it and now reporting correct IP.

Nice to know it is now resolved for you,  & one to look out for in the future

Quote from: avatastic

<snip> Does this mean I can remove the bng specific hack from my uptime sig image? $gateway_host = gethostbyaddr($gateway_ip); $gateway_host_parts = explode(".",$gateway_host); <snip> }

@ First glance looks like you were attempting to blow their servers up

[#12]

Quote from: Bob

I'd imagine so. There's likely to be more end points added in the not-too-distant future though, and I'd be lying if I said this was the first time we'd neglected to update the rDNS in a timely fashion.

Either I'd cached the result for 195.166.128.229 or it hasn't had its gw identifier moved.

preg_match('/\.([a-z]{3}\-[a-z]{2,3}[0-9]{2})\./',$gateway_host,$matches);
$gateway_id = $matches[1];

Regex to the rescue then. 

[#13]

Withdrawn. Rebooting router a few times solved it.

[#14]

Quote from: ejs

I wouldn't be surprised if we see ptn-bng02 and/or ptw-bng02 appear before plusnet say anything about making some progress towards solving the problem.

ptn-bng02 has appeared.

[#15]

That does not explain why my connection dropped,

& I am not sure what gateway it was on previously
[code= Tracert]Tracing route to portal.plus.net [212.159.9.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.10.1
  2     1 ms     1 ms     1 ms  192.168.1.1
  3    27 ms    29 ms    27 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195
]
  4    27 ms    27 ms    27 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.14
4]
  5    27 ms    26 ms    30 ms  xe-4-2-0.ptw-cr01.plus.net [212.159.0.240]
  6    27 ms    26 ms    27 ms  ae1.pcl-cr01.plus.net [195.166.129.1]
  7    27 ms    28 ms    27 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  8    34 ms    34 ms    34 ms  gi5-8.ptp-cr01.plus.net [84.93.224.48]
  9    34 ms    34 ms    33 ms  vlan2657.ptp-elb01.plus.net [84.93.224.36]
10    34 ms    48 ms    33 ms  portal.plus.net [212.159.9.2]
Trace complete.
[/code]
However this might
[quote= Email]Service: Broadband
Posted: Thu, Oct 30 2014 at 13:47:14
Subject: Regional Engineering & Repair Delays - UPDATE
This is an update to the previous post regarding MBORC (Matters Beyond Our Reasonable Control) declarations from BT Openreach.
Parts of the UK, in particular the South West and Wales, were hit with severe storm conditions with heavy rain, wind and lightning strikes, from Wednesday 8 into Thursday 9 October 2014.
This seriously impacted BT Openreach's infrastructure, both above and below ground with fault intake in these areas at extremely high levels. BT Openreach therefore declared MBORC for repair activities, in the three areas, with effect from 23:59 10 October 2014.
Due to the prevailing conditions in the region, we also declared MBORC in Cardiff, with effect from 23:59 14 October 2014.
We have been working hard to to bring the position back to normal as quickly as possible and have removed MBORC from the following area:
Cardiff
MBORC remains in place in the following areas
North Wales
Swansea
Truro
We are continuing to direct available additional resource into these areas to bring the position back to normal as quickly as possible and will be  monitoring the situation and will remove MBORC as soon as service can be restored to the levels they were at immediately before the severe weather.

We'll continue to post further updates as they become available.
Kind regards,
Adam Cassim
Customer Relations
--
This email has been sent to you because you have requested to join the Plusnet Status Mailing List. To unsubscribe from this mailing list, please visit http://usertools.plus.net/status/email.php?action=unsubscribe&uid=7209&auth=4g62qjftey
If not then CRT can enlighten us