cancel
Showing results for 
Search instead for 
Did you mean: 

TD-W9980 setup

Highlighted
graemev
Hooked
Posts: 8
Registered: a week ago

TD-W9980 setup

Following complaints from my family (the internet is slow!!) I took a look at my TD-W9980  ... odd stuff, ended up sending remote syslog to my NAS (otherwise it's always 1-jan-1970 at restart time :-) ) . It seems to be dropping connection and reconnecting quite regularly ... now I had about 6 months of BT digging up my drive, so I think the physical line quality is now fine. I do suspect I might have been running too much stuff on the W9980 such that it's just too busy (100% cpu)   so I've stopped doing some unnecessary stuff.

 

But it did occur to me it's years since I installed the TD-W9980  , plusnet might have changed their settings ? If the "save format" of the tp-link was e.g XML I'd ask if somebody could dump their settings (elide the password etc) and post it?  Failing that have there been any changes that might affect the modem?

 

 

(I've added blank lines, where there is a block of time , but not deleted any lines, I've elided CHAP traffic & MAC addresses)  [ the showtime messages appear to show a "nesting" which I don't understand ]

 

<13>1 2018-06-12T19:05:42.288797+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC1>
<13>1 2018-06-12T19:05:42.288797+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.109
<13>1 2018-06-12T19:57:42.165320+01:00 DHCPD - - - DHCPD: Recv DISCOVER from <MAC1>
<13>1 2018-06-12T19:57:42.165320+01:00 DHCPD - - - DHCPD: Send OFFER with ip 192.168.1.109
<13>1 2018-06-12T19:57:43.189503+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC1>
<13>1 2018-06-12T19:57:43.689697+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.109

<13>1 2018-06-12T20:15:22.452769+01:00 DSL - - - DSL: xDSL Leave Showtime!!
<13>1 2018-06-12T20:15:22.671168+01:00 DSL - - - DSL: xDSL Leave Showtime!!
<11>1 2018-06-12T20:15:23.613823+01:00 PPP - - - PPP: ppp0 User request
<11>1 2018-06-12T20:15:23.614893+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-12T20:15:23.615632+01:00 PPP - - - PPP: ppp0 LCP down
<14>1 2018-06-12T20:15:23.616498+01:00 PPP - - - PPP: ppp0 sent [LCP TermReq id=0x3 "User request"]

<14>1 2018-06-12T20:15:26.607307+01:00 PPP - - - PPP: ppp0 sent [LCP TermReq id=0x4 "User request"]
<13>1 2018-06-12T20:15:26.794873+01:00 DSL - - - DSL: xDSL Ready!!
<11>1 2018-06-12T20:15:29.999404+01:00 PPP - - - PPP: ppp0
<13>1 2018-06-12T20:15:30.793437+01:00 DSL - - - DSL: xDSL Handshake!!
<13>1 2018-06-12T20:15:33.794808+01:00 DSL - - - DSL: xDSL Training!!
<13>1 2018-06-12T20:15:54.863876+01:00 DSL - - - DSL: xDSL Enter Showtime!!
<14>1 2018-06-12T20:15:58.706667+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000e7e)]
<14>1 2018-06-12T20:16:03.450765+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000e7e)]
<14>1 2018-06-12T20:16:13.460864+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000e7e)]

<11>1 2018-06-12T20:16:33.693050+01:00 PPP - - - PPP: ppp0 Timeout waiting for PADO packets
<11>1 2018-06-12T20:16:33.694372+01:00 PPP - - - PPP: ppp0
<14>1 2018-06-12T20:16:52.307812+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000f03)]
<14>1 2018-06-12T20:16:57.047960+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000f03)]
<14>1 2018-06-12T20:17:07.051395+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000f03)]

<11>1 2018-06-12T20:17:27.252937+01:00 PPP - - - PPP: ppp0 Timeout waiting for PADO packets
<11>1 2018-06-12T20:17:27.252937+01:00 PPP - - - PPP: ppp0

