topic Re: Draytek 2850n Plusnet FTTC fibre problem in Full Fibre

Draytek 2850n Plusnet FTTC fibre problem

BusterRaid — Fri, 06 May 2016 17:56:06 GMT

Hi.

Trying to use a Draytek 2850n Vigor VDSL2 router with Plusnet FTTC broadband.

The Plusnet supplied router works fine and seems stable.

I want to use the Draytek for the VPN server it offers and other features.

If I try to use the Draytek, it connects for a short while (seconds to minutes) then looses the connection. It has a ponder and then reconnects. Repeat.

The Draytek firmware is from the UK Dryatek site: 3.6.8.2_2471201 (latest 20160506).

I’ve tried a few on the Draytek FTP site with no luck.

The connection was new to the premises and its provisioning should have been, but wasn’t smooth. Its via a new BT Openreach “Version 3” faceplate/connection box – one connection for phone, one for internet – meaning no ADSL filter is required.

I fully reset the Draytek so no old settings should be present, then configured the required settings.

To swap over from the Plusnet router to the Draytek I “politely” disconnect the connection via the GUI, pull the RJ11 cable and leave it about 15 mins. I then plug it in to the Draytek and click “Dial PPPoe”. The Draytek then connects.

Below is a summary of the changes I made to the router config.

WAN >> General Setup
WAN2: Enabled: No
WAN3: Enabled No

WAN >> General Setup
Wan1

DSL Mode: VDSL only
Vlan Tag Insertion (VDSL): Enable
Tag value: 101
Active Mode: Always On
Load Balance: (off) unchecked

WAN >> Internet Access
Wan1

Service Name: (blank)
Username :xxx@sdds
Password:xxxx

Protocol: PPPoE

MTU: 1492
Fixed IP: No (Dynamic IP)

LAN >> General Setup

Primary IP Address: 212.159.13.49
Secondary IP Address: 212.159.13.50

The Router is set to pick up the time from the browser (I go in and force an update).

I have logged into the Plusnet Members Centre and disabled the “automatic router config” option.

The Plusnet managed firewall is also disabled.

In the Syslog extract below, I show the WAN and CONNECTION Syslog extracts.

Note the first timestamp is “system” time, the second is “router” time – I will always refer to “router” time in the below.

They both start at the same time with the VDSL connection in the down state at 16:04:11.

During the period shown, the connection comes back up – reported at 16:06:14 (and I can browse the internet).

At 16:15:28 we see the beginning of the end for the connection:

WAN Log - 16:15:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) TermReq Identifier:0x25 ##
Connection Log - 16:15:28 Vigor PPP Closed : No Echo Response (PPPoE)

… which as I understand it, is the router saying it’s not had a suitable or timely response so it’s terminating the connection.

Below the Syslog output is the VDSL status, as reported by the Draytek.

This is driving me nuts. I’ve used Draytek’s for years and the Plusnet ADSL connection we had (at a different location) was serviced by a Draytek for 5 years, no problem.

I can’t see, and am not knowledgeable enough to see the “smoking gun” to identify the culprit. Is it the Draytek not sending the correct echo requests, the peer not responding correctly or in a timely fashion or something completely different?

I’ve shouted at it, in the most base and profane terms and have promised a furious and gruesome end to the device unless it works, but all to no avail.

Any ideas?

Thank you.

Note the first time stamp is system time and the second is router time.

Syslog – WAN.

