cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Distinguished Sage
Distinguished Sage
93 Views
Message 11 of 15

Re: At wits end with infinity drop outs


@adrianhand wrote:

Thank you both, I will conduct my own testing as discussed and report back.

Will definitely have a look at the TP-Link options, I imagined being on the hook for more than £40 so if it turned out to be the router, that would be a real blessing.


For many people, its a cheap option to prove a fault, and to keep as a spare if their home hub fails. Some prefer to use it anyway, owing to all its extra features.

-----------------------------------------------------------------------------------

Communityhelp (Private website) Lots of additional information and help.
You will need to be connected to your home BT Broadband connection to view it, or any links to it that I post on this forum.

0 Ratings
adrianhand
Beginner
61 Views
Message 12 of 15

Re: At wits end with infinity drop outs

Okay fellas, nothing noteworthy on the quiet line test, it was quiet for as long as I maintained my patience.
As fate would have it I have encountered a period of relative stability - right now I am on nearly 1 days uptime.
Here are the oddities, though
 
1) connection cycled yesterday just after midnight - but this time the system uptime reset as well as the network uptime - I was not up to witness the event. But the per-device upload totals (which are supposed to reset when the device resets) did not go back to zero....
 
2) the reset and re-sync of the connection if thats what it was shows as ":A device reset was performed (GUI/Button)" - which it definitely was not - here is the relevant chunk:
00:00:35, 01 Jan. :The Modem has successfully powered up
00:00:35, 01 Jan. :WDG Laststatus:: # Current boot was caused by Soft Reset (SAAF)
00:00:28, 01 Jan. :The Modem underwent a warm reset
00:00:24, 01 Jan. :WAN: ethernet as LAN
00:05:16, 08 Dec. dsl:VDSL Link Down: duration was 78483 seconds
00:05:16, 08 Dec. :VLAN VLAN_DATA disconnected
00:05:15, 08 Dec. ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
00:05:15, 08 Dec. ppp1:The DYN ROUTE [81.139.56.100/32 gw ] is deleted
00:05:15, 08 Dec. ppp1:The DYN ROUTE [81.139.57.100/32 gw ] is deleted
00:05:13, 08 Dec. ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
00:05:13, 08 Dec. BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
00:05:13, 08 Dec. BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
00:05:11, 08 Dec. :A device reset was performed (GUI/Button)
3) not all of my re-syncs look like this though. Here is the following one from approx 2am:
02:57:23, 08 Dec. :Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
02:57:22, 08 Dec. :VLAN VLAN_DATA disconnected
02:57:22, 08 Dec. :Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
02:57:22, 08 Dec. BR_LAN:The LAN DHCPv6 Server is active
02:57:22, 08 Dec. BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
02:57:21, 08 Dec. ppp1:The DYN ROUTE [81.139.56.100/32 gw ] is deleted
02:57:21, 08 Dec. ppp1:The DYN ROUTE [81.139.57.100/32 gw ] is deleted
02:57:20, 08 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
02:57:20, 08 Dec. BR_LAN:The LAN DHCPv6 Server is active
02:57:20, 08 Dec. BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
02:57:19, 08 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
02:57:19, 08 Dec. BR_LAN:The LAN DHCPv6 Server is active
02:57:19, 08 Dec. ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
02:57:19, 08 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
02:57:19, 08 Dec. BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
02:57:19, 08 Dec. BR_LAN: Revoked prefix = 2a00:23c5:2a06:d000::/64 (valid time = 2026291200 / preferred time = 2026291200)
02:57:19, 08 Dec. ppp1: Revoked prefix = 2a00:23c5:2a06:d001::/64 (valid time = 2026291200 / preferred time = 2026291200)
02:57:19, 08 Dec. ppp1: Revoked prefix = 2a00:23c5:2a06:d000::/56 (valid time = 2026291200 / preferred time = 2026291200)
02:57:17, 08 Dec. dsl:VDSL Link Down: duration was 10182 seconds
4) There was talk of a firmware bug making a lot of uploading a problem. On 5Mbit up I've pushed 4GB in a 24 hour period, equivalent to saturating the upstream for 2 hours. I dont know what device did it, but is that enough to cause a problem for the HH?
 