<14>1 2018-06-12T20:17:47.098884+01:00 PPP - - - PPP: ppp0 sent [PADI Host-Uniq(0x00000f8Cool]
<14>1 2018-06-12T20:17:47.101143+01:00 PPP - - - PPP: ppp0 sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x4ed3577f>]
<14>1 2018-06-12T20:17:47.124718+01:00 PPP - - - PPP: ppp0 rcvd [LCP ConfReq id=0x11 <mru 1492> <auth chap MD5> <magic 0x6470f0cf>]
<14>1 2018-06-12T20:17:47.125679+01:00 PPP - - - PPP: ppp0 sent [LCP ConfAck id=0x11 <mru 1492> <auth chap MD5> <magic 0x6470f0cf>]
<14>1 2018-06-12T20:17:47.126678+01:00 PPP - - - PPP: ppp0 rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x4ed3577f>]
<14>1 2018-06-12T20:17:47.127614+01:00 PPP - - - PPP: ppp0 sent [LCP EchoReq id=0x0 magic=0x4ed3577f]
<14>1 2018-06-12T20:17:47.131651+01:00 PPP - - - PPP: ppp0 rcvd [CHAP <elided> ]
<14>1 2018-06-12T20:17:47.132326+01:00 PPP - - - PPP: ppp0 sent [CHAP <elided> ]
<14>1 2018-06-12T20:17:47.133359+01:00 PPP - - - PPP: ppp0 rcvd [LCP EchoRep id=0x0 magic=0x6470f0cf]
<14>1 2018-06-12T20:17:47.209575+01:00 PPP - - - PPP: ppp0 rcvd [LCP ConfReq id=0x56 <auth chap MD5> <magic 0x71e5af21>]
<11>1 2018-06-12T20:17:47.210211+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-12T20:17:47.211258+01:00 PPP - - - PPP: ppp0 LCP down
<14>1 2018-06-12T20:17:47.211697+01:00 PPP - - - PPP: ppp0 sent [LCP ConfReq id=0x2 <mru 1492> <magic 0x83a2773b>]
<14>1 2018-06-12T20:17:47.212356+01:00 PPP - - - PPP: ppp0 sent [LCP ConfAck id=0x56 <auth chap MD5> <magic 0x71e5af21>]
<14>1 2018-06-12T20:17:47.219597+01:00 PPP - - - PPP: ppp0 rcvd [LCP ConfAck id=0x2 <mru 1492> <magic 0x83a2773b>]
<14>1 2018-06-12T20:17:47.220224+01:00 PPP - - - PPP: ppp0 sent [LCP EchoReq id=0x0 magic=0x83a2773b]
<14>1 2018-06-12T20:17:47.220868+01:00 PPP - - - PPP: ppp0 rcvd [CHAP <elided> ]
<14>1 2018-06-12T20:17:47.221636+01:00 PPP - - - PPP: ppp0 sent [CHAP <elided> ]
<14>1 2018-06-12T20:17:47.228345+01:00 PPP - - - PPP: ppp0 rcvd [LCP EchoRep id=0x0 magic=0x71e5af21]
<14>1 2018-06-12T20:17:47.349772+01:00 PPP - - - PPP: ppp0 rcvd [CHAP Success id=0x92 ""]
<14>1 2018-06-12T20:17:47.350531+01:00 PPP - - - PPP: ppp0 sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
<14>1 2018-06-12T20:17:47.359689+01:00 PPP - - - PPP: ppp0 rcvd [IPCP ConfNak id=0x1 <addr 84.92.34.227> <ms-dns1 212.159.6.9> <ms-dns2 212.159.6.10>]
<14>1 2018-06-12T20:17:47.360377+01:00 PPP - - - PPP: ppp0 sent [IPCP ConfReq id=0x2 <addr 84.92.34.227> <ms-dns1 212.159.6.9> <ms-dns2 212.159.6.10>]
<14>1 2018-06-12T20:17:47.439835+01:00 PPP - - - PPP: ppp0 rcvd [IPCP ConfReq id=0x40 <addr 195.166.130.249>]
<14>1 2018-06-12T20:17:47.440508+01:00 PPP - - - PPP: ppp0 sent [IPCP ConfAck id=0x40 <addr 195.166.130.249>]
<14>1 2018-06-12T20:17:48.155477+01:00 PPP - - - PPP: ppp0 rcvd [IPCP ConfAck id=0x2 <addr 84.92.34.227> <ms-dns1 212.159.6.9> <ms-dns2 212.159.6.10>]

