cancel
Showing results for 
Search instead for 
Did you mean: 

New customer bb drops every morning-event log attached

FIXED
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

New customer bb drops every morning-event log attached

Hi I;ve been with PlusNet for 8 days now. Everything works fine apart from that bb drops every morning and I have to log back in via the router on my PC. Occasionally it will drop out daytime too. Below is the last trace page before it dropped this morning. Please help me figure this out. Smiley

06:05:47, 18 Dec.
(128819.220000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
06:05:47, 18 Dec.
(128819.220000) CHAP authentication failed
06:05:47, 18 Dec.
(128819.190000) CHAP Receive Challenge
06:05:47, 18 Dec.
(128819.190000) Starting CHAP authentication with peer
06:05:47, 18 Dec.
(128819.190000) PPP LCP Receive Configuration ACK
06:05:47, 18 Dec.
(128819.180000) PPP LCP Send Configuration Request
06:05:47, 18 Dec.
(128819.180000) PPP LCP Receive Configuration Reject
06:05:47, 18 Dec.
(128819.170000) PPP LCP Send Configuration ACK
06:05:47, 18 Dec.
(128819.170000) PPP LCP Receive Configuration Request
06:05:47, 18 Dec.
(128819.170000) PPP LCP Send Configuration Request
06:05:35, 18 Dec.
(128807.390000) Admin login successful by 192.168.1.79 on HTTP
06:05:23, 18 Dec.
(128795.080000) New GUI session from IP 192.168.1.79
06:05:19, 18 Dec.
(128791.430000) Lease for IP 192.168.1.79 renewed by host Magpie (MAC 14:4f:8a:24:2b:c4). Lease duration: 30240 min
06:05:19, 18 Dec.
(128791.430000) Device connected: Hostname: Magpie IP: 192.168.1.79 MAC: 14:4f:8a:24:2b:c4 Lease time: 30240 min. Link rate: 866.6 Mbps
06:05:19, 18 Dec.
(128791.350000) Lease requested
06:05:19, 18 Dec.
ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client associated
06:05:17, 18 Dec.
(128789.100000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
06:05:17, 18 Dec.
(128789.100000) CHAP authentication failed
06:05:17, 18 Dec.
(128789.070000) CHAP Receive Challenge
06:05:17, 18 Dec.
(128789.060000) Starting CHAP authentication with peer
06:05:17, 18 Dec.
(128789.060000) PPP LCP Receive Configuration ACK
06:05:17, 18 Dec.
(128789.050000) PPP LCP Send Configuration Request
06:05:17, 18 Dec.
(128789.050000) PPP LCP Receive Configuration Reject
06:05:17, 18 Dec.
(128789.050000) PPP LCP Send Configuration ACK
06:05:17, 18 Dec.
(128789.050000) PPP LCP Receive Configuration Request
06:05:17, 18 Dec.
(128789.040000) PPP LCP Send Configuration Request
06:05:17, 18 Dec.
ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client disassociated
06:04:47, 18 Dec.
(128758.970000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
06:04:47, 18 Dec.
(128758.970000) CHAP authentication failed
06:04:47, 18 Dec.
(128758.920000) CHAP Receive Challenge
06:04:47, 18 Dec.
(128758.920000) Starting CHAP authentication with peer
06:04:47, 18 Dec.
(128758.920000) PPP LCP Receive Configuration ACK
06:04:47, 18 Dec.
(128758.910000) PPP LCP Send Configuration Request
06:04:47, 18 Dec.
(128758.910000) PPP LCP Receive Configuration Reject
06:04:47, 18 Dec.
(128758.910000) PPP LCP Send Configuration ACK
06:04:47, 18 Dec.
(128758.900000) PPP LCP Receive Configuration Request
06:04:47, 18 Dec.
(128758.900000) PPP LCP Send Configuration Request
06:04:47, 18 Dec.
(128758.840000) CWMP: session closed due to error: Could not resolve host
06:04:47, 18 Dec.
(128758.820000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
06:04:47, 18 Dec.
(128758.810000) CWMP: Session start now. Event code(s): '2 PERIODIC,6 CONNECTION REQUEST,4 VALUE CHANGE'
06:04:17, 18 Dec.
(128728.530000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
06:04:17, 18 Dec.
(128728.530000) CHAP authentication failed
06:04:17, 18 Dec.
(128728.490000) CHAP Receive Challenge
06:04:17, 18 Dec.
(128728.480000) CWMP: session closed due to error: Could not resolve host
06:04:17, 18 Dec.
(128728.480000) Starting CHAP authentication with peer
06:04:17, 18 Dec.
(128728.480000) PPP LCP Receive Configuration ACK
06:04:17, 18 Dec.
(128728.480000) PPP LCP Send Configuration Request
06:04:17, 18 Dec.
(128728.470000) PPP LCP Receive Configuration Reject
06:04:17, 18 Dec.
(128728.470000) PPP LCP Send Configuration ACK
06:04:17, 18 Dec.
(128728.470000) PPP LCP Receive Configuration Request
06:04:17, 18 Dec.
(128728.470000) PPP LCP Send Configuration Request
06:04:15, 18 Dec.
(128727.230000) PPPoE is down after 1430 minutes uptime [In Progress...]
06:04:13, 18 Dec.
(128724.660000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
06:04:13, 18 Dec.
(128724.650000) CWMP: Session start now. Event code(s): '2 PERIODIC,6 CONNECTION REQUEST,4 VALUE CHANGE'
06:04:11, 18 Dec.
(128722.800000) PPP LCP Send Termination Request [User request]
06:04:10, 18 Dec.
(128722.390000) CWMP: session completed successfully
06:04:10, 18 Dec.
(128722.340000) CWMP: Initializing transaction for event code 6 CONNECTION REQUEST
06:04:10, 18 Dec.
(128722.180000) CWMP: Set Parameter by TR069 failure 9003: Invalid arguments
06:04:10, 18 Dec.
(128721.890000) CWMP: HTTP authentication success from https://dbtpnhdm.bt.mo
06:04:07, 18 Dec.
(128719.440000) CWMP: Initializing transaction for event code 2 PERIODIC
06:04:07, 18 Dec.
(128719.430000) CWMP: Initializing transaction for event code 2 PERIODIC
06:04:07, 18 Dec.
(128719.430000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
06:04:07, 18 Dec.
(128719.420000) CWMP: Session start now. Event code(s): '2 PERIODIC,4 VALUE CHANGE'
06:04:07, 18 Dec.
(128719.080000) CWMP: Initializing transaction for event code 2 PERIODIC
06:01:00, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 192.172.226.146-​>209.93.243.216 on ppp3)
05:59:59, 18 Dec.
OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 209.93.243.216-​>17.248.144.207 on ppp3)
05:59:57, 18 Dec.
BLOCKED 1 more packets (because of ICMP replay)
05:59:56, 18 Dec.
OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 209.93.243.216-​>17.248.144.207 on ppp3)
05:59:28, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 65.123.202.139-​>209.93.243.216 on ppp3)
05:56:09, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 71.6.202.205-​>209.93.243.216 on ppp3)
05:54:45, 18 Dec.
(128156.470000) Lease for IP 192.168.1.69 renewed by host Rohans-​phone (MAC c0:b6:58:49:c6:95). Lease duration: 30240 min
05:54:45, 18 Dec.
(128156.470000) Device connected: Hostname: Rohans-​phone IP: 192.168.1.69 MAC: c0:b6:58:49:c6:95 Lease time: 30240 min. Link rate: 74.8 Mbps
05:54:44, 18 Dec.
(128156.390000) Lease requested
05:54:44, 18 Dec.
ath00: STA c0:b6:58:49:c6:95 IEEE 802.11: Client associated
05:52:44, 18 Dec.
(128036.440000) Device disconnected: Hostname: Rohans-​phone IP: 192.168.1.69 MAC: c0:b6:58:49:c6:95
05:52:44, 18 Dec.
ath00: STA c0:b6:58:49:c6:95 IEEE 802.11: Client disassociated
05:52:39, 18 Dec.
ath00: STA c0:b6:58:49:c6:95 IEEE 802.11: Client associated
05:51:24, 18 Dec.
(127956.440000) Device disconnected: Hostname: Ardans-​iPhone IP: 192.168.1.76 MAC: d4:dc:cd:a6:99:1e
05:51:24, 18 Dec.
(127956.440000) Device disconnected: Hostname: MarieLoesiPhone IP: 192.168.1.70 MAC: d8:1c:79:ac:86:db
05:51:23, 18 Dec.
ath00: STA d4:dc:cd:a6:99:1e IEEE 802.11: Client disassociated
05:51:23, 18 Dec.
ath00: STA d8:1c:79:ac:86:db IEEE 802.11: Client disassociated
05:51:23, 18 Dec.
ath00: STA d4:dc:cd:a6:99:1e IEEE 802.11: WiFi registration failed
05:51:23, 18 Dec.
ath00: STA d8:1c:79:ac:86:db IEEE 802.11: WiFi registration failed
05:51:18, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 129.82.138.44-​>209.93.243.216 on ppp3)
05:46:56, 18 Dec.
(127688.270000) Host Ardans-​iPhone (MAC d4:dc:cd:a6:99:1e) using IP 192.168.1.76 detected on interface ath10, port -​1
05:46:51, 18 Dec.
ath10: STA d4:dc:cd:a6:99:1e IEEE 802.11: Client associated
05:46:37, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 195.251.255.69-​>209.93.243.216 on ppp3)
05:45:07, 18 Dec.
IN: BLOCK [16] Remote administration (TCP [218.92.1.141]:9090-​>[209.93.243.216]:22 on ppp3)
05:44:16, 18 Dec.
(127527.920000) Lease for IP 192.168.1.79 renewed by host Magpie (MAC 14:4f:8a:24:2b:c4). Lease duration: 30240 min
05:44:16, 18 Dec.
(127527.920000) Device connected: Hostname: Magpie IP: 192.168.1.79 MAC: 14:4f:8a:24:2b:c4 Lease time: 30240 min. Link rate: 6.0 Mbps
05:44:16, 18 Dec.
(127527.830000) Lease requested
05:44:15, 18 Dec.
ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client associated
05:42:16, 18 Dec.
(127408.210000) Host MarieLoesiPhone (MAC d8:1c:79:ac:86:db) using IP 192.168.1.70 detected on interface ath10, port -​1
05:42:09, 18 Dec.
ath10: STA d8:1c:79:ac:86:db IEEE 802.11: Client associated
05:38:03, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 195.169.125.251-​>209.93.243.216 on ppp3)
05:30:45, 18 Dec.
IN: BLOCK [16] Remote administration (TCP [185.143.221.42]:51140-​>[209.93.243.216]:8080 on ppp3)
05:27:44, 18 Dec.
IN: BLOCK [16] Remote administration (ICMP type 8 code 0 206.117.25.90-​>209.93.243.216 on ppp3)
05:22:14, 18 Dec.
(126206.430000) Device disconnected: Hostname: Unknown-​18-​2a-​7b-​51-​32-​e3-​2 IP: 192.168.1.67 MAC: 18:2a:7b:51:32:e3
05:22:13, 18 Dec.
ath00: STA 18:2a:7b:51:32:e3 IEEE 802.11: Client disassociated
05:21:23, 18 Dec.
ath00: STA c0:b6:58:49:c6:95 IEEE 802.11: WiFi registration failed

 

