Trinitarian broadband!!!

[#1]

Avodat,
Not entirely sad news - it was not a Kernel Warm Restart.  Can you please look at / post the RouterStats graph covering the restart, both Rx and if you gave it Tx plots.
@Adam,
This is the first restart since the firmware upgrade late Friday morning.  It fits the perceived 3 day events first reported, however am I correct that this line is still in a DLM 10 day training period?  Is there any DLM information advising of the reason for the resynch?  Is it possible to state with confidence that this synch was / was not due to training behaviour?  This synch is a little lower that it was.
Kevin

[#2]

Townman - I do not have that data. RouterStats is currently saying it has only been running for a couple of hours, probably because I had to take the computer out of the house today as the builders are in and it is far too noisy to work.

[#3]

The length of time RouterStats reports as being up is that from the router's session connectivity duration - in your case the time since 14:30 today.
It is therefore possible that RouterStats did record the events if it was powered on within reach of the router.  See graphs in the RS folder.
I hope that the builders are soon finished and do not damage your phone line / extensions.  Talking of which, were they using power tools, particularly things with powerful motors - circular saws, angle grinders... - around 14:30?
Kevin

[#4]

RouterStats was re-started when I switched on the computer again, back indoors, a couple of hours ago.
I don't know what the builders were using - when I left it was a lot of banging!  They are ripping out the bathroom and putting in a new one. I did check that they had not switched off the power at any time, they say 'no' and I cannot see why they would need to have done so.

[#5]

It was a clutch at a straw - not turning the power off (good thought) - but rather the possibility that a PowerBook starting up could gave day's end a small power dip, or the electrical noise (EMI or RFI) of the tool could have brought the line down.
Given the lack of obvious explanations to your connectivity issues, one has to be open to all possibilities from all sources.  RFI and EMI have not been explored (whatever source) - until today all disconnections which were not Kernel Warm Restarts we have been able to explain as some facet of changes being made to the line by PlusNET.

@Adam,
Is there any chance that someone in faults ran an intrusive test this afternoon? 

[#6]

<173> Sep  1 14:30:41 xDSL linestate down
<173> Sep  1 14:33:30 xDSL linestate up
Looks as though it could be a line test to me. I would think Adam may be able to confirm that. It may even be on the ticket.
You posted as I was typing Kevin and I've been pinging you all day

[#7]

<81> Sep  2 00:00:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 223.83.187.162 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 00:12:04 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 189.125.28.190 Dst ip: 87.112.59.198 Type: Time Exceeded Code: Time to Live exceeded in Transit
<81> Sep  2 00:27:10 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 71.102.5.242 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 00:34:25 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 173.55.67.18 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 00:53:43 SNTP Synchronised to server: 212.159.6.9
<81> Sep  2 01:03:01 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 31.209.98.165 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 01:05:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 27.24.20.191 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 01:53:43 SNTP Synchronised again to server: 212.159.6.9
<102> Sep  2 02:53:43 SNTP Synchronised again to server: 212.159.6.9
<102> Sep  2 03:53:43 SNTP Synchronised again to server: 212.159.6.9
<173> Sep  2 04:11:26 xDSL linestate down
<173> Sep  2 04:11:43 xDSL linestate down
<132> Sep  2 04:12:13 PPP link down (Internet) [87.112.59.]

<173> Sep  2 04:12:14 xDSL linestate down
<173> Sep  2 04:12:40 xDSL linestate up (ITU-T G.992.5; downstream: 12594 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.8 dBm; line Attenuation Down: 22.5 dB, Up: 10.7 dB; snr Margin Down: 6.1 dB, Up: 31.5 dB)
<38> Sep  2 04:12:42 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  2 04:12:42 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  2 04:12:42 PPP CHAP Receive success (Internet)
<132> Sep  2 04:12:46 PPP link up (Internet) [80.189.200.]

<14> Sep  2 04:13:26 CONFIGURATION saved by TR69
<173> Sep  2 04:16:18 xDSL linestate down
<173> Sep  2 04:16:35 xDSL linestate down
<132> Sep  2 04:17:03 PPP link down (Internet) [80.189.200.74]

<173> Sep  2 04:17:05 xDSL linestate down
<173> Sep  2 04:17:33 xDSL linestate up (ITU-T G.992.5; downstream: 12523 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.9 dBm; line Attenuation Down: 22.5 dB, Up: 10.7 dB; snr Margin Down: 6.1 dB, Up: 30.9 dB)
<38> Sep  2 04:17:38 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  2 04:17:38 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  2 04:17:38 PPP CHAP Receive success (Internet)
<132> Sep  2 04:17:39 PPP link up (Internet) [46.208.12.]

<14> Sep  2 04:18:20 CONFIGURATION saved by TR69
<81> Sep  2 04:46:06 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 83.87.250.77 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 04:53:43 SNTP Synchronised to server: 212.159.13.49
<81> Sep  2 05:12:26 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 74.124.114.255 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 05:37:49 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 125.119.146.251 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 05:53:44 SNTP Synchronised to server: 212.159.6.9
<102> Sep  2 06:53:44 SNTP Synchronised to server: 212.159.13.49
<81> Sep  2 06:57:45 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 173.51.142.160 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 07:01:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 190.96.190.79 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 07:36:19 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 1.11.97.196 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 07:51:51 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 125.73.196.162 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 07:53:44 SNTP Synchronised to server: 212.159.6.9
<81> Sep  2 08:03:50 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 113.250.79.59 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<37> Sep  2 08:04:28 LOGIN User admin logged in on TELNET (192.168.1.66)
<81> Sep  2 08:28:19 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 179.132.101.235 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 08:53:44 SNTP Synchronised again to server: 212.159.6.9
<37> Sep  2 09:35:25 LOGIN wireless station [a0:82:1f:6e:de:55] can't get authorized.  
<102> Sep  2 09:53:44 SNTP Synchronised again to server: 212.159.6.9
<81> Sep  2 10:51:48 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 70.109.46.14 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 10:53:44 SNTP Synchronised to server: 212.159.13.49
<81> Sep  2 11:02:29 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 218.220.25.102 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 11:07:07 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 77.191.84.135 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Sep  2 11:07:10 FIREWALL replay check (1 of 2): Protocol: ICMP  Src ip: 77.191.84.135 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Communication Administratively Prohibited
<102> Sep  2 11:53:45 SNTP Synchronised again to server: 212.159.13.49
<84> Sep  2 11:57:14 IDS proto parser : tcp null port (1 of 1) : 123.151.42.61   46.208.12.43    40    40  TCP 12201->0 [S.....] seq 75793588 ack 0 win 8192
<81> Sep  2 12:21:51 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 91.77.101.162 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 12:38:22 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 180.164.205.243 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 12:42:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 197.202.132.185 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 12:42:17 FIREWALL replay check (1 of 2): Protocol: ICMP  Src ip: 197.202.132.185 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 12:53:45 SNTP Synchronised again to server: 212.159.13.49
<81> Sep  2 13:34:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 95.91.239.62 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 13:53:45 SNTP Synchronised to server: 212.159.6.9
<81> Sep  2 14:04:19 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 200.63.22.251 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 14:53:45 SNTP Synchronised to server: 212.159.13.49
<102> Sep  2 15:53:45 SNTP Synchronised to server: 212.159.6.9
<81> Sep  2 15:58:14 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 192.99.35.5 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 16:23:35 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 203.211.150.117 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 16:53:45 SNTP Synchronised again to server: 212.159.6.9
<37> Sep  2 17:28:12 LOGIN User logged in on [HTTP] (from 192.168.1.)
<81> Sep  2 17:28:35 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 95.252.104.62 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 17:33:55 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 210.56.24.233 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 17:53:46 SNTP Synchronised again to server: 212.159.6.9
<81> Sep  2 18:06:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 117.229.213.189 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 18:10:30 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 89.124.243.71 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 18:53:45 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 115.161.101.54 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 18:53:46 SNTP Synchronised to server: 212.159.13.50
<81> Sep  2 18:58:20 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 114.29.72.176 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 19:09:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 123.117.209.209 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  2 19:15:07 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 191.162.208.59 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  2 19:53:46 SNTP Synchronised again to server: 212.159.13.50
<84> Sep  2 20:20:21 IDS proto parser : tcp data on syn segment (1 of 1) : 50.22.53.71     46.208.12.43    1010  231 TCP 22->26571 [S.A...] seq 4110682502 ack 768609323 win 63114
<102> Sep  2 20:53:46 SNTP Synchronised to server: 212.159.6.9
<81> Sep  2 21:03:29 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 125.72.173.61 Dst ip: 46.208.12.43 Type: Destination Unreachable Code: Port Unreacheable
<173> Sep  2 21:27:55 xDSL linestate down
<173> Sep  2 21:28:12 xDSL linestate down
<132> Sep  2 21:28:36 PPP link down (Internet) [46.208.12.]

<173> Sep  2 21:28:42 xDSL linestate down
<173> Sep  2 21:29:08 xDSL linestate up (ITU-T G.992.5; downstream: 12639 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.9 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.2 dB)
<38> Sep  2 21:29:14 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  2 21:29:14 PPP CHAP Receive challenge from rhost PCL-AG08 (Internet)
<38> Sep  2 21:29:14 PPP CHAP Receive success (Internet)
<132> Sep  2 21:29:15 PPP link up (Internet) [87.113.163.]

<14> Sep  2 21:29:55 CONFIGURATION saved by TR69
<173> Sep  2 21:32:14 xDSL linestate down
<173> Sep  2 21:32:33 xDSL linestate down
<132> Sep  2 21:32:55 PPP link down (Internet) [87.113.163.]

<173> Sep  2 21:33:03 xDSL linestate down
<173> Sep  2 21:33:29 xDSL linestate up (ITU-T G.992.5; downstream: 12560 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.7 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.5 dB)
<38> Sep  2 21:33:33 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  2 21:33:33 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  2 21:33:34 PPP CHAP Receive success (Internet)
<132> Sep  2 21:33:34 PPP link up (Internet) [80.189.15.]

<14> Sep  2 21:34:14 CONFIGURATION saved by TR69
<173> Sep  2 21:47:48 xDSL linestate down
<173> Sep  2 21:48:05 xDSL linestate down
<173> Sep  2 21:48:36 xDSL linestate down
<132> Sep  2 21:48:37 PPP link down (Internet) [80.189.15.48]

<173> Sep  2 21:49:02 xDSL linestate up (ITU-T G.992.5; downstream: 12512 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.9 dBm; line Attenuation Down: 23.0 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.3 dB)
<38> Sep  2 21:49:08 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  2 21:49:09 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  2 21:49:09 PPP CHAP Receive success (Internet)
<132> Sep  2 21:49:12 PPP link up (Internet) [84.51.162.]

<14> Sep  2 21:49:52 CONFIGURATION saved by TR69
<37> Sep  2 21:50:20 LOGIN User logged in on [HTTP] (from 192.168.1.)

Date of copy graph should read 020914.

[#8]

<81> Sep  3 00:32:49 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 186.48.68.93 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  3 00:42:34 FIREWALL replay check (1 of 1): Protocol: ICMP  Src ip: 82.10.56.194 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Host Unreacheable
<102> Sep  3 00:53:25 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  3 00:53:47 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 84.133.37.43 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Sep  3 00:53:50 FIREWALL replay check (1 of 1): Protocol: ICMP  Src ip: 84.133.37.43 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Communication Administratively Prohibited
<102> Sep  3 01:53:25 SNTP Synchronised again to server: 212.159.6.10
<102> Sep  3 02:53:25 SNTP Synchronised to server: 212.159.13.50
<81> Sep  3 03:17:34 FIREWALL replay check (1 of 2): Protocol: ICMP  Src ip: 82.10.56.194 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Host Unreacheable
<102> Sep  3 03:53:26 SNTP Synchronised to server: 212.159.6.10
<81> Sep  3 04:07:31 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 82.10.56.194 Dst ip: 84.51.162.199 Type: Destination Unreachable Code: Host Unreacheable
<173> Sep  3 04:20:30 xDSL linestate down
<173> Sep  3 04:20:47 xDSL linestate down
<132> Sep  3 04:21:11 PPP link down (Internet) [84.51.162.]

<173> Sep  3 04:21:17 xDSL linestate down
<173> Sep  3 04:21:43 xDSL linestate up (ITU-T G.992.5; downstream: 12538 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.9 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.1 dB)
<38> Sep  3 04:21:46 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 04:21:46 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  3 04:21:47 PPP CHAP Receive success (Internet)
<132> Sep  3 04:21:47 PPP link up (Internet) [146.200.129.]

<14> Sep  3 04:22:28 CONFIGURATION saved by TR69
<81> Sep  3 04:22:30 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 24.35.114.25 Dst ip: 146.200.129.130 Type: Destination Unreachable Code: Host Unreacheable
<173> Sep  3 04:43:00 xDSL linestate down
<173> Sep  3 04:43:18 xDSL linestate down
<173> Sep  3 04:43:48 xDSL linestate down
<132> Sep  3 04:43:52 PPP link down (Internet) [146.200.129.]

<173> Sep  3 04:44:14 xDSL linestate up (ITU-T G.992.5; downstream: 12605 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.6 dBm; line Attenuation Down: 23.0 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.3 dB)
<38> Sep  3 04:44:17 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 04:44:18 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  3 04:44:18 PPP CHAP Receive success (Internet)
<132> Sep  3 04:44:19 PPP link up (Internet) [80.189.150.]

<14> Sep  3 04:45:22 CONFIGURATION saved by TR69
<102> Sep  3 04:53:26 SNTP Synchronised again to server: 212.159.6.10
<173> Sep  3 05:11:46 xDSL linestate down
<173> Sep  3 05:12:03 xDSL linestate down
<173> Sep  3 05:12:33 xDSL linestate down
<132> Sep  3 05:12:35 PPP link down (Internet) [80.189.150.]

<173> Sep  3 05:12:59 xDSL linestate up (ITU-T G.992.5; downstream: 12583 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.9 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.7 dB)
<38> Sep  3 05:13:03 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 05:13:03 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  3 05:13:04 PPP CHAP Receive success (Internet)
<132> Sep  3 05:13:07 PPP link up (Internet) [146.200.29.]

<14> Sep  3 05:13:48 CONFIGURATION saved by TR69
<102> Sep  3 05:53:26 SNTP Synchronised again to server: 212.159.6.10
<173> Sep  3 05:53:43 xDSL linestate down
<173> Sep  3 05:54:00 xDSL linestate down
<132> Sep  3 05:54:24 PPP link down (Internet) [146.200.29.]

<173> Sep  3 05:54:30 xDSL linestate down
<173> Sep  3 05:54:56 xDSL linestate up (ITU-T G.992.5; downstream: 12765 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.6 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.4 dB)
<38> Sep  3 05:54:58 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 05:54:59 PPP CHAP Receive challenge from rhost PCL-AG03 (Internet)
<38> Sep  3 05:54:59 PPP CHAP Receive success (Internet)
<132> Sep  3 05:54:59 PPP link up (Internet) [87.114.48.]

<14> Sep  3 05:55:39 CONFIGURATION saved by TR69
<81> Sep  3 06:16:17 FIREWALL icmp check (1 of 6): Protocol: ICMP  Src ip: 208.116.1.150 Dst ip: 87.114.48.23 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  3 06:29:22 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 60.215.187.139 Dst ip: 87.114.48.23 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  3 06:31:48 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 98.108.221.243 Dst ip: 87.114.48.23 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  3 06:45:08 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 72.65.226.164 Dst ip: 87.114.48.23 Type: Destination Unreachable Code: Port Unreacheable
<173> Sep  3 06:47:20 xDSL linestate down
<173> Sep  3 06:47:37 xDSL linestate down
<132> Sep  3 06:48:05 PPP link down (Internet) [87.114.48.]

<173> Sep  3 06:48:07 xDSL linestate down
<173> Sep  3 06:48:33 xDSL linestate up (ITU-T G.992.5; downstream: 12759 kbit/s, upstream: 440 kbit/s; output Power Down: 20.9 dBm, Up: 12.8 dBm; line Attenuation Down: 23.0 dB, Up: 10.8 dB; snr Margin Down: 6.3 dB, Up: 31.0 dB)
<38> Sep  3 06:48:39 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 06:48:40 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Sep  3 06:48:40 PPP CHAP Receive success (Internet)
<132> Sep  3 06:48:41 PPP link up (Internet) [87.115.250.]

<14> Sep  3 06:49:21 CONFIGURATION saved by TR69
<102> Sep  3 06:53:26 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  3 07:09:48 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 186.45.90.161 Dst ip: 87.115.250.123 Type: Destination Unreachable Code: Port Unreacheable
{admin}

[#9]

Oh dear, that is not looking so clever. I've listed the start of each xDSL linestate down below - 10 events in just over 24hrs. The last 5 are also clearly displayed on the RouterStats graphs.
<173> Sep  2 04:11:26 xDSL linestate down
<173> Sep  2 04:16:18 xDSL linestate down
<173> Sep  2 21:27:55 xDSL linestate down
<173> Sep  2 21:32:14 xDSL linestate down
<173> Sep  2 21:47:48 xDSL linestate down
<173> Sep  3 04:20:30 xDSL linestate down
<173> Sep  3 04:43:00 xDSL linestate down
<173> Sep  3 05:11:46 xDSL linestate down
<173> Sep  3 05:53:43 xDSL linestate down
<173> Sep  3 06:47:20 xDSL linestate down
The timings of these "seem" to coincide around dusk and just before dawn, the most recent near dawn ones are those on the RouterStats graphs.
Let's try and eliminate any potential red herrings.
avodat, I assume you didn't have and thunderstorms maybe even a couple of miles away during those sort of times, and also you weren't up at 4 o'clock in the morning doing anything - I expect the answer will be No 
I doubt that it will be overnight work going on inside your local exchange because of the pattern of the timings.
Do you, or a very near neighbour have any dusk to dawn lights? or is there a street light anywhere very close by?
Has your street lighting had any changes made recently.(since April/May)  A lot of local authorities are changing sensors so they are off for most of the "early" hours, or even changing the type of lighting to a more energy efficient type.
And I'm certainly not going to forget this one, do you or a very near neighbour have any CCTV equipment operating 24/7 that has IR illumination for after dark?
Are any of your neighbours experiencing similar problems with their broadband?
I have very little doubt, that your internal wiring will be related to the "extra" sensitivity to issues of this kind mentioned above that could cause this sort of thing. However your ability to reduce that sensitivity by making any changes is hampered by the fact that you do not have a modern NTE5 Master Line Box. I thought it was part of the standard service level agreement these days that one was fitted? (that means it's the provider's problem to get one fitted FOC when there are faults).
Can I just double check avodat, roughly how far it is from the current master socket in the hall to the socket you are using?
Are you still plugged in at the master socket btw?

[#10]

Morning avodat,
Sorry to see we still appear to be affected by the drops I thought that we had managed to crack something with the firmware update however this may not be the case. I can certainly confirm that no further intrusive testing was carried out on or around the first drop, in fact, everything I've run personally has been non-intrusive and no further action has been taken on the faults ticket.
I did however, run an intrusive test this morning to see if we have anything showing up in the diagnostics testing. The DLM hasn't budged and we still have no banding or speed restrictions applied. The overall testing returned no network fault so again we're in a place where nothing can be raised on our side without the risk of there being charges for the engineer visit.
Connection wise, here is what we're seeing on the RADIUS graphing:
<img src="http://community.plus.net/visualradius/generated/image14097332751597.png"/>
Thanks for updating on the owner of the line, would there be a possibility that the landlord could be contacted in order to have them call the provider and have some tests run on the line? Guaranteed, we don't seem to have any audible noise on the line and the phone service is working however we may well have something intermittent happening that's affecting the broadband and causing the drops.
Aside from this, I'm going to have a sit down with one of the more senior faults chaps to see if he can take a look over the results of the BRAT graphing we have just in case this can reveal anything more. After speaking with one of the senior faults agents it looks like we may have a couple of things to try in order to stabilise the line. First up, we're going to have another tinker with the SNR to see if this will help keep the connection up (it appears the last reset completed but nothing changed), after this I think we should look at replacing the router as a test and then finally I'm hoping that this could possibly give us some leverage on getting an engineer out but I can't promise anything at the moment. We believe we should push to get the master socket replaced with something newer and have the copper checked as well.
I'll check back on the line stats in 4 hours and make sure we see a change with the SNR and we should then be able to see if this resolves the issue and where we go next.

[#11]

Adam, several points.
This pattern of disconnects is completely different from the previous issue, the firmware upgrade appears to have alleviated that.
Whether or not the previous and this may in some way be related is difficult to conclude other than my comments above about wiring.
The newer firmware is more stable and has better noise immunity.
Tinkering with the SNRM is only attempting to mask the problem and NOT deal with the root cause.
Ownership of the property is irrelevant to the line if avodat actually pays the line rental and the account is in his name.
Further than that and irrespective of ownership, Plusnet are capable of and should run full detailed copper diagnostic tests to see if there is anything that can be referred to the line provider. The customer is complaining of a Broadband problem, it's Plusnet's responsibility to diagnose the fault, if any, with the service.
Tinkering with settings should be a last resort in the absence of all other avenues having been fully explored.

[#12]

Quote from: Anotherone

<173> Sep  1 14:30:41 xDSL linestate down <173> Sep  1 14:33:30 xDSL linestate up Looks as though it could be a line test to me. I would think Adam may be able to confirm that. It may even be on the ticket.

For the record, I wasn't suggesting that you had done a line test Adam, merely that someone probably has, whether or not it was recorded is another matter, the duration is typical of a full line test.

[#13]

and on, and on, and on it goes, though these, or some of may be down to the builders here - but they only arrived at 9.30 and so could not be the source of the earlier drops.  Builder just used the cutting equipment - no problem shown on the connection!  Graph just been added for the drops shown below
syslog msgbuf show hist=enabled
<85> Jan  1 00:00:08 FIREWALL has been enabled
<4> Jan  1 00:00:16 KERNEL Cold restart
<85> Jan  1 00:00:24 FIREWALL event (1 of 1): created rules
<85> Jan  1 00:00:24 FIREWALL event (1 of 1): modified rules
<82> Jan  1 00:00:32 UPnP framework disabled
<85> Jan  1 00:00:32 FIREWALL has been enabled
<82> Jan  1 00:00:34 UPnP framework disabled
<82> Jan  1 00:00:36 UPnP framework disabled
<82> Jan  1 00:00:42 UPnP framework enabled
<85> Jan  1 00:00:46 FIREWALL level changed to Standard.
<85> Jan  1 00:00:46 FIREWALL event (1 of 1): deleted rules
<148> Jan  1 00:00:46 DHCS server up
<173> Jan  1 00:00:54 xDSL linestate down
<3> Jan  1 00:00:59 [ANTI_SPOOFD] (err) llist_getobject_at for ENV.ANTI_SPOOFD's value failed

<37> Jan  1 00:01:24 LOGIN User logged in on TELNET (192.168.1.)
<173> Jan  1 00:01:24 xDSL linestate down
<173> Jan  1 00:01:50 xDSL linestate up (ITU-T G.992.5; downstream: 12910 kbit/s, upstream: 440 kbit/s; output Power Down: 20.8 dBm, Up: 12.7 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.4 dB)
<38> Jan  1 00:01:52 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Jan  1 00:01:53 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Jan  1 00:01:53 PPP CHAP Receive success (Internet)
<132> Jan  1 00:01:56 PPP link up (Internet) [80.189.57.]

<173> Jan  1 00:03:21 xDSL linestate down
<132> Jan  1 00:04:03 PPP link down (Internet) [80.189.57.]

<173> Jan  1 00:04:17 xDSL linestate down
<173> Jan  1 00:04:32 xDSL linestate down
<173> Jan  1 00:05:13 xDSL linestate down
<173> Jan  1 00:05:43 xDSL linestate down
<173> Jan  1 00:06:09 xDSL linestate up (ITU-T G.992.5; downstream: 12903 kbit/s, upstream: 440 kbit/s; output Power Down: 20.9 dBm, Up: 12.9 dBm; line Attenuation Down: 22.5 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.6 dB)
<38> Jan  1 00:06:21 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Jan  1 00:06:21 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Jan  1 00:06:22 PPP CHAP Receive success (Internet)
<132> Jan  1 00:06:25 PPP link up (Internet) [80.189.147.]

<14> Jan  1 00:06:40 CONFIGURATION saved by TR69
<100> Jan  1 00:06:42 SNTP Unable to contact server: 198.18.1.11
<99> Sep  3 08:46:07 SNTP Systemtime update: time setting 00:11:42 > new time setting: 08:46:07
<102> Sep  3 08:46:07 SNTP Synchronised to server: 212.159.6.10
<173> Sep  3 10:24:48 xDSL linestate down
<132> Sep  3 10:25:38 PPP link down (Internet) [80.189.147.]

<173> Sep  3 10:25:57 xDSL linestate down
<173> Sep  3 10:26:52 xDSL linestate down
<173> Sep  3 10:27:22 xDSL linestate down
<173> Sep  3 10:27:48 xDSL linestate up (ITU-T G.992.5; downstream: 12937 kbit/s, upstream: 440 kbit/s; output Power Down: 20.9 dBm, Up: 12.9 dBm; line Attenuation Down: 23.0 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.0 dB)
<38> Sep  3 10:27:55 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  3 10:27:56 PPP CHAP Receive challenge from rhost PTW-AG03 (Internet)
<38> Sep  3 10:27:56 PPP CHAP Receive success (Internet)
<132> Sep  3 10:27:57 PPP link up (Internet) [146.90.167.]

<14> Sep  3 10:28:37 CONFIGURATION saved by TR69
<81> Sep  3 10:29:29 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 24.168.135.218 Dst ip: 146.90.167.152 Type: Destination Unreachable Code: Host Unreacheable
<102> Sep  3 10:46:08 SNTP Synchronised to server: 212.159.13.50
<102> Sep  3 11:46:08 SNTP Synchronised to server: 212.159.6.10
{admin}

[#14]

Answers in red:
The timings of these "seem" to coincide around dusk and just before dawn, the most recent near dawn ones are those on the RouterStats graphs.
Let's try and eliminate any potential red herrings.
It is, again, the 3rd day
avodat, I assume you didn't have and thunderstorms maybe even a couple of miles away during those sort of times, and also you weren't up at 4 o'clock in the morning doing anything - I expect the answer will be No  Wink    You are correct - no
I doubt that it will be overnight work going on inside your local exchange because of the pattern of the timings.
Do you, or a very near neighbour have any dusk to dawn lights? or is there a street light anywhere very close by? No, for me, no for neighbours
Has your street lighting had any changes made recently.(since April/May)  A lot of local authorities are changing sensors so they are off for most of the "early" hours, or even changing the type of lighting to a more energy efficient type. No, new lighting was put a few years ago
And I'm certainly not going to forget this one, do you or a very near neighbour have any CCTV equipment operating 24/7 that has IR illumination for after dark? No, for me, not that I am aware of for neighbours where that has been installed since May/June)
Are any of your neighbours experiencing similar problems with their broadband?  I don't know - most are professionals who are at work all day, and some very senior, retirees
I have very little doubt, that your internal wiring will be related to the "extra" sensitivity to issues of this kind mentioned above that could cause this sort of thing. However your ability to reduce that sensitivity by making any changes is hampered by the fact that you do not have a modern NTE5 Master Line Box. I thought it was part of the standard service level agreement these days that one was fitted? (that means it's the provider's problem to get one fitted FOC when there are faults). I don't know - it is not my phone, it comes with the tied house - if it was mine I would go for a better level of service, but I can't[color=red][/color]
Can I just double check avodat, roughly how far it is from the current master socket in the hall to the socket you are using?  It is plugged into the master socket
Are you still plugged in at the master socket btw?  Yes

[#15]

Hello avodat, I meant the socket that you normally use.
Who pays your landline bill and whose name is it in, your's or the landlord's?