Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2

Author Topic: FTTC dropouts  (Read 1345 times)

ads

  • Member
  • **
  • Posts: 23
FTTC dropouts
« on: September 09, 2021, 06:11:25 PM »

My BT FTTC has been dropping out this week, couple of times on Monday, again on Tuesday, and now twice so far today. Always between 5-7PM, rest of the time it seems fine.

Code: [Select]
18:06:34, 09 Sep.

:HTTP UserAdmin login from 192.168.1.124 successfully

18:06:25, 09 Sep.

:HTTP UserBasic login from 192.168.1.124 successfully

18:05:55, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

18:05:51, 09 Sep.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

18:05:50, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:50, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:05:49, 09 Sep.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

18:05:49, 09 Sep.

ppp1:TR69 receiving InformResponse message

18:05:49, 09 Sep.

ppp1:TR69 event found : 4 VALUE CHANGE

18:05:48, 09 Sep.

ppp1:TR69 sending Inform message

18:05:48, 09 Sep.

ppp1:TR69 event found : 4 VALUE CHANGE

18:05:47, 09 Sep.

ppp1:TR69 sending Inform message

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated address = 2a00:23c4:6e82:4601:8aa6:c6ff:fe24:dad9 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1:TR69 creating new session with ACS

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

18:05:39, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated address = 2a00:23c4:6e82:4601:8aa6:c6ff:fe24:dad9 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:38, 09 Sep.

ppp1:WAN DHCPv6 Mode : Statefull

18:05:38, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:38, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:05:38, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:38, 09 Sep.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

18:05:37, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:36, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:36, 09 Sep.

:WAN: SENSING AUTO VDSL

18:05:36, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:36, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:36, 09 Sep.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.10.141]

18:05:35, 09 Sep.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.10.141]

18:05:35, 09 Sep.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

18:05:35, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:35, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:35, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1:PPP: PPP INFO

18:05:35, 09 Sep.

ppp:PPP: IPCP_NAK

18:05:35, 09 Sep.

ppp:PPP: CHAP_SUCCESS

18:05:35, 09 Sep.

ppp:PPP: CHAP_RESPONSE

18:05:35, 09 Sep.

ppp:PPP: LCP_GOOD_ACK

18:05:35, 09 Sep.

ppp:PPP: LCP_REQUEST

18:05:34, 09 Sep.

:PPPoE error: timeout

18:05:26, 09 Sep.

:PPPoE error: timeout

18:05:21, 09 Sep.

:PPPoE error: timeout

18:05:16, 09 Sep.

ptm0.101:VLAN VLAN_DATA connected

18:05:16, 09 Sep.

:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]

18:05:16, 09 Sep.

:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]

18:05:16, 09 Sep.

dsl:VDSL link Up: Down Rate=39706Kbps, Up Rate=12829Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB

18:04:54, 09 Sep.

:VLAN VLAN_DATA disconnected

18:04:53, 09 Sep.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

18:04:53, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:52, 09 Sep.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

18:04:52, 09 Sep.

ppp1:Request for a new authenticated connection

18:04:52, 09 Sep.

ppp1:TR69 ConnectionRequest: processing request from ACS

18:04:52, 09 Sep.

ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.10.141] is deleted

18:04:52, 09 Sep.

ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.10.141] is deleted

18:04:52, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:04:51, 09 Sep.

BR_LAN: Revoked prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:04:51, 09 Sep.

ppp1: Revoked prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:04:51, 09 Sep.

ppp1: Revoked prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:04:50, 09 Sep.

dsl:VDSL Link Down: duration was 176582 seconds

17:06:05, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

17:03:42, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

17:03:42, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

Log I grabbed from the last dropout, anything obvious there? BT website test says they found no issues.

[Moderator edited to change [pre][/pre] tags to [code][/code] tags.]
« Last Edit: September 09, 2021, 08:50:17 PM by burakkucat »
Logged

ads

  • Member
  • **
  • Posts: 23
Re: FTTC dropouts
« Reply #1 on: September 09, 2021, 06:14:36 PM »

Code: [Select]
Noise margin:
6.1 dB / 6.2 dB

Line attenuation:
37 dB

Signal attenuation:
23.1 dB / 37 dB

VPI / VCI:
0/38

Modulation:
G_993_2_ANNEX_B

Latency type:
Fast Path

if that helps ^


Oh and for some reason a tab in Firefox opens; http://www.msftconnecttest.com/00000111500/gui/?item=redirect

Never seen that before

[Moderator edited: As preceding post.]
« Last Edit: September 09, 2021, 08:52:43 PM by burakkucat »
Logged

Alex Atkin UK

  • Kitizen
  • ****
  • Posts: 3166
    • Thinkbroadband Quality Monitors
Re: FTTC dropouts
« Reply #2 on: September 10, 2021, 01:39:25 AM »

There's not really enough to go on if your router isn't even showing the number of errors.
Logged
INTAKE (ECI) Home Hub 5A (OpenWRT) on Zen, Hauwei B353-232 on Libera 4G, Hauwei CPE Pro 2 H122-373 on Three 5G Router: pfSense (i5-7200U) WiFi: Zyxel NWA210AX + Ubiquiti nanoHD (OpenWRT)
My Broadband History & Ping Quality Monitors