<13>1 2018-06-12T20:20:29.790095+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC2>
<13>1 2018-06-12T20:20:29.790790+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.113

<13>1 2018-06-12T20:21:18.888541+01:00 DHCPD - - - DHCPD: Recv DISCOVER from <MAC3>
<13>1 2018-06-12T20:21:18.889205+01:00 DHCPD - - - DHCPD: Send OFFER with ip 192.168.1.101
<13>1 2018-06-12T20:21:18.903792+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC3>
<13>1 2018-06-12T20:21:19.406215+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.101
<13>1 2018-06-12T20:53:45.265424+01:00 DHCPD - - - DHCPD: Recv DISCOVER from <MAC3>
<13>1 2018-06-12T20:53:45.265424+01:00 DHCPD - - - DHCPD: Send OFFER with ip 192.168.1.101
<13>1 2018-06-12T20:53:45.265671+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC3>
<13>1 2018-06-12T20:53:45.761006+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.101

<13>1 2018-06-12T21:17:11.578222+01:00 DSL - - - DSL: xDSL Ready!!
<13>1 2018-06-12T21:17:13.764251+01:00 DSL - - - DSL: xDSL Handshake!!
<13>1 2018-06-12T21:17:13.886281+01:00 DHCPD - - - DHCPD: Recv DISCOVER from <MAC4>
<13>1 2018-06-12T21:17:13.886943+01:00 DHCPD - - - DHCPD: Send OFFER with ip 192.168.1.100
<13>1 2018-06-12T21:17:13.888997+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC4>
<13>1 2018-06-12T21:17:14.390187+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.100
<13>1 2018-06-12T21:17:16.765031+01:00 DSL - - - DSL: xDSL Training!!
<13>1 2018-06-12T21:17:17.420598+01:00 DHCPD - - - DHCPD: Recv DISCOVER from <MAC3>
<13>1 2018-06-12T21:17:17.421225+01:00 DHCPD - - - DHCPD: Send OFFER with ip 192.168.1.101
<13>1 2018-06-12T21:17:17.459278+01:00 DHCPD - - - DHCPD: Recv REQUEST from <MAC3>
<13>1 2018-06-12T21:17:17.960130+01:00 DHCPD - - - DHCPD: Send ACK to 192.168.1.101

<13>1 2018-06-12T21:17:38.792319+01:00 DSL - - - DSL: xDSL Enter Showtime!!

7 REPLIES
bill888
Seasoned Pro
Posts: 866
Thanks: 122
Fixes: 24
Registered: 18-10-2008

Re: TD-W9980 setup

fwiw, as it is not clear whether the disconnections are caused by a line/cabling fault or with the TPlink router, can I suggest you temporarily substitute the TPlink router with another one (eg. original Plusnet router), and see if the disconnects return?

You may also wish to connect the router directly into the Engineer's test socket within the master socket as another test.

TPlink did release new firmware from mid 2015 to support G.INP on FTTC connections for the TD-W9980.  Otherwise, I'm not aware of any other Openreach or Plusnet changes that would require changes to modem router settings.

graemev
Hooked
Posts: 8
Registered: a week ago

Re: TD-W9980 setup

I have

Firmware Version:0.6.0 1.13 v0021.0 Build 160125 Rel.52064n

Hardware Version:TD-W9980 v1 00000001

 

I'd recently upgraded it , but it looks like it was a nop (already on that version)

 

Fair point about the swapping hardware, but I want to give my "mod" a chance (disabled a number of services which would have used packet inspection, thus CPU) . Switching back to the "two box" solution removes a lot of my diagnostics and is about a days work in terms of re-jigging the hallway ( even with Cat5 throughout the house :-) ) so I'll only try that as a last resort ... e.g if it now stays up for a week and I switch back to 2 box model, how long do I wait before deciding it's better . If it dropped out every hour or so it would be a no-brainer (swap the hardware)

 