16:04:18 16:04:11 Vigor WAN 1 is down.
16:04:31 16:04:25 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:31 16:04:25 Vigor WAN1 PPPoE ==> V:1 T:1 PADI ID:0
16:04:37 16:04:31 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:04:49 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:04:49 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:49 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:49 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:50 16:04:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:51 16:04:44 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:51 16:04:44 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:51 16:04:44 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:53 16:04:46 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:53 16:04:46 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:53 16:04:46 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:53 16:04:46 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:56 16:04:49 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:56 16:04:49 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:04:56 16:04:49 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:01 16:04:54 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:01 16:04:55 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:05:03 16:04:56 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:03 16:04:56 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:03 16:04:57 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:13 16:05:07 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:05:14 16:05:07 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:16 16:05:09 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:17 16:05:10 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:18 16:05:11 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:18 16:05:11 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:20 16:05:13 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:25 16:05:18 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:26 16:05:19 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:05:30 16:05:23 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:32 16:05:24 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:35 16:05:27 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:38 16:05:31 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:05:41 16:05:34 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:45 16:05:38 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:45 16:05:38 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:46 16:05:39 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:46 16:05:39 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:46 16:05:39 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:05:50 16:05:43 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:06:02 16:05:55 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:06:14 16:06:07 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:0
16:06:16 16:06:09 Vigor WAN1 PPPoE ==> V:1 T:1 PADT ID:530
16:06:16 16:06:09 Vigor WAN1 PPPoE <== V:1 T:1 PADT ID:530
16:06:17 16:06:10 Vigor WAN1 PPPoE <== V:1 T:1 PADO ID:0
16:06:17 16:06:10 Vigor WAN1 PPPoE ==> V:1 T:1 PADR ID:0
16:06:17 16:06:10 Vigor WAN1 PPPoE <== V:1 T:1 PADS ID:533
16:06:17 16:06:10 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x00 MRU: 1492 ##
16:06:17 16:06:10 Vigor WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0xB8 MRU: 1492 Authentication Type: CHAP 05 Magic Number: 0x2beb1be9 ##
16:06:17 16:06:10 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0xB8 MRU: 1492 Authentication Type: CHAP 05 Magic Number: 0x2beb1be9 ##
16:06:17 16:06:10 Vigor WAN1 PPPoE <== Protocol:LCP(c021) ConfAck Identifier:0x00 MRU: 1492 ##
16:06:17 16:06:10 Vigor WAN1 PPPoE <== Protocol:CHAP(c223) Challenge Identifier:0x01 3c ec 88 58 d2 d7 9c 78 b4 dd af 0c f6 86 e0 ac 2f 6b 2e 73 b6 0e d1 c9 cf 3f ad ee d7 37 63 4a 24 ec 22 77 44 be 6f f8 1d 1f 05 14 a6 65 40 d5 d0 6e c8 88 fb 9a d1 cc 59 00 3b 32 37 61 63 63 2d.....
16:06:17 16:06:10 Vigor WAN1 PPPoE ==> Protocol:CHAP(c223) Response Identifier:0x01 10 4d 95 e6 fa 68 74 ef 6d 64 f3 94 dd 8c 5d 9e a1 69 6e 65 74 70 6e 63 62 31 40 70 6c 75 73 64 73 6c 2e 6e 65 74 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0x71 Authentication Type: CHAP 05 Magic Number: 0x48f6da15 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x01 MRU: 1492 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0x71 Authentication Type: CHAP 05 Magic Number: 0x48f6da15 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE <== Protocol:LCP(c021) ConfAck Identifier:0x01 MRU: 1492 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE <== Protocol:CHAP(c223) Challenge Identifier:0x58 15 f7 37 e3 13 c8 e8 30 cd 49 e0 4b d4 16 70 fb 24 de 4e 06 93 57 4a 55 4e 4f 53 ##
16:06:18 16:06:10 Vigor WAN1 PPPoE ==> Protocol:CHAP(c223) Response Identifier:0x58 10 05 e8 c0 83 04 9e 3c 46 4e d7 c0 e1 da 33 c4 f7 69 6e 65 74 70 6e 63 62 31 40 70 6c 75 73 64 73 6c 2e 6e 65 74 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE <== Protocol:CHAP(c223) Success Identifier:0x58 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x00 Vendor Specific: 00 00 0c 01 00 00 00 00 IP Address: 0 0 0 0 Primary Domain Name Server: 0 0 0 0 Secondary Domain Name Server: 0 0 0 0 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE <== Protocol:IPCP(8021) ConfRej Identifier:0x00 Vendor Specific: 00 00 0c 01 00 00 00 00 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x01 IP Address: 0 0 0 0 Primary Domain Name Server: 0 0 0 0 Secondary Domain Name Server: 0 0 0 0 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE <== Protocol:IPCP(8021) ConfNak Identifier:0x01 IP Address: 194 75 4 49 Primary Domain Name Server: 212 159 6 10 Secondary Domain Name Server: 212 159 6 9 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x02 IP Address: 194 75 4 49 Primary Domain Name Server: 212 159 6 10 Secondary Domain Name Server: 212 159 6 9 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE <== Protocol:IPCP(8021) ConfAck Identifier:0x02 IP Address: 194 75 4 49 Primary Domain Name Server: 212 159 6 10 Secondary Domain Name Server: 212 159 6 9 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE <== Protocol:IPCP(8021) ConfReq Identifier:0x07 IP Address: 195 166 130 216 ##
16:06:21 16:06:14 Vigor WAN1 PPPoE ==> Protocol:IPCP(8021) ConfAck Identifier:0x07 IP Address: 195 166 130 216 ##
16:06:21 16:06:14 Vigor WAN 1 is up.
16:06:36 16:06:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x02 Magic Number: 0x0 00 00 ##
16:06:36 16:06:28 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x02 Magic Number: 0x48f6 da 15 ##
16:06:37 16:06:29 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x00 Magic Number: 0x48f6 da 15 ##
16:06:37 16:06:29 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x00 Magic Number: 0x0 00 00 ##
16:07:07 16:06:59 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x01 Magic Number: 0x48f6 da 15 ##
16:07:07 16:06:59 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x01 Magic Number: 0x0 00 00 ##
16:07:17 16:07:09 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x03 Magic Number: 0x0 00 00 ##
16:07:17 16:07:09 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x03 Magic Number: 0x48f6 da 15 ##
16:07:34 16:07:26 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x04 Magic Number: 0x0 00 00 ##
16:07:34 16:07:26 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x04 Magic Number: 0x48f6 da 15 ##
16:07:37 16:07:29 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x02 Magic Number: 0x48f6 da 15 ##
16:07:37 16:07:29 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x02 Magic Number: 0x0 00 00 ##
16:07:47 16:07:39 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x05 Magic Number: 0x0 00 00 ##
16:07:47 16:07:39 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x05 Magic Number: 0x48f6 da 15 ##
16:07:53 16:07:45 Vigor statistic: WAN1: Tx 12 Kbps, Rx 132 Kbps (5 min average)
16:07:53 16:07:45 Vigor statistic: Session Usage: 18 (5 min average)
16:07:57 16:07:49 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x06 Magic Number: 0x0 00 00 ##
16:07:57 16:07:49 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x06 Magic Number: 0x48f6 da 15 ##
16:08:07 16:07:59 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x03 Magic Number: 0x48f6 da 15 ##
16:08:07 16:07:59 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x03 Magic Number: 0x0 00 00 ##
16:08:37 16:08:28 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x04 Magic Number: 0x48f6 da 15 ##
16:08:37 16:08:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x04 Magic Number: 0x0 00 00 ##
16:08:50 16:08:42 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x07 Magic Number: 0x0 00 00 ##
16:08:50 16:08:42 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x07 Magic Number: 0x48f6 da 15 ##
16:09:04 16:08:55 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x08 Magic Number: 0x0 00 00 ##
16:09:04 16:08:55 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x08 Magic Number: 0x48f6 da 15 ##
16:09:07 16:08:58 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x05 Magic Number: 0x48f6 da 15 ##
16:09:07 16:08:58 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x05 Magic Number: 0x0 00 00 ##
16:09:16 16:09:08 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x09 Magic Number: 0x0 00 00 ##
16:09:17 16:09:08 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x09 Magic Number: 0x48f6 da 15 ##
16:09:27 16:09:18 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0A Magic Number: 0x0 00 00 ##
16:09:27 16:09:18 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0A Magic Number: 0x48f6 da 15 ##
16:09:37 16:09:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0B Magic Number: 0x0 00 00 ##
16:09:37 16:09:28 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0B Magic Number: 0x48f6 da 15 ##
16:09:37 16:09:28 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x06 Magic Number: 0x48f6 da 15 ##
16:09:37 16:09:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x06 Magic Number: 0x0 00 00 ##
16:09:49 16:09:40 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0C Magic Number: 0x0 00 00 ##
16:09:49 16:09:40 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0C Magic Number: 0x48f6 da 15 ##
16:10:01 16:09:52 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0D Magic Number: 0x0 00 00 ##
16:10:01 16:09:52 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0D Magic Number: 0x48f6 da 15 ##
16:10:07 16:09:57 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x07 Magic Number: 0x48f6 da 15 ##
16:10:07 16:09:57 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x07 Magic Number: 0x0 00 00 ##
16:10:17 16:10:07 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0E Magic Number: 0x0 00 00 ##
16:10:17 16:10:07 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0E Magic Number: 0x48f6 da 15 ##
16:10:34 16:10:25 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0F Magic Number: 0x0 00 00 ##
16:10:34 16:10:25 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x0F Magic Number: 0x48f6 da 15 ##
16:10:37 16:10:27 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x08 Magic Number: 0x48f6 da 15 ##
16:10:37 16:10:27 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x08 Magic Number: 0x0 00 00 ##
16:10:49 16:10:40 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x10 Magic Number: 0x0 00 00 ##
16:10:49 16:10:40 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x10 Magic Number: 0x48f6 da 15 ##
16:10:59 16:10:50 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x11 Magic Number: 0x0 00 00 ##
16:10:59 16:10:50 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x11 Magic Number: 0x48f6 da 15 ##
16:11:07 16:10:57 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x09 Magic Number: 0x48f6 da 15 ##
16:11:07 16:10:57 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x09 Magic Number: 0x0 00 00 ##
16:11:17 16:11:07 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x12 Magic Number: 0x0 00 00 ##
16:11:17 16:11:07 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x12 Magic Number: 0x48f6 da 15 ##
16:11:27 16:11:17 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x13 Magic Number: 0x0 00 00 ##
16:11:27 16:11:17 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x13 Magic Number: 0x48f6 da 15 ##
16:11:37 16:11:27 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0A Magic Number: 0x48f6 da 15 ##
16:11:37 16:11:27 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0A Magic Number: 0x0 00 00 ##
16:11:47 16:11:37 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x14 Magic Number: 0x0 00 00 ##
16:11:47 16:11:37 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x14 Magic Number: 0x48f6 da 15 ##
16:11:57 16:11:47 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x15 Magic Number: 0x0 00 00 ##
16:11:57 16:11:47 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x15 Magic Number: 0x48f6 da 15 ##
16:12:07 16:11:56 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0B Magic Number: 0x48f6 da 15 ##
16:12:07 16:11:56 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0B Magic Number: 0x0 00 00 ##
16:12:17 16:12:06 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x16 Magic Number: 0x0 00 00 ##
16:12:17 16:12:06 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x16 Magic Number: 0x48f6 da 15 ##
16:12:27 16:12:16 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x17 Magic Number: 0x0 00 00 ##
16:12:27 16:12:16 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x17 Magic Number: 0x48f6 da 15 ##
16:12:37 16:12:26 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x18 Magic Number: 0x0 00 00 ##
16:12:37 16:12:26 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x18 Magic Number: 0x48f6 da 15 ##
16:12:37 16:12:26 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0C Magic Number: 0x48f6 da 15 ##
16:12:37 16:12:26 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0C Magic Number: 0x0 00 00 ##
16:12:47 16:12:36 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x19 Magic Number: 0x0 00 00 ##
16:12:47 16:12:36 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x19 Magic Number: 0x48f6 da 15 ##
16:12:56 16:12:45 Vigor statistic: WAN1: Tx 0 Kbps, Rx 0 Kbps (5 min average)
16:12:56 16:12:45 Vigor statistic: Session Usage: 2 (5 min average)
16:12:58 16:12:47 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1A Magic Number: 0x0 00 00 ##
16:12:58 16:12:47 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1A Magic Number: 0x48f6 da 15 ##
16:13:07 16:12:56 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0D Magic Number: 0x48f6 da 15 ##
16:13:07 16:12:56 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0D Magic Number: 0x0 00 00 ##
16:13:17 16:13:06 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1B Magic Number: 0x0 00 00 ##
16:13:17 16:13:06 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1B Magic Number: 0x48f6 da 15 ##
16:13:27 16:13:16 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1C Magic Number: 0x0 00 00 ##
16:13:27 16:13:16 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1C Magic Number: 0x48f6 da 15 ##
16:13:37 16:13:26 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0E Magic Number: 0x48f6 da 15 ##
16:13:37 16:13:26 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0E Magic Number: 0x0 00 00 ##
16:13:47 16:13:36 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1D Magic Number: 0x0 00 00 ##
16:13:47 16:13:36 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1D Magic Number: 0x48f6 da 15 ##
16:14:02 16:13:51 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1E Magic Number: 0x0 00 00 ##
16:14:02 16:13:51 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1E Magic Number: 0x48f6 da 15 ##
16:14:07 16:13:55 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x0F Magic Number: 0x48f6 da 15 ##
16:14:07 16:13:55 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x0F Magic Number: 0x0 00 00 ##
16:14:17 16:14:05 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x1F Magic Number: 0x0 00 00 ##
16:14:17 16:14:05 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x1F Magic Number: 0x48f6 da 15 ##
16:14:27 16:14:15 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x20 Magic Number: 0x0 00 00 ##
16:14:27 16:14:15 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x20 Magic Number: 0x48f6 da 15 ##
16:14:37 16:14:25 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x10 Magic Number: 0x48f6 da 15 ##
16:14:37 16:14:25 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x10 Magic Number: 0x0 00 00 ##
16:14:46 16:14:35 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x21 Magic Number: 0x0 00 00 ##
16:14:46 16:14:35 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x21 Magic Number: 0x48f6 da 15 ##
16:14:56 16:14:45 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x22 Magic Number: 0x0 00 00 ##
16:14:56 16:14:45 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x22 Magic Number: 0x48f6 da 15 ##
16:15:07 16:14:55 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x11 Magic Number: 0x48f6 da 15 ##
16:15:07 16:14:55 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x11 Magic Number: 0x0 00 00 ##
16:15:17 16:15:05 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x23 Magic Number: 0x0 00 00 ##
16:15:17 16:15:05 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x23 Magic Number: 0x48f6 da 15 ##
16:15:27 16:15:15 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoReq Identifier:0x24 Magic Number: 0x0 00 00 ##
16:15:27 16:15:15 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoRep Identifier:0x24 Magic Number: 0x48f6 da 15 ##
16:15:37 16:15:25 Vigor WAN1 PPPoE <== Protocol:LCP(c021) EchoReq Identifier:0x12 Magic Number: 0x48f6 da 15 ##
16:15:37 16:15:25 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) EchoRep Identifier:0x12 Magic Number: 0x0 00 00 ##
16:15:40 16:15:28 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) TermReq Identifier:0x25 ##
16:15:48 16:15:35 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) TermReq Identifier:0x26 ##
16:15:56 16:15:43 Vigor WAN1 PPPoE ==> Protocol:LCP(c021) TermReq Identifier:0x27 ##
16:16:04 16:15:51 Vigor WAN 1 is down.