ads

  • Member
  • **
  • Posts: 23
Re: FTTC dropouts
« Reply #3 on: September 10, 2021, 02:31:41 PM »

That's all the info the stupid BT Hub 6A tells me when the event log is set to all, is there a way to gather more info?
Logged

mofa2020

  • Reg Member
  • ***
  • Posts: 275
Re: FTTC dropouts
« Reply #4 on: September 10, 2021, 02:52:16 PM »

are VPI / VCI used on FTTC lines? never seen it before when VDSL is the line modulation.
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 34407
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: FTTC dropouts
« Reply #5 on: September 10, 2021, 04:32:20 PM »

are VPI / VCI used on FTTC lines?

No, never.

Quote
. . . never seen it before when VDSL is the line modulation.

It is just the result of a decision by the writer of the system code (or firmware) to display that irrelevant information.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

meritez

  • Reg Member
  • ***
  • Posts: 829
Re: FTTC dropouts
« Reply #6 on: September 10, 2021, 04:35:40 PM »

That's all the info the stupid BT Hub 6A tells me when the event log is set to all, is there a way to gather more info?

Anything else running at that time, boiler, microwave, etc?
Logged

ads

  • Member
  • **
  • Posts: 23
Re: FTTC dropouts
« Reply #7 on: September 11, 2021, 02:02:14 PM »

Nothing new, or obvious

It did just drop out a few minutes ago, the kettle was on, but I don't think that lines up with the other dropouts
Logged

ads

  • Member
  • **
  • Posts: 23
Re: FTTC dropouts
« Reply #8 on: October 13, 2021, 03:18:40 AM »

Things went back to normal for a month, then 6+ dropouts today

Is it normal for the BT Home Hub Event Log to display the wrong date every so often after dropouts?

Logged

Alex Atkin UK

  • Kitizen
  • ****
  • Posts: 3166
    • Thinkbroadband Quality Monitors
Re: FTTC dropouts
« Reply #9 on: October 13, 2021, 04:02:13 AM »

Darn, that's unhelpful as we can see PPP drop but does it drop sync?  (I'd assume so)
Logged
INTAKE (ECI) Home Hub 5A (OpenWRT) on Zen, Hauwei B353-232 on Libera 4G, Hauwei CPE Pro 2 H122-373 on Three 5G Router: pfSense (i5-7200U) WiFi: Zyxel NWA210AX + Ubiquiti nanoHD (OpenWRT)
My Broadband History & Ping Quality Monitors

gt94sss2

  • Kitizen
  • ****
  • Posts: 1111
Re: FTTC dropouts
« Reply #10 on: October 13, 2021, 05:30:42 AM »

Things went back to normal for a month, then 6+ dropouts today

Is it normal for the BT Home Hub Event Log to display the wrong date every so often after dropouts?

Your modem is rebooting - is not just a dropout.

Have you tried a hard reset?
Logged

ads

  • Member
  • **
  • Posts: 23
Re: FTTC dropouts
« Reply #11 on: October 13, 2021, 01:33:48 PM »

Yep, left it unplugged for 15 minutes. It continued to drop. It's not the whole hub rebooting though, LAN continues to work (at least it seemed to while I was watching local media).

I ran another BT test thing and finally their automated system says they've detected an issue not at my property and they're going to fix it. Haven't spoken to a human so I don't really know anything else, I guess I just sit on it and hope for the best for now.
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 10294
  • Retd s/w dev; A&A; 3x7km lines; Firebrick; IPv6
Re: FTTC dropouts
« Reply #12 on: October 13, 2021, 01:58:07 PM »

Is the modem itself ill? Need a replacement unit / or new PSU ?
Logged

Alex Atkin UK

  • Kitizen
  • ****
  • Posts: 3166
    • Thinkbroadband Quality Monitors
Re: FTTC dropouts
« Reply #13 on: October 13, 2021, 02:29:43 PM »

Your modem is rebooting - is not just a dropout.

Have you tried a hard reset?

Good point, I thought it was a user triggered reboot as I was looking at the time thinking "oh theres a gap", missing the obvious that the date was reset due to the reboot.
Logged
INTAKE (ECI) Home Hub 5A (OpenWRT) on Zen, Hauwei B353-232 on Libera 4G, Hauwei CPE Pro 2 H122-373 on Three 5G Router: pfSense (i5-7200U) WiFi: Zyxel NWA210AX + Ubiquiti nanoHD (OpenWRT)
My Broadband History & Ping Quality Monitors

gt94sss2

  • Kitizen
  • ****
  • Posts: 1111
Re: FTTC dropouts
« Reply #14 on: October 13, 2021, 05:35:03 PM »

Yep, left it unplugged for 15 minutes. It continued to drop. It's not the whole hub rebooting though, LAN continues to work (at least it seemed to while I was watching local media).

Sometimes, especially after the HH upgrades it's firmware, it needs a hard reset to take.

This is not the same as switching it off/on but pressing the reset button at the back (or in the GUI) to reset it to it's default settings.

You can backup your config before doing this and reapply it once reset
Logged
Pages: [1] 2