Using the test socket is a no-go I'm afraid , we do actually use the phone line and it looks like I'd need to take it out of service for several days to prove anything.

Plusnet Help Team
Plusnet Help Team
Posts: 138
Thanks: 58
Fixes: 11
Registered: 26-03-2018

Re: TD-W9980 setup

Hi @graemev 

 

Reading this, it sounds as though you have an SSFP socket which auto splits your service? Two sockets on your faceplate rather than just the one? 

 

You can still have your phone line running whilst in the test socket - just bang a Microfilter (we provided on in the box) in first and that'll split the service between your dsl connection and landline connection.

 

Sorry if i have completely misread this situation. 

 

Thanks 

 

Alisdair 

 

 

If this post resolved your issue please click the 'This fixed my problem' button
 Alisdair C
 Plusnet Help Team
graemev
Hooked
Posts: 8
Registered: a week ago

Re: TD-W9980 setup

I could add a microfilter, but then that's not exactly direct :-)

I point this out because I've wasted a lot of time on various folks setup but putting a faulty micro-filter in-line . I have seen a number of microfilters fail

Plusnet Help Team
Plusnet Help Team
Posts: 7,201
Thanks: 2,052
Fixes: 359
Registered: 21-04-2017

Re: TD-W9980 setup

Whilst I'm not disagreeing with you that microfilters can develop a fault like any hardware, by trying the test socket with a microfilter would rule out the faceplate and the wiring behind it.

If this post resolved your issue please click the 'This fixed my problem' button
 Anoush Mortazavi
 Plusnet Help Team
graemev
Hooked
Posts: 8
Registered: a week ago

Re: TD-W9980 setup

OK, I've reduced the syslog settings so I only see "warnings" and above, last night I got this , little activity in the house at this time I believe.

 

<11>1 2018-06-14T21:44:14.956827+01:00 PPP - - - PPP: ppp0 User request
<11>1 2018-06-14T21:44:14.956827+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-14T21:44:14.970317+01:00 PPP - - - PPP: ppp0 LCP down
<11>1 2018-06-14T21:44:21.302978+01:00 PPP - - - PPP: ppp0
<11>1 2018-06-14T21:45:20.957879+01:00 PPP - - - PPP: ppp0 Timeout waiting for PADO packets
<11>1 2018-06-14T21:45:20.971114+01:00 PPP - - - PPP: ppp0
<11>1 2018-06-14T21:45:55.700999+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-14T21:45:55.702122+01:00 PPP - - - PPP: ppp0 LCP down


<11>1 2018-06-14T21:54:52.919989+01:00 PPP - - - PPP: ppp0 User request
<11>1 2018-06-14T21:54:52.945825+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-14T21:54:52.946451+01:00 PPP - - - PPP: ppp0 LCP down
<11>1 2018-06-14T21:54:59.185648+01:00 PPP - - - PPP: ppp0 User request
<11>1 2018-06-14T21:54:59.186771+01:00 PPP - - - PPP: ppp0
<11>1 2018-06-14T21:55:20.254373+01:00 PPP - - - PPP: ppp0 LCP down
<12>1 2018-06-14T21:55:20.255479+01:00 PPP - - - PPP: ppp0 LCP down

 

Looks like 2 bouts about 10 mins apart. So my plan of attack will be:

 

1: Leave existing setup "mostly untouched" for several days , so I can estimate MTBF

2: Remove BOTH faceplates , which will disable house phones (wired on back of inner plate) but leave emergency phone (not mains power) working for 999 use (plugs in front), install an inline micro-filter from test socket  ... wait 2 X MTBF and see stats

 

3: Replace tp-link with two boxes, this will loose all diagnostics, so I won't be able to see the failure any more, wait 2 X MTBF and phone plusnet to see if they have seen disconnects from their end.

 

Plusnet Help Team
Plusnet Help Team
Posts: 7,201
Thanks: 2,052
Fixes: 359
Registered: 21-04-2017

Re: TD-W9980 setup

Thanks for the update. Keep us posted and feel free to let us know over here if you want us to check up on the disconnections.

If this post resolved your issue please click the 'This fixed my problem' button
 Anoush Mortazavi
 Plusnet Help Team