Syslog – CONNECTION:

16:04:17 16:04:11 Vigor PPP Closed : No Echo Response (PPPoE)
16:04:18 16:04:11 Vigor PPP Closed : No Echo Response (PPPoE)
16:04:19 16:04:11 Vigor PPP Closed : LCP Time-out (PPPoE)
16:04:19 16:04:13 Vigor >>> Dial-up triggered by user : 192.168.1.65 ; proto=UDP, to 212.159.13.49 port=domain
16:04:28 16:04:21 Vigor [QoS] WAN1 IN/OUT speed: 18179/1460 Kbps
16:06:17 16:06:10 Vigor PPP Start (PPPoE)
16:06:21 16:06:14 Vigor CHAP Login OK (PPPoE)
16:06:21 16:06:14 Vigor IPCP Opening (PPPoE); Own IP Address : 194.75.4.49 Peer IP Address : 195.166.130.216; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
16:15:40 16:15:28 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:40 16:15:28 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:41 16:15:29 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:41 16:15:29 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:42 16:15:30 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:42 16:15:30 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:43 16:15:31 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:43 16:15:31 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:44 16:15:32 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:44 16:15:32 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:45 16:15:33 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:45 16:15:33 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:46 16:15:34 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:46 16:15:34 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:47 16:15:35 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:47 16:15:35 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:48 16:15:36 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:48 16:15:36 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:49 16:15:37 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:50 16:15:37 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:50 16:15:38 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:50 16:15:38 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:51 16:15:39 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:52 16:15:39 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:52 16:15:40 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:53 16:15:40 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:53 16:15:41 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:54 16:15:41 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:54 16:15:42 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:55 16:15:42 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:55 16:15:43 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:56 16:15:43 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:56 16:15:44 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:57 16:15:44 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:57 16:15:45 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:58 16:15:45 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:58 16:15:46 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:59 16:15:46 Vigor PPP Closed : No Echo Response (PPPoE)
16:15:59 16:15:47 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:00 16:15:47 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:00 16:15:48 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:01 16:15:48 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:01 16:15:49 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:02 16:15:49 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:02 16:15:50 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:03 16:15:50 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:03 16:15:51 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:04 16:15:51 Vigor PPP Closed : No Echo Response (PPPoE)
16:16:05 16:15:51 Vigor PPP Closed : LCP Time-out (PPPoE)