20 REPLIES 20
dvorak
Moderator
Moderator
Posts: 29,473
Thanks: 6,623
Fixes: 1,482
Registered: ‎11-01-2008

Re: New customer bb drops every morning-event log attached


Moderators Note


This topic has been released from the Spam Filter.

 


 

Customer / Moderator
If it helped click the thumb
If it fixed it click 'This fixed my problem'
adamwalker
Plusnet Help Team
Plusnet Help Team
Posts: 16,871
Thanks: 882
Fixes: 221
Registered: ‎27-04-2007

Re: New customer bb drops every morning-event log attached

Hi Tyranade, 

 

Sorry to see the connection has been dropping. I've just been testing the line and we're not seeing any obvious issues. 

 

Please try following the checks here next if that's still a problem: https://goo.gl/tu2WWu beyond that it would be a good idea to report a fault over at http://faults.plus.net

 

Adam

If this post resolved your issue please click the 'This fixed my problem' button
 Adam Walker
 Plusnet Help Team
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

I tried to report an error as you suggested but it doesn't work. Here is the message I get: 

Broadband Troubleshooter - Error

There's been a problem

We're sorry, but you can't use the Broadband Troubleshooter to report a fault on your service. Please contact our Support Team for help.

SammyM
Plusnet Help Team
Plusnet Help Team
Posts: 1,901
Thanks: 411
Fixes: 93
Registered: ‎22-01-2018

