topic Re: ppp outages in IPv6 Trial

ppp outages

chrcoluk — Wed, 12 Feb 2014 10:26:36 GMT

anyone else on the trial getting outages during the night on their ppp sessions?
I assumed was the trial but I checked another plusnet trialist tbb graph and they dont have the same outage. mine here.

note this outage is on ipv4 as well the entire ppp session was down.
I had a similiar outage on the 1 feb as well.
If you can see 2pm outage from yesterday ignore that (engineer visit). I am reffering to the one at dusk.

Re: ppp outages

pwatson — Wed, 12 Feb 2014 10:34:07 GMT

Probably just maintenance work at you exchange?

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 10:37:55 GMT

sync was online.
the outage was ppp, not dsl.

Feb 12 01:27:29 pppd[416]: No response to 10 echo-requests
Feb 12 01:27:29 pppd[416]: Serial link appears to be disconnected.
Feb 12 01:27:29 pppd[416]: Connect time 678.8 minutes.
Feb 12 01:27:29 pppd[416]: Sent 2060126690 bytes, received 1858985905 bytes.
Feb 12 01:27:30 radvd[12577]: attempting to reread config file
Feb 12 01:27:30 radvd[12577]: resuming normal operation
Feb 12 01:27:30 rc_service: ipv6-down 12678:notify_rc stop_radvd
Feb 12 01:27:30 dhcp6c[12540]: client6_send: transmit failed: Network is unreachable
Feb 12 01:27:30 dnsmasq[12551]: read /etc/hosts - 6 addresses
Feb 12 01:27:30 dnsmasq[12551]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:27:30 dnsmasq-dhcp[12551]: read /etc/ethers - 3 addresses
Feb 12 01:27:30 dnsmasq[12551]: using nameserver 212.159.6.10#53
Feb 12 01:27:30 dnsmasq[12551]: using nameserver 212.159.6.9#53
Feb 12 01:27:30 radvd[12577]: Exiting, sigterm or sigint received.
Feb 12 01:27:30 radvd[12577]: sending stop adverts
Feb 12 01:27:30 radvd[12577]: removing /var/run/radvd.pid
Feb 12 01:27:31 dhcp6c[12540]: client6_send: transmit failed: Network is unreachable
Feb 12 01:27:31 dnsmasq[12551]: read /etc/hosts - 6 addresses
Feb 12 01:27:31 dnsmasq[12551]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:27:31 dnsmasq-dhcp[12551]: read /etc/ethers - 3 addresses
Feb 12 01:27:31 dnsmasq[12551]: using nameserver 212.159.6.10#53
Feb 12 01:27:31 dnsmasq[12551]: using nameserver 212.159.6.9#53
Feb 12 01:27:34 WAN Connection: Fail to connect with some issues.
Feb 12 01:27:34 stop_nat_rules: apply the redirect_rules!
Feb 12 01:27:34 dnsmasq[12551]: exiting on receipt of SIGTERM
Feb 12 01:27:34 dnsmasq[12685]: started, version 2.67 cachesize 1500
Feb 12 01:27:34 dnsmasq[12685]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Feb 12 01:27:34 dnsmasq[12685]: warning: interface ppp1* does not currently exist
Feb 12 01:27:34 dnsmasq[12685]: asynchronous logging enabled, queue limit is 5 messages
Feb 12 01:27:34 dnsmasq-dhcp[12685]: DHCP, IP range 192.168.1.1 -- 192.168.1.128, lease time 1d
Feb 12 01:27:34 dnsmasq[12685]: read /etc/hosts - 6 addresses
Feb 12 01:27:34 dnsmasq[12685]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:27:34 dnsmasq-dhcp[12685]: read /etc/ethers - 3 addresses
Feb 12 01:27:34 dnsmasq[12685]: using nameserver 212.159.6.10#53
Feb 12 01:27:34 dnsmasq[12685]: using nameserver 212.159.6.9#53
Feb 12 01:27:36 pppd[416]: Connection terminated.
Feb 12 01:27:36 pppd[416]: Connect time 678.8 minutes.
Feb 12 01:27:36 pppd[416]: Sent 2060126690 bytes, received 1858985905 bytes.
Feb 12 01:27:36 pppd[416]: Sent PADT
Feb 12 01:27:36 pppd[416]: Modem hangup
Feb 12 01:28:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:29:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:30:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:32:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:33:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:34:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:35:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:37:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:38:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:39:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:40:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:42:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:43:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:44:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:45:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:47:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:48:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:49:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:50:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:52:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:53:21 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:54:36 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:55:51 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:57:06 pppd[416]: Timeout waiting for PADO packets
Feb 12 01:57:41 pppd[416]: PPP session is 257 (0x101)
Feb 12 01:57:41 pppd[416]: Connected to XXXXXXX via interface eth0
Feb 12 01:57:41 pppd[416]: Using interface ppp0
Feb 12 01:57:41 pppd[416]: Connect: ppp0 <--> eth0
Feb 12 01:57:42 pppd[416]: CHAP authentication succeeded
Feb 12 01:57:42 pppd[416]: CHAP authentication succeeded
Feb 12 01:57:42 pppd[416]: peer from calling number XXXXXXX authorized
Feb 12 01:57:42 pppd[416]: local  LL address fe80::XXXXXXX
Feb 12 01:57:42 pppd[416]: remote LL address fe80::XXXXX
Feb 12 01:57:42 pppd[416]: local  IP address 81.XXXX
Feb 12 01:57:42 pppd[416]: remote IP address 195.XXXX
Feb 12 01:57:42 pppd[416]: primary   DNS address 212.159.6.10
Feb 12 01:57:42 pppd[416]: secondary DNS address 212.159.6.9
Feb 12 01:57:42 dnsmasq[12685]: read /etc/hosts - 6 addresses
Feb 12 01:57:42 dnsmasq[12685]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:57:42 dnsmasq-dhcp[12685]: read /etc/ethers - 3 addresses
Feb 12 01:57:42 dnsmasq[12685]: using nameserver 212.159.6.9#53
Feb 12 01:57:42 dnsmasq[12685]: using nameserver 212.159.6.10#53
Feb 12 01:57:42 syslog: module nf_conntrack_ipv6 not found in modules.dep
Feb 12 01:57:42 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Feb 12 01:57:42 dnsmasq[12685]: exiting on receipt of SIGTERM
Feb 12 01:57:42 dnsmasq[12724]: started, version 2.67 cachesize 1500
Feb 12 01:57:42 dnsmasq[12724]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Feb 12 01:57:42 dnsmasq[12724]: warning: interface ppp1* does not currently exist
Feb 12 01:57:42 dnsmasq[12724]: asynchronous logging enabled, queue limit is 5 messages
Feb 12 01:57:42 dnsmasq-dhcp[12724]: DHCP, IP range 192.168.1.1 -- 192.168.1.128, lease time 1d
Feb 12 01:57:42 dnsmasq[12724]: read /etc/hosts - 6 addresses
Feb 12 01:57:42 dnsmasq[12724]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:57:42 dnsmasq-dhcp[12724]: read /etc/ethers - 3 addresses
Feb 12 01:57:42 dnsmasq[12724]: using nameserver 212.159.6.9#53
Feb 12 01:57:42 dnsmasq[12724]: using nameserver 212.159.6.10#53
Feb 12 01:57:42 rc_service: ip-up 12699:notify_rc stop_upnp
Feb 12 01:57:42 rc_service: ip-up 12699:notify_rc start_upnp
Feb 12 01:57:45 WAN Connection: WAN was restored.
Feb 12 01:57:52 syslog: module nf_conntrack_ipv6 not found in modules.dep
Feb 12 01:57:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Feb 12 01:57:52 dnsmasq[12724]: exiting on receipt of SIGTERM
Feb 12 01:57:52 dnsmasq[12756]: started, version 2.67 cachesize 1500
Feb 12 01:57:52 dnsmasq[12756]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Feb 12 01:57:52 dnsmasq[12756]: warning: interface ppp1* does not currently exist
Feb 12 01:57:52 dnsmasq[12756]: asynchronous logging enabled, queue limit is 5 messages
Feb 12 01:57:52 dnsmasq-dhcp[12756]: DHCP, IP range 192.168.1.1 -- 192.168.1.128, lease time 1d
Feb 12 01:57:52 dnsmasq[12756]: read /etc/hosts - 6 addresses
Feb 12 01:57:52 dnsmasq[12756]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:57:52 dnsmasq-dhcp[12756]: read /etc/ethers - 3 addresses
Feb 12 01:57:52 dnsmasq[12756]: using nameserver 212.159.6.9#53
Feb 12 01:57:52 dnsmasq[12756]: using nameserver 212.159.6.10#53
Feb 12 01:57:53 rc_service: dhcp6c-state 12775:notify_rc start_radvd
Feb 12 01:57:53 radvd[12779]: version 1.9.3 started
Feb 12 01:57:53 rc_service: dhcp6c-state 12775:notify_rc start_httpd
Feb 12 01:57:53 RT-AC66U: start httpd
Feb 12 01:57:53 dnsmasq[12756]: read /etc/hosts - 6 addresses
Feb 12 01:57:53 dnsmasq[12756]: read /etc/hosts.dnsmasq - 3 addresses
Feb 12 01:57:53 dnsmasq-dhcp[12756]: read /etc/ethers - 3 addresses
Feb 12 01:57:53 dnsmasq[12756]: using nameserver 212.159.6.9#53
Feb 12 01:57:53 dnsmasq[12756]: using nameserver 212.159.6.10#53