VDSL Status

VDSL,,,
Link Status,Showtime,,
Firmware Version,1414c3,,
Basic Status,Upstream,Downstream,Unit
VDSL Profile,17a,,
Actual Data Rate,1999,21059,Kb/s
SNR,156,74,0.1dB
Advance Status,Upstream,Downstream,Unit
Actual delay,0,0,ms
Actual INP,1,0,0.1 symbols
Actual INP,1,0,0.1 symbols
15M CV,0,0,counter
1Day CV,40,2,counter
15M FEC,0,0,counter
1Day FEC,2640,363,counter
Total FEC,2640,363,counter
Previous Data Rate,1999,21601,Kbps
Attainable Rate,6562,21059,Kbps
Electrical Length,233,233,0.1 dB
SNR Margin,157,157,"(US0,--) 0.1 dB"
SNR Margin,156,76,"(US1,DS1) 0.1 dB"
SNR Margin,0,71,"(US2,DS2) 0.1 dB"
SNR Margin,0,N/A,"(US3,DS3) 0.1 dB"
SNR Margin,0,N/A,"(US4,DS4) 0.1 dB"
15M Elapsed time,118,118,secs
15M FECS,0,0,counter
15M ES,0,0,counter
15M SES,0,0,counter
15M LOSS,0,0,counter
15M UAS,0,119,counter
1Day Elapsed time,6418,6418,secs
1Day FECS,135,1,counter
1Day ES,3,0,counter
1Day SES,1,176,counter
1Day LOSS,357,0,counter
1Day UAS,921284,6205,counter
Total FECS,135,1,counter
Total ES,3,0,counter
Total SES,1,176,counter
Total LOSS,357,0,counter
Total UAS,921284,6205,counter