Re: New customer bb drops every morning-event log attached

Hello @Tyranade,

 

I am sorry to hear that yoyu are unable to report the issue to us, and we would be happy to raise the issue to our supplier. However we do need to rule out internal wiring as the cause.

 

Please can you plug your equipment in to the test socket without any extension cabling. How to locate the test socket can be found here.

 

Once in there please monitor for 24 hours and get back to us if the issue persists.

 

 

 

 

 

 

If this post resolved your issue please click the 'This fixed my problem' button
 Sammy M - Sheffield Team
 Plusnet Help Team
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

Hi it’s attached to the master socket, it’s always been. I’ve attached a photo of the socket
Jubby
All Star
Posts: 626
Thanks: 111
Fixes: 31
Registered: ‎06-08-2018

Re: New customer bb drops every morning-event log attached

Hi @Tyranade,

Thank you for providing the image of how your equipment is connected.

It appears you have a micro-filter connected with a telephone splitter. To connect to the test socket, take our the two screws either side of the telephone socket and remove the faceplate. Once removed in the bottom right corner, connect only the micro-filter with the DSL cable from the router and the telephone cable (RJ-11.)

Once complete, monitor the service and let us know if the issue persists.

Thank you.

If this post resolved your issue please click the 'This fixed my problem' button
 Lewis G
 Infrastructure Operations Professional
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