5) my event log is pages and pages of "wl0:IGMP join received for group 239.255.3.22 on interface wl0" - ive found reference to this being chromecast-related, of which I have two, but the problem was allegedly fixed long ago in a firmware update. Perhaps this is a red herring.
 
This little period of relative stability has put me off trying the draytek for now, but if there are any nuggets to be gleamed from the above I would be very grateful to hear about them.
 
Thank you! Adrian.
0 Ratings
Distinguished Sage
Distinguished Sage
52 Views
Message 13 of 15

Re: At wits end with infinity drop outs

The DSL drop in the early morning , every few days, seems normal for some VDSL connections, I have seen it on my daughter`s VDSL connection, so I assume its something to do with DLM?

In your case it looked like the Draytek reset itself, so that seems to indicate that it may be faulty.

Its difficult to tell what is going on, as I am only familiar with the logs from the TP Link router.

My daughter has a chromecast unit, but I have not seen any issues on the TP Link LAN log, but the chromecast is connected to a BT 600 wireless hotspot in a bedroom, so the IGMP requests do not seem to get onto the LAN.

Her house is old, with thick brick walls, so there are a few wireless hotspots in the bedrooms, and also to provide Ethernet connectivity.

If the Draytek continues to reboot, then it may be worth trying the TP Link unit I mentioned

-----------------------------------------------------------------------------------

Communityhelp (Private website) Lots of additional information and help.
You will need to be connected to your home BT Broadband connection to view it, or any links to it that I post on this forum.

0 Ratings
adrianhand
Beginner
44 Views
Message 14 of 15

Re: At wits end with infinity drop outs

Thank you Keith - as I said I've not actually tried an alteranate router yet because the connection was (relatively) stable - all the logs and info above are from my BT hub.

Regardless, it went down again about an hour ago and came back up with a record low sync speed (27.4Mb) since my openreach visitor reset the DLM six days ago like so:

06:23:14, 09 Dec. :Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
06:23:13, 09 Dec. :VLAN VLAN_DATA disconnected
06:23:13, 09 Dec. ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
06:23:13, 09 Dec. BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
06:23:12, 09 Dec. BR_LAN:The LAN DHCPv6 Server is active
06:23:12, 09 Dec. ppp1:The DYN ROUTE [81.139.57.100/32 gw ] is deleted
06:23:12, 09 Dec. ppp1:The DYN ROUTE [81.139.56.100/32 gw ] is deleted
06:23:11, 09 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
06:23:10, 09 Dec. BR_LAN:The LAN DHCPv6 Server is active
06:23:10, 09 Dec. BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
06:23:10, 09 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
06:23:10, 09 Dec. BR_LAN:The LAN DHCPv6 Server is active
06:23:10, 09 Dec. ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
06:23:10, 09 Dec. BR_LAN:The LAN DHCPv6 Server is inactive
06:23:10, 09 Dec. BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
06:23:10, 09 Dec. BR_LAN: Revoked prefix = 2a00:23c5:2a06:d000::/64 (valid time = 2026291200 / preferred time = 2026291200)
06:23:10, 09 Dec. ppp1: Revoked prefix = 2a00:23c5:2a06:d001::/64 (valid time = 2026291200 / preferred time = 2026291200)
06:23:10, 09 Dec. ppp1: Revoked prefix = 2a00:23c5:2a06:d000::/56 (valid time = 2026291200 / preferred time = 2026291200)
06:23:08, 09 Dec. dsl:VDSL Link Down: duration was 98727 seconds
0 Ratings
Distinguished Sage
Distinguished Sage
36 Views
Message 15 of 15

Re: At wits end with infinity drop outs

If those logs were from the home hub, then what caused the device reset I wonder?

I do not use a home hub, which is why I did not recognise the logs.

As to what caused the DSL to drop at 06:23, is difficult to say, especially if you say there is no noise on the line. People have reported that the home hubs do seem to drop the line for no reason.

-----------------------------------------------------------------------------------

Communityhelp (Private website) Lots of additional information and help.
You will need to be connected to your home BT Broadband connection to view it, or any links to it that I post on this forum.

0 Ratings