Re: Draytek 2850n Plusnet FTTC fibre problem

Mustrum — Fri, 06 May 2016 21:53:42 GMT

Just a quick reply, but your username should follow your member centre usernam@plusdsl.net

Re: Draytek 2850n Plusnet FTTC fibre problem

kitz — Sat, 07 May 2016 07:39:34 GMT

It was chance that I spotted this whilst looking for something else.
I don't want to point any firm blame yet, because I notice you say you have the latest f/w and I dont want to send you down a wrong path. AFAIK last year Draytek said they had no plans to release an updated f/w version for the 2850 series.

Facts noted

You have valid sync.
You are having problems establishing and retaining PPP session.
Connection is fine with PN supplied router.

Would you do me a favour please - Can you follow the instructions on How to lookup your FTTC cabinet and let me know if you are on a Huawei or ECI cabinet.

I also really need your DLM profile. If a Plusnet rep is about can you do a GEA service test please for the EU as I'd like to know if they have retransmission applied?

---
Because Im not always around on these forums, and if anyone wonders where Im heading with this. The router is displaying signs typical to the ECI modem issue 1 problem.
However, Im wanting to identify and rule out is:- If the EU is caught up in the reason why G.INP is being rolled back on the ECI cabs or if its a possible f/w incompatibility with G.INP retransmission on the Huawei cabs.

Re: Draytek 2850n Plusnet FTTC fibre problem

BusterRaid — Sat, 07 May 2016 10:01:11 GMT

Thank you for the replys.

I changed the logon details to anonymise them - the actual login format I used is MyLoginName@plusdsl.net

I've used the suggested sites and checked what the Draytek reports.

The web sites indicate we are connected to cabinet 12.

They indicated it is type ECI.

The Draytek indicates it is type Infineon .

Curiously, this morning the connection on the Draytek has been steady - up to 1hr mins and no down time.

Also, i think that the "Down Speed" as reported by the Draytek seem to be half that of what it reported yesterday - but I could be mistaken - 32 Mb would be great but we have gone from a 2Mb connection, (oop North) to what is now 18Mb, so we still think we have an embarrassment of internet speed richness.

Is there any other diagnostics required - the Draytek can generate some VDSL debug output but it's fairly lengthy.

Below is the output from the web sites & from the Draytek.

From the recommended websites:

BT BROADBAND AVAILABILITY CHECKER

Telephone Number 017xxx on Exchange STAFFORD is served by Cabinet 12

Featured Products	Downstream Line Rate(Mbps)		Upstream Line Rate(Mbps)		Downstream Range(Mbps)	Availability Date
	High	Low	High	Low