The micro filter and the splitter connects the alarm system. Are you saying that the alarm system needs be kept disconnected for 24hrs?
Jubby
All Star
Posts: 626
Thanks: 111
Fixes: 31
Registered: ‎06-08-2018

Re: New customer bb drops every morning-event log attached

Hi again @Tyranade,

Thank you for getting back in touch.

After further diagnostics, I have confirmed that the service has dropped once since the connection was authenticated with our server. Please see the connection logs below.
 



Before progressing to connecting to your test socket, I would recommend monitoring the service in case these drops are due to a stabilization period or a retrain with it only been connected since 06:07AM. If you notice the connection drop again, I'm afraid disconnecting any devices that are not the telephone / router will be required until the issue is raised with our suppliers.

Let us know if the connection drops again so we can pick it up as soon as possible for you.

Thank you.

If this post resolved your issue please click the 'This fixed my problem' button
 Lewis G
 Infrastructure Operations Professional
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

Hi

It dropped as usual this morning. (See event log below) I will have to get some help to disconnect the alarm system. I will post here when I've connected to the test socket.

 

Time and date Message
07:58:59, 19 Dec. (222008.700000) Admin login successful by 192.168.1.79 on HTTP
07:58:54, 19 Dec. (222004.250000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:58:54, 19 Dec. (222004.250000) CHAP authentication failed
07:58:54, 19 Dec. (222004.220000) CHAP Receive Challenge
07:58:54, 19 Dec. (222004.220000) Starting CHAP authentication with peer
07:58:54, 19 Dec. (222004.210000) PPP LCP Receive Configuration ACK
07:58:54, 19 Dec. (222004.210000) PPP LCP Send Configuration Request
07:58:54, 19 Dec. (222004.200000) PPP LCP Receive Configuration Reject
07:58:54, 19 Dec. (222004.200000) PPP LCP Send Configuration ACK
07:58:54, 19 Dec. (222004.200000) PPP LCP Receive Configuration Request
07:58:54, 19 Dec. (222004.200000) PPP LCP Send Configuration Request
07:58:48, 19 Dec. (221997.790000) New GUI session from IP 192.168.1.79
07:58:42, 19 Dec. (221991.900000) Lease for IP 192.168.1.79 renewed by host Magpie (MAC 14:4f:8a:24:2b:c4). Lease duration: 30240 min
07:58:42, 19 Dec. (221991.900000) Device connected: Hostname: Magpie IP: 192.168.1.79 MAC: 14:4f:8a:24:2b:c4 Lease time: 30240 min. Link rate: 866.6 Mbps
07:58:42, 19 Dec. (221991.810000) Lease requested
07:58:42, 19 Dec. ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client associated
07:58:41, 19 Dec. (221991.460000) Device disconnected: Hostname: Magpie IP: 192.168.1.79 MAC: 14:4f:8a:24:2b:c4
07:58:40, 19 Dec. ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client disassociated
07:58:24, 19 Dec. (221974.110000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:58:24, 19 Dec. (221974.110000) CHAP authentication failed
07:58:24, 19 Dec. (221974.080000) CHAP Receive Challenge
07:58:24, 19 Dec. (221974.080000) Starting CHAP authentication with peer
07:58:24, 19 Dec. (221974.080000) PPP LCP Receive Configuration ACK
07:58:24, 19 Dec. (221974.070000) PPP LCP Send Configuration Request
07:58:24, 19 Dec. (221974.070000) PPP LCP Receive Configuration Reject
07:58:24, 19 Dec. (221974.070000) PPP LCP Send Configuration ACK
07:58:24, 19 Dec. (221974.060000) PPP LCP Receive Configuration Request
07:58:24, 19 Dec. (221974.060000) PPP LCP Send Configuration Request
07:58:22, 19 Dec. (221972.280000) Lease for IP 192.168.1.79 renewed by host Magpie (MAC 14:4f:8a:24:2b:c4). Lease duration: 30240 min
07:58:22, 19 Dec. (221972.280000) Device connected: Hostname: Magpie IP: 192.168.1.79 MAC: 14:4f:8a:24:2b:c4 Lease time: 30240 min. Link rate: 175.5 Mbps
07:58:22, 19 Dec. (221972.190000) Lease requested
07:58:21, 19 Dec. ath10: STA 14:4f:8a:24:2b:c4 IEEE 802.11: Client associated
07:57:54, 19 Dec. (221943.960000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:57:54, 19 Dec. (221943.960000) CHAP authentication failed
07:57:54, 19 Dec. (221943.930000) CHAP Receive Challenge
07:57:54, 19 Dec. (221943.930000) Starting CHAP authentication with peer
07:57:54, 19 Dec. (221943.920000) PPP LCP Receive Configuration ACK
07:57:54, 19 Dec. (221943.920000) PPP LCP Send Configuration Request
07:57:54, 19 Dec. (221943.920000) PPP LCP Receive Configuration Reject
07:57:54, 19 Dec. (221943.920000) PPP LCP Send Configuration ACK
07:57:54, 19 Dec. (221943.910000) PPP LCP Receive Configuration Request
07:57:54, 19 Dec. (221943.910000) PPP LCP Send Configuration Request
07:57:24, 19 Dec. (221913.840000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:57:24, 19 Dec. (221913.840000) CHAP authentication failed
07:57:24, 19 Dec. (221913.790000) CHAP Receive Challenge
07:57:24, 19 Dec. (221913.790000) Starting CHAP authentication with peer
07:57:24, 19 Dec. (221913.790000) PPP LCP Receive Configuration ACK
07:57:24, 19 Dec. (221913.780000) PPP LCP Send Configuration Request
07:57:24, 19 Dec. (221913.780000) PPP LCP Receive Configuration Reject
07:57:24, 19 Dec. (221913.780000) PPP LCP Send Configuration ACK
07:57:24, 19 Dec. (221913.770000) PPP LCP Receive Configuration Request
07:57:24, 19 Dec. (221913.770000) PPP LCP Send Configuration Request
07:56:54, 19 Dec. (221883.690000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:56:54, 19 Dec. (221883.690000) CHAP authentication failed
07:56:53, 19 Dec. (221883.640000) CHAP Receive Challenge
07:56:53, 19 Dec. (221883.640000) Starting CHAP authentication with peer
07:56:53, 19 Dec. (221883.640000) PPP LCP Receive Configuration ACK
07:56:53, 19 Dec. (221883.630000) PPP LCP Send Configuration Request
07:56:53, 19 Dec. (221883.630000) PPP LCP Receive Configuration Reject
07:56:53, 19 Dec. (221883.630000) PPP LCP Send Configuration ACK
07:56:53, 19 Dec. (221883.620000) PPP LCP Receive Configuration Request
07:56:53, 19 Dec. (221883.620000) PPP LCP Send Configuration Request
07:56:23, 19 Dec. (221853.550000) PPP LCP Send Termination Request [Failed to authenticate ourselves to peer]
07:56:23, 19 Dec. (221853.550000) CHAP authentication failed
OskarPapa
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 1,325
Fixes: 65
Registered: ‎09-10-2018

Re: New customer bb drops every morning-event log attached

Thanks for those logs @Tyranade.

 

Please do let us know when you're in the test socket and we'll begin to run further diagnostics alongside our suppliers.

Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

Connected to the test socket 16:55. The speed is so slow I can't even do a speed test. This is the log from now. looks really strange. The internet is basically unusable atm.

( 541.440000) Admin login successful by 192.168.1.79 on HTTP
17:01:20, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62636-​>[1.1.1.1]:443 on ppp3)
17:00:59, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62581-​>[216.58.206.34]:80 on ppp3)
17:00:48, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62536-​>[216.58.206.35]:443 on ppp3)
17:00:44, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62517-​>[216.58.206.34]:80 on ppp3)
17:00:40, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62497-​>[163.172.71.37]:38460 on ppp3)
17:00:38, 20 Dec. IN: BLOCK [16] Remote administration (TCP [189.47.198.92]:37770-​>[146.200.172.202]:8080 on ppp3)
17:00:36, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62319-​>[68.151.225.246]:27507 on ppp3)
17:00:33, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62479-​>[163.172.71.37]:38460 on ppp3)
17:00:30, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
17:00:29, 20 Dec. ( 489.490000) New GUI session from IP 192.168.1.79
17:00:29, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62437-​>[152.195.39.114]:80 on ppp3)
17:00:23, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62149-​>[163.172.71.37]:38460 on ppp3)
17:00:19, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62421-​>[73.205.21.20]:47925 on ppp3)
17:00:17, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
17:00:16, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62456-​>[109.189.240.139]:8999 on ppp3)
17:00:12, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61912-​>[104.82.198.30]:443 on ppp3)
17:00:11, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62443-​>[109.189.240.139]:8999 on ppp3)
17:00:09, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62383-​>[216.58.204.2]:80 on ppp3)
17:00:09, 20 Dec. BLOCKED 9 more packets (because of First packet is Invalid)
17:00:08, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62373-​>[23.251.20.22]:25035 on ppp3)
17:00:06, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62415-​>[109.189.240.139]:8999 on ppp3)
17:00:04, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62078-​>[73.205.21.20]:47925 on ppp3)
17:00:02, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
17:00:01, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62402-​>[109.189.240.139]:8999 on ppp3)
16:59:59, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62351-​>[92.4.215.156]:43781 on ppp3)
16:59:56, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:59:55, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62332-​>[216.58.204.2]:80 on ppp3)
16:59:49, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62317-​>[23.251.20.22]:25035 on ppp3)
16:59:47, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62321-​>[92.4.215.156]:43781 on ppp3)
16:59:43, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:59:42, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62342-​>[51.15.4.13]:1337 on ppp3)
16:59:40, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62291-​>[92.4.215.156]:43781 on ppp3)
16:59:34, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:59:33, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62102-​>[23.251.20.22]:25035 on ppp3)
16:59:29, 20 Dec. BLOCKED 3 more packets (because of First packet is Invalid)
16:59:28, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62289-​>[1.1.1.1]:443 on ppp3)
16:59:27, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62278-​>[92.4.215.156]:43781 on ppp3)
16:59:17, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:59:16, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62239-​>[185.33.223.80]:80 on ppp3)
16:59:13, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62223-​>[104.237.191.1]:443 on ppp3)
16:59:10, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62217-​>[151.101.18.219]:443 on ppp3)
16:59:05, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62143-​>[109.144.113.198]:443 on ppp3)
16:59:03, 20 Dec. BLOCKED 3 more packets (because of First packet is Invalid)
16:59:02, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62209-​>[185.33.223.80]:80 on ppp3)
16:58:49, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62023-​>[52.17.150.45]:80 on ppp3)
16:58:48, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:58:47, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61894-​>[104.103.249.91]:443 on ppp3)
16:58:46, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62181-​>[151.101.16.175]:443 on ppp3)
16:58:46, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:58:45, 20 Dec. BLOCKED 3 more packets (because of First packet is Invalid)
16:58:44, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61978-​>[54.154.81.193]:80 on ppp3)
16:58:43, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61917-​>[157.240.1.23]:443 on ppp3)
16:58:42, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61965-​>[54.229.201.41]:443 on ppp3)
16:58:40, 20 Dec. IN: BLOCK [16] Remote administration (TCP [187.74.177.237]:53497-​>[146.200.172.202]:8080 on ppp3)
16:58:38, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61916-​>[54.229.201.41]:80 on ppp3)
16:58:32, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62142-​>[151.101.16.175]:80 on ppp3)
16:58:29, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62136-​>[104.82.214.243]:80 on ppp3)
16:58:29, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62134-​>[104.82.198.207]:80 on ppp3)
16:58:20, 20 Dec. BLOCKED 2 more packets (because of First packet is Invalid)
16:58:19, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62119-​>[104.19.196.151]:443 on ppp3)
16:58:18, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:58:17, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62050-​>[104.244.37.20]:443 on ppp3)
16:58:06, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62062-​>[104.244.37.20]:443 on ppp3)
16:58:04, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62066-​>[205.185.216.10]:443 on ppp3)
16:58:01, 20 Dec. BLOCKED 2 more packets (because of First packet is Invalid)
16:58:00, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:62028-​>[52.17.150.45]:80 on ppp3)
16:58:00, 20 Dec. BLOCKED 2 more packets (because of First packet is Invalid)
16:57:59, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61949-​>[185.33.223.80]:80 on ppp3)
16:57:50, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61843-​>[109.144.113.198]:443 on ppp3)
16:57:48, 20 Dec. BLOCKED 2 more packets (because of First packet is Invalid)
16:57:47, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61915-​>[151.101.17.194]:80 on ppp3)
16:57:46, 20 Dec. BLOCKED 1 more packets (because of First packet is Invalid)
16:57:45, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61906-​>[216.58.204.2]:443 on ppp3)
16:57:44, 20 Dec. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.79]:61884-​>[151.101.66.219]:80 on ppp3)
16:57:22, 20 Dec. ( 302.710000) Host MarieLoesiPhone (MAC d8:1c:79:ac:86:db) using IP 192.168.1.70 detected on interface ath00, port -​1
16:57:15, 20 Dec. ath00: STA d8:1c:79:ac:86:db IEEE 802.11: Client associated
16:57:15, 20 Dec. ath00: STA d8:1c:79:ac:86:db IEEE 802.11: Client disassociated
16:57:10, 20 Dec. OUT: BLOCK [15] Default policy (First packet in connection is not a SYN packet: TCP [192.168.1.70]:52191-​>[54.235.93.206]:443 on ppp3)
16:57:09, 20 Dec. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.70]:52192-​>[34.251.118.222]:443 on ppp3)
16:57:09, 20 Dec. IN: BLOCK [15] Default policy (UDP [89.65.139.50]:6881-​>[146.200.172.202]:15000 on ppp3)
16:57:05, 20 Dec. IN: BLOCK [15] Default policy (TCP [40.127.142.76]:443-​>[146.200.172.202]:61744 on ppp3)
16:56:58, 20 Dec. BLOCKED 1 more packets (because of Default policy)
16:56:57, 20 Dec. IN: BLOCK [15] Default policy (ICMP type 3 code 1 211.46.116.185-​>146.200.172.202 on ppp3)
16:56:56, 20 Dec. IN: BLOCK [15] Default policy (TCP [5.188.206.252]:53005-​>[146.200.172.202]:2000 on ppp3)
16:56:54, 20 Dec. IN: BLOCK [15] Default policy (TCP [94.102.49.190]:29011-​>[146.200.172.202]:7777 on ppp3)
16:56:52, 20 Dec. IN: BLOCK [15] Default policy (TCP [78.128.112.94]:51159-​>[146.200.172.202]:63000 on ppp3)
16:56:46, 20 Dec. ( 267.030000) Host MarieLoesiPhone (MAC d8:1c:79:ac:86:db) using IP 192.168.1.70 detected on interface ath10, port -​1
16:56:45, 20 Dec. BLOCKED 2 more packets (because of Default policy)
16:56:45, 20 Dec. IN: BLOCK [15] Default policy (TCP [17.253.35.203]:443-​>[146.200.172.202]:50284 on ppp3)
16:56:42, 20 Dec. IN: BLOCK [15] Default policy (ICMP type 3 code 1 211.46.116.185-​>146.200.172.202 on ppp3)
16:56:40, 20 Dec. ( 260.890000) Lease for IP 192.168.1.71 renewed by host Elinas-​Ipad (MAC 40:83:1d:3f:5e:6a). Lease duration: 30240 min
16:56:40, 20 Dec. ( 260.890000) Device connected: Hostname: Elinas-​Ipad IP: 192.168.1.71 MAC: 40:83:1d:3f:5e:6a Lease time: 30240 min. Link rate: 11.0 Mbps
16:56:40, 20 Dec. ( 260.810000) Lease requested
16:56:40, 20 Dec. ath00: STA 40:83:1d:3f:5e:6a IEEE 802.11: Client associated
16:56:39, 20 Dec. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.235.189.114]:443-​>[146.200.172.202]:52190 on ppp3)
16:56:38, 20 Dec. IN: BLOCK [15] Default policy (TCP [17.57.10.6]:443-​>[146.200.172.202]:52178 on ppp3)
16:56:38, 20 Dec. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.57.10.7]:443-​>[146.200.172.202]:52177 on ppp3)
16:56:38, 20 Dec. ath10: STA d8:1c:79:ac:86:db IEEE 802.11: Client associated
16:56:36, 20 Dec. ( 256.740000) Lease for IP 192.168.1.70 renewed by host MarieLoesiPhone (MAC d8:1c:79:ac:86:db). Lease duration: 30240 min
EmilyD
Plusnet Help Team
Plusnet Help Team
Posts: 2,032
Thanks: 357
Fixes: 117
Registered: ‎26-03-2018

Re: New customer bb drops every morning-event log attached

Hi @Tyranade,

 

Thank you for connecting directly to the test socket and for sending those logs over. I'm sorry to see that connecting to the test socket hasn't resolved this problem.

 

Your connection logs definitely seem to indicate that something is out of place:

 

However, testing your line isn't picking up the cause of this problem:

 

Please can you report the issue here and let us know when you've completed it - we'll then be able to progress things further for you.

If this post resolved your issue please click the 'This fixed my problem' button
 Emily D
 Plusnet Help Team
Tyranade
Dabbler
Posts: 13
Registered: ‎18-12-2018

Re: New customer bb drops every morning-event log attached

Hi have done as you asked and raised a ticket. Do I have to keep the router on the test socket?
EmilyD
Plusnet Help Team
Plusnet Help Team
Posts: 2,032
Thanks: 357
Fixes: 117
Registered: ‎26-03-2018

Re: New customer bb drops every morning-event log attached

Hi @Tyranade,

 

Thank you for raising the ticket, you can put your router back into its normal set up now. When you've reported the fault you've advised that you are also getting no dial tone on your landline. Please can you confirm whether or not this is the case, as this will affect the next steps of the investigation.

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