Re: ppp outages

SimonHobson — Wed, 12 Feb 2014 10:40:07 GMT

Connection drops during the early hours are "normal".
It seems BT see no problem doing lots of network maintenance and cutting large numbers of users off for a short while - and most days as well. At work I monitor a proportion of our customer's connections (mostly the ones important enough that we'd like to know there's a problem before the phone rings), and I quite regularly see a cluster of them go offline early morning - sometimes for a few minutes, sometimes for an hour or more (but that's not too common). I did query it with the wholesaler once, I got a reply back (around mid morning) to the effect that "so far today I've got 20 notices of work for tonight".
There doesn't seem to be much of a pattern about it. Sometimes it's just "random" customers, other times it's "most of them" - I guess it depends which bit of the network BT are working on.
The message to take away from this ? If you rely on your connection (as in it's business or safety critical) then don't rely on ADSL ! One of the things you get when you pay many times more for a "business grade" connection (apart from the several hundred quid a month bill) is an SLA that means they'll fix it it if breaks. With ADSL, apart from these routine drops, if it breaks then they can take a week to fix it and there's nothing you can do but sit and fume. Explaining that to customers can be "challenging" - especially the ones that refused to pay for a business grade connection to their business centre and now expect you to wave a magic wand and get all their tenants back online "yesterday"

PS - having read the additional posts while I was writing this, your sync with the exchange will be fine, the work is "somewhere" in the network between you and your ISP.

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 10:41:42 GMT

to me isnt normal, I am used to uptimes lasting several weeks.
and an outage lasting 40 mins or so isnt normal.
I attached log to above post now.
basically if noone else on the trial had this I will make a support ticket with plusnet to get an answer on the cause.

Re: ppp outages

pwatson — Wed, 12 Feb 2014 10:46:04 GMT

Most customers will have uptimes of several weeks - BT do a lot of work overnight around the country but that doesn't mean the same customers are cut off night after night!
You'll still have DSL sync as that comes from the cabinet but there's a lot of BT Wholesale systems between there and PN that may need work.

Quote from: chrcoluk
basically if noone else on the trial had this I will make a support ticket with plusnet to get an answer on the cause.

Really? Aren't PN support overloaded enough without answering why a connection went down during a maintenance window, came back up and is working perfectly...

Re: ppp outages

AndyH — Wed, 12 Feb 2014 10:49:51 GMT

@ chrcoluk - What's your area code?

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 10:57:38 GMT

LE3

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 10:58:38 GMT

Quote from: pwatson
Most customers will have uptimes of several weeks - BT do a lot of work overnight around the country but that doesn't mean the same customers are cut off night after night!
You'll still have DSL sync as that comes from the cabinet but there's a lot of BT Wholesale systems between there and PN that may need work.

3 times in space of 4 weeks is excessive.
if its due to trial and something plusnet did no problem, as I accept it been a trialist, if its due to BT on normal paid for service, its excessive.
telling me it 'may' be this or that isnt too helpful.
Its pretty obvious its either maintenance or a unplanned outage, thats easy to guess. The question is what it is exactly.

Re: ppp outages

pwatson — Wed, 12 Feb 2014 11:00:23 GMT

Quote from: AndyH
@ chrcoluk - What's your area code?

LE3 doesn't help - what's your dialling code

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 11:00:48 GMT

Quote from: pwatson
Quote from: AndyH
@ chrcoluk - What's your area code?

LE3 doesn't help - what's your dialling code

0116

Re: ppp outages

AndyH — Wed, 12 Feb 2014 11:08:16 GMT

I can't see anything for that area code.
I don't think it was PlusNet's end because no one else seemed to have those brief outages on their graphs.
There could have been some unplanned maintenance work at your exchange, or further upstream. The 13:30 one seemed to benefit you as it lowered your ping according to the graph.

Re: ppp outages

chrcoluk — Wed, 12 Feb 2014 11:09:42 GMT

Quote from: AndyH
I can't see anything for that area code.
I don't think it was PlusNet's end because no one else seemed to have those brief outages on their graphs.
There could have been some unplanned maintenance work at your exchange, or further upstream. The 13:30 one seemed to benefit you as it lowered your ping according to the graph.

ok thanks for checking andy, out of interest is it easy for me to check somewhere on a site?
I will ask plusnet if they can find a reason for it.
I am assuming the latency change was due to changing plusnet gateways as each gateway has different base latency.
As a reminder the afternoon outage was an engineer visit, my modem was unplugged. I am talking about the 1.20am to 2am outage.

Re: ppp outages

AndyH — Wed, 12 Feb 2014 11:21:32 GMT

http://status.zen.co.uk/broadband/ Shows faults and upcoming maintenance. You can input your area code.
http://usertools.plus.net/exchanges/mso.php
http://portal.plus.net/supportpages.html?a=2&support_action=messages&ispservice_id=adsldial
http://clueless.aa.net.uk/pew.cgi
If there is an outage between 00:00 and 06:00, then it is normally always some kind of BT maintenance. It's not too uncommon to have multiple outages in a month, particularly if BT are doing some major work at your exchange or nearest node. It is normally fairly minimal though (5 min outages etc.)

Re: ppp outages

SimonHobson — Wed, 12 Feb 2014 12:23:24 GMT

Quote from: chrcoluk
3 times in space of 4 weeks is excessive.

While it's unusual, it's not anything you'll get anywhere with. Like I said, it's one of the things that comes with the low price tag of ADSL.
If you want a service with guaranteed uptimes and advance notification of any maintenance then you can have it - but you'll add at least one zero onto the monthly price.