FTTC Range A (Clean)	32	22.4	7.3	5.7	--	Available
FTTC Range B (Impacted)	23.3	10	6.6	2.3	--	Available
WBC ADSL 2+	Up to 7		--		5 to 12.5	Available
WBC ADSL 2+ Annex M	Up to 7		Up to 1		5 to 12.5	Available
ADSL Max	Up to 2.5		--		2 to 5.5	Available
WBC Fixed Rate	2		--		--	Available
Fixed Rate	2		--		--	Available
Other Offerings
Fibre Multicast	--		--		--	Available
Copper Multicast	--		--		--	Available

Locality:	Stafford, Staffordshire All Post Codes All 107 Fibre Cabinets
District:	Stafford	County:	Staffordshire
Country:	England	Post Code:	ST16
20CN IPStream:	ADSL
21CN WBC:	ADSL2+	Fibre:	FTTC or FTTP 31st January 2012
BT Exchange:	Stafford	Exchange Code:	WMSPA

Cabinet P12

FTTC Available from 23rd August 2012

Phase 09a 2012-2013

534

ECI

ST16 1DD

Post Code:	ST16 1DD
Locality:	Castledene Drive, Stafford, Staffordshire
District:	Stafford	County:	Staffordshire
		Country:	England
20CN IPStream:	ADSL	Exchange Distance:	1,748m
21CN WBC:	ADSL2+	Fibre Phase:	Phase 09a 2012-2013
BT Exchange:	Stafford	Exchange Code:	WMSPA

From the Draytek:

VDSL Information (VDSL Firmware Version: 1414c3 )

Profile	State	UP Speed	Down Speed	SNR Upstream	SNR Downstream
17a	Showtime	1999 (Kbps)	18367 (Kbps)	N/A (0.1dB)	74 (0.1dB)

Server Information (Infineon )

Re: Draytek 2850n Plusnet FTTC fibre problem

kitz — Sat, 07 May 2016 12:14:22 GMT

>> They indicated it is type ECI.
>> The Draytek indicates it is type Infineon .

Thank you that is what I wanted to know.

Basically there is (was) a problem with the roll-out of G.INP/Retransmission on some lines which is known to have a problem causing difficulties in obtaining PPP and maintaining PPP. As a result Openreach are now rolling back G.INP for ECI cabs.

What we havent so far been able to identify is the exact cause and why only 'some' lines had a problem. Over the past few days Ive had a sneaky but growing suspicion if it may be related to EU equipment. However its hard to monitor as ECI modems and HomeHubs dont provide line stats.. plus those of us who do monitor lines on MDWS all tend to use BCM based modems which appear to have no issues of this type.

this morning the connection on the Draytek has been steady - up to 1hr mins and no down time

Also, i think that the "Down Speed" as reported by the Draytek seem to be half that of what it reported yesterday - but I could be mistaken.

As mentioned, Openreach are rolling back. Most lines are now done, but there are still a few to go.
Upon roll-back, DLM removes g.inp and instead applies Interleaving and Error Correction. The result of this is less speed due to FEC overheads.

Full line stats from the Draytek should be able to tell you if you are interleaved.

PS.
Last I heard, the 2850's had problems with g.inp on the Huawei cabs and last year Draytek said they had no plans to upgrade the firmware to support g.inp

Re: Draytek 2850n Plusnet FTTC fibre problem

BusterRaid — Sun, 08 May 2016 11:18:08 GMT

Thank you for the information!

Not sure how to get the line stats - telnet/ssh-ing to the Draytek offers ADSL info but I cant see any VDSL option.

Update - Connection via Draytek OK for many hours this morning, still running at about 18Mbs - only interruption was yesterday - frantic unplugging due to lightning.

If I can be of any assistance testing the possible G.Inp "issue", i'd be happy to help. As detailed - I have the Draytek and the Plusnet Hub One and am happy to fiddle with the setup & config.

Thanks again for your help!

Re: Draytek 2850n Plusnet FTTC fibre problem

kitz — Sun, 08 May 2016 11:39:47 GMT

I dont have a 2850, but Im guessing one of the adsl info commands should pull out any xDSL info for your line.

For example the CLI command for vdsl stats on my Zyxel is adsl info --stats. I think 'ADSL' is just a historic command that works for both adsl or vdsl on some modems.

I'm also guessing that DLM will have removed g.inp/retransmission from your line, which is why things are now more stable. Most lines should have now been rolled back.

Re: Draytek 2850n Plusnet FTTC fibre problem

slime-uk — Tue, 20 Jun 2017 10:27:11 GMT

Ever get this resolved? I've tried everything and the Draytek 2860 I have is driving me nuts with constant WAN drops (3 or 4 a day sometimes). Tried multiple firmwares, with Draytek UK helping too, BT recommended, vector 2 etc.

Just had:

DrayTek: PPP Closed : Remote Terminating (PPPoA)
<166>Jun 20 11:15:20 DrayTek: WAN1 PPPoE ==> Protocol:LCP(c021) TermReq Identifier:0x02 ##
<166>Jun 20 11:15:20 DrayTek: WAN 1 is down.

Any ideas?

Thanks,

Si.

Re: Draytek 2850n Plusnet FTTC fibre problem

corringham — Tue, 20 Jun 2017 12:47:04 GMT

I'm having similar problems with a Vigor 2860n+ but with an ADSL Max connection. Currently I get a few drops a day, with the occasional episode where it will drop multiple times within an hour - sometimes it drops before it fully reconnects. It is unusable at those times, which is a problem as a home-worker.

My line stats are text book (max supported sync rate, low CRC/ES, high SNR) so I don't believe it is line quality per se. I also have the latest recommended firmware. It has been suggested that it is due to high upstream utilization, but QoS to limit this has no obvious effect on the problem.

I'm puzzled that this is a problem for both FTTC and ADSL - or alternatively there are two separate but very similar problems with Vigor kit. The only difference is my log usually gives TermReq Identifier:0x04

Plusnet support have advised me to buy a new router, but as I need the VPN support provided by the (not too old) Vigor I'm reluctant to do that.

As an aside, I recently discovered that the 2860 supports a WAN via a WiFi connection - so if you have a decent 4G (or 3G) signal you can connect to a MiFi or phone hotspot (or any local WiFi signal available) and set up a failover or load-balancing to mitigate the VDSL/ADSL problems.

Re: Draytek 2850n Plusnet FTTC fibre problem

markhawkin — Tue, 20 Jun 2017 18:56:36 GMT

Hello @corringham

I've a Draytek 2860ac

Firmware Version : 3.8.4.3_BT
Build Date/Time : Jan 17 2017 19:54:29

This will run for a month or more without intervention (typically it gets reset if I need to change something that requires a reboot).

I've unlimited fibre extra.

What I do recommend from other experience is use of the master socket and fitting one of the VDSL filter plates.

This may be a contributing factor to the whole setup being stable.

Re: Draytek 2850n Plusnet FTTC fibre problem

slime-uk — Tue, 20 Jun 2017 19:39:33 GMT

Thanks.

I do have quite high upload traffic I guess so that could be similar. I have pretty poor downstream SNR though - currently sitting at 3db but I see it go to 0db at times. It starts at 9db and drops throughout the day, sometimes recovering to 6 or 7. I really do think my drops are when it gets to zero.

I used to use the 4g backup but disconnected it thinking it may be causing noise. No change though.

ATU-R Information

Type:

VDSL2

Hardware:

Annex A

Firmware:

05-07-06-0D-01-07

Power Mngt Mode:

DSL_G997_PMS_L0

Line State:

SHOWTIME

Running Mode:

17A

Vendor ID:

00000000 00000000

ATU-C Information

Vendor ID:

b5004244 434da48c [BDCM]

Line Statistics

	Downstream		Upstream
Actual Rate	66997	Kbps	19999	Kbps
Attainable Rate	54950	Kbps	28348	Kbps
Path Mode	Fast		Fast
Interleave Depth	1		1
Actual PSD	5. 7	dB	12. 9	dB


	Near End		Far End
Trellis	ON		ON
Bitswap	ON		ON
ReTx	1		1
SNR Margin	3	dB	10	dB
Attenuation	13	dB	15	dB
CRC	0		23
FECS	0	s	17972	s
ES	0	s	7	s
SES	0	s	3	s
LOSS	0	s	3	s
UAS	27	s	1010	s
HEC Errors	0		0
RS Corrections	0		0
LOS Failure	4		4
LOF Failure	0		0
LPR Failure	0		4
NCD Failure	0		0
LCD Failure	0		0
NFEC	32		32
RFEC	16		16
LYSMB	16		16

Re: Draytek 2850n Plusnet FTTC fibre problem

slime-uk — Tue, 20 Jun 2017 19:41:36 GMT

BT checked the line again last week and noticed nothing. He changed from an NTE Mk3 to a Mk4. My Draytek is at the master. Even replaced the RG11 cable for a shorter one from the BT socket to the Draytek - no change.

Re: Draytek 2850n Plusnet FTTC fibre problem

markhawkin — Tue, 20 Jun 2017 20:50:18 GMT

What I have is on Amazon as:

"GENUINE BT Openreach - MK3 2014 Version - vDSL Interstitial Faceplate, ADSL Filter & I-Plate / iplate"

You need the correct version for your NTE but this (which seems to separate all the house wiring from the VDSL signals) seems to work well.

Re: Draytek 2850n Plusnet FTTC fibre problem

corringham — Tue, 20 Jun 2017 21:37:54 GMT

Hi @markhawkin,

Yes I'd recommend a filter plate too - I use an ADSLNation plate, but on a rather old master socket. I don't think my issue is line stability as such - my SNR is 11 down and 16 up, and I get few CRC errors (1 or 2 an hour, which is more than I used to get but still pretty low).

There is something causing the connection to drop which doesn't appear to be line errors. It is quite possible my issue may be different to the VDSL issues.

Re: Draytek 2850n Plusnet FTTC fibre problem

BusterRaid — Wed, 21 Jun 2017 06:10:12 GMT

Hi.

OP here.

My problem eventually went away - it seemed to decrease in frequency over about 3 days and then, for all intents and purposes, disappeared.

I changed nothing – RJ11, faceplate, etc. No electronic devices were added to removed from the house wiring, no phones added.

Therefore, I currently don’t think it was the router causing the issue.

I’m pretty miffed that Plusnet/openreach are lacking the tools to identify this problem. I am considering migrating to another, more IT focused provider as this problem wasn’t “fixed” it just “went away”.

My details (current):

Model Name : Vigor2850n

Firmware Version : 3.6.8.6_RC2

Build Date/Time : Jan 13 2017 10:49:26

Time server:ntp.cis.strath.ac.uk – 3 hour update (london, daylight saving enabled).

MTU 1492

WAN 1

Enable:Yes

Physical Mode:	VDSL
DSL Mode: VDSL Only
VLAN Tag insertion (ADSL):Disable


Tag value:	(0~4095)
Priority:	(0~7)
VLAN Tag insertion (VDSL):Disable

Tag value:101	(0~4095)
Priority:0	(0~7)
Active Mode:Always ON

Load Balance: (OFF)

WAN 1 Status				>> Drop PPPoE
Enable	Line	Name	Mode	Up Time
Yes	VDSL		PPPoE	1132:06:27
IP	GW IP	TX Packets	TX Rate(Bps)	RX Packets	RX Rate(Bps)
		93050779	8480	173065307	230198

VDSL Information (VDSL Firmware Version: 1414c3 )

Profile	State	UP Speed	Down Speed	SNR Upstream	SNR Downstream
17a	Showtime	1999 (Kbps)	17991 (Kbps)	141 (0.1dB)	51 (0.1dB)

Server Information (Infineon )

System Status:

VDSL
Link Status	Showtime
Firmware Version	1414c3
Basic Status	Upstream	Downstream	Unit
VDSL Profile	17a
Actual Data Rate	1999	17991	Kb/s
SNR	135	51	0.1dB
Advance Status	Upstream	Downstream	Unit
Actual delay	0	8	ms
Actual INP	1	30	0.1 symbols
Actual INP	1	30	0.1 symbols
15M CV	0	39	counter
1Day CV	2	167	counter
15M FEC	0	2140684	counter
1Day FEC	6	4831680	counter
Total FEC	9722	16014998	counter
Previous Data Rate	0	0	Kbps
Attainable Rate	5709	18451	Kbps
Electrical Length	233	233	0.1 dB
SNR Margin	125	125	(US0,--) 0.1 dB
SNR Margin	136	55	(US1,DS1) 0.1 dB
SNR Margin	0	46	(US2,DS2) 0.1 dB
SNR Margin	0	N/A	(US3,DS3) 0.1 dB
SNR Margin	0	N/A	(US4,DS4) 0.1 dB
15M Elapsed time	489	489	secs
15M FECS	0	490	counter
15M ES	0	20	counter
15M SES	0	0	counter
15M LOSS	0	0	counter
15M UAS	0	0	counter
1Day Elapsed time	61689	61689	secs
1Day FECS	2	61690	counter
1Day ES	2	121	counter
1Day SES	0	0	counter
1Day LOSS	0	0	counter
1Day UAS	0	0	counter
Total FECS	1504	4208743	counter
Total ES	596	5418	counter
Total SES	1	36	counter
Total LOSS	929	0	counter
Total UAS	121819	70	counter

Re: Draytek 2850n Plusnet FTTC fibre problem

Chris — Wed, 21 Jun 2017 10:59:56 GMT

If there's anything Plusnet specific in this thread we can help with, please let us know. -Chris

Re: Draytek 2850n Plusnet FTTC fibre problem

guitaristanime — Wed, 21 Jun 2017 11:39:03 GMT

This is all weirdly timely,

I've just picked up a Vigor 2860n and an ap902 for home which I'll be installing tonight. Weird that this subject is current now but anyway...

I've got a VDSL faceplate supplied by OpenReach when they came to resolve a line issue previous. I get around 70/20 with the supplied PN router. I'll let you know how I get on and if there's any disconnecting at all.

Re: Draytek 2850n Plusnet FTTC fibre problem

guitaristanime — Wed, 21 Jun 2017 18:31:05 GMT

Just installed my 2860n, only had to change VLAN tag and I'm all done. Synced at 75/20.

Re: Draytek 2850n Plusnet FTTC fibre problem

markhawkin — Wed, 21 Jun 2017 20:32:05 GMT

@BusterRaid

I have to say I sympathise with you but I'm not sure that your "more IT focused provider" really exists.

At a premium price "Andrews and Arnold" offer various business oriented packages but everyone (except Virgin) in some way uses Openreach.

Someone (probably in Openreach) found this problem and fixed it (and I don't have the system knowledge to speculate where it was) but most likely either configuration or a hardware fault.

One other point to consider is Drayteks statement on the 2850 and BT VDSL.

http://www.draytek.co.uk/information/our-technology/bt-sin-498

Earlier DrayTek Products

DrayTek's very earliest VDSL2 products (The Vigor 2850 and 2750, sold until 2013) are not upgradable to SIN498 compliance as the chipsets do not have the capability to support some of the new requirements. For those users, if you wish to upgrade to a compliant model, we have provided an upgrade scheme here.

There was a fairly generous upgrade scheme (now closed) but you could still see if Draytek would honour it.

Re: Draytek 2850n Plusnet FTTC fibre problem

slime-uk — Mon, 03 Jul 2017 15:18:47 GMT

How is the 2860n performing? What's your WAN uptime if you don't mind me asking?