cancel
Showing results for 
Search instead for 
Did you mean: 
dfects
Contributor
2,288 Views
Message 1 of 67

Pages of TR69 ConnectionRequest Failed

Hiya,

 

Our internet just disconnected so I had a look through the logs and noticed for the last 2-3 days the event log is literally full of these, maybe 8-10 pages worth with no successfull requests since Friday:

 

21:30:56, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:28:14, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:28:14, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:28:14, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:28:14, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:27:46, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:27:46, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:27:45, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:27:45, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:26:52, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:26:52, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:26:52, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:26:52, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:24:21, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:24:21, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:24:21, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:24:21, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:23:18, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:23:18, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:23:18, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:23:18, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:21:35, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:20:21, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:20:21, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:20:21, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:20:21, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:19:42, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:19:42, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS
21:19:42, 27 Nov.
ppp1:TR69 ConnectionRequest Failed
21:19:42, 27 Nov.
ppp1:TR69 ConnectionRequest: processing request from ACS

It doesn't seem to have affected the internet the last few days (apart from the recent reconnect but that could be unrelated)

 

Any ideas or something to worry about?

0 Ratings
Reply
66 REPLIES 66
Distinguished Expert
Distinguished Expert
2,254 Views
Message 2 of 67

Re: Pages of TR69 ConnectionRequest Failed

Are you using the HH6?

Which firmware version is your hub using?

 

Do you have the log entries showing the disconnect? And does your hub reboot at 14 day intervals?

If it doesn't affect your connection or speeds, then perhaps it's better to wait, until it reboots.

 

The downside is that it fills your log listing, and you will have difficulty searching for old events.

0 Ratings
Reply
dfects
Contributor
2,235 Views
Message 3 of 67

Re: Pages of TR69 ConnectionRequest Failed

Thanks for the reply. It rebooted roughly around 14 days, is that a normal thing?

 

Here's the log:

 

22:01:47	 27 Nov.	ppp1:TR69 ConnectionRequest: processing request from ACS	
22:01:46	 27 Nov.	ppp1:TR69 ConnectionRequest Failed	
22:01:46	 27 Nov.	ppp1:TR69 ConnectionRequest: processing request from ACS	
22:01:30	 27 Nov.	:HTTP UserAdmin login from 192.168.1.7 successfully	
22:01:27	 27 Nov.	ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed	
22:01:27	 27 Nov.	ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated	
22:01:27	 27 Nov.	InformResponse:TR69 receiving message	
22:01:26	 27 Nov.	ppp1:TR69 event found : 4 VALUE CHANGE	
22:01:26	 27 Nov.	ppp1:TR69 event found : 1 BOOT	
22:01:25	 27 Nov.	ppp1:TR69 sending Inform message	
22:01:25	 27 Nov.	ppp1:TR69 event found : 4 VALUE CHANGE	
22:01:25	 27 Nov.	ppp1:TR69 event found : 1 BOOT	
22:01:24	 27 Nov.	ppp1:TR69 sending Inform message	
22:01:23	 27 Nov.	ppp1:TR69 creating new session with ACS	
22:01:20	 27 Nov.	:HTTP UserBasic login from 192.168.1.7 successfully	
22:01:07	 27 Nov.	BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0	 O_flag = 1
22:01:07	 27 Nov.	BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0	 O_flag = 1
22:01:07	 27 Nov.	ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36	
22:01:07	 27 Nov.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
22:01:07	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	BR_LAN: Allocated address = 0000:23c4:64ce:0000:0000:29ff:0000:347b (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:64ce:0000::/56 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	ppp1: Allocated address = 0000:23c4:0000:2a01:42c7:29ff:fe04:3479 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:07	 27 Nov.	ppp1:WAN DHCPv6 Mode : Statefull	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	BR_LAN: Allocated address = 0000:23c4:64ce:0000:0000:29ff:0000:347b (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:64ce:0000::/56 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated address = 0000:23c4:0000:2a01:42c7:29ff:fe04:3479 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
22:01:06	 27 Nov.	BR_LAN: Revoked prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	BR_LAN: Allocated address = 0000:23c4:64ce:0000:0000:29ff:0000:347b (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	BR_LAN: Allocated prefix = 0000:23c4:64ce:0000::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:64ce:0000::/56 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated address = 0000:23c4:0000:2a01:42c7:29ff:fe04:3479 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:0000:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1:WAN DHCPv6 Mode : Statefull	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:64ce:0000::/56 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:06	 27 Nov.	ppp1: Allocated prefix = 0000:23c4:64ce:0000::/56 (valid time = 2026291200 / preferred time = 2026291200)	
22:01:04	 27 Nov.	ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36	
00:01:45	 01 Jan.	ppp1:WAN DHCPv6 Mode : Statefull	
00:01:44	 01 Jan.	ppp1:WAN Router Discovery Setting Updated : M_flag = 1	 O_flag = 0
00:01:42	 01 Jan.	BR_LAN:UPnP functionality has been activated	
00:01:42	 01 Jan.	BR_LAN:UPnP functionality has been deactivated (manually)	
00:01:39	 01 Jan.	ppp1:New DYN ROUTE is added [00.139.00.100/32 gw ]	
00:01:39	 01 Jan.	ppp1:New DYN ROUTE is added [00.139.00.100/32 gw ]	
00:01:39	 01 Jan.	:WAN: SENSING AUTO VDSL 	
00:01:39	 01 Jan.	ppp1:PPP: PPP INFO 00.139.00.100	00.139.00.100
00:01:39	 01 Jan.	ppp1:PPP: PPP INFO 	
00:01:39	 01 Jan.	ppp:PPP: IPCP_NAK	
00:01:39	 01 Jan.	ppp:PPP: CHAP_SUCCESS	
00:01:39	 01 Jan.	ppp:PPP: CHAP_RESPONSE 	
00:01:39	 01 Jan.	ppp:PPP: LCP_GOOD_ACK 	
00:01:39	 01 Jan.	ppp:PPP: LCP_REQUEST 	
00:01:37	 01 Jan.	:PPPoE error: timeout	
00:01:26	 01 Jan.	:PPPoE error: timeout	
00:01:20	 01 Jan.	:PPPoE error: timeout	
00:01:08	 01 Jan.	ptm0.101:VLAN VLAN_DATA connected	
00:01:08	 01 Jan.	:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]	
00:01:08	 01 Jan.	:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]	
00:01:08	 01 Jan.	dsl:VDSL link Up: Down Rate=36688Kbps	 Up Rate=8988Kbps
00:01:04	 01 Jan.	BR_LAN:UPnP functionality has been activated	
00:01:03	 01 Jan.	:The LAN DHCP Server is active	
00:01:03	 01 Jan.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:01:02	 01 Jan.	eth1:An Ethernet port is now connected (2/100/FULL)	
00:00:58	 01 Jan.	:The LAN DHCP Server is inactive	
00:00:52	 01 Jan.	BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:00:52	 01 Jan.	BR_LAN:UPnP functionality has been deactivated (manually)	
00:00:44	 01 Jan.	BR_LAN:UPnP functionality has been activated	
00:00:44	 01 Jan.	eth1:A device has been disconnected from an Ethernet port (2)	
00:00:42	 01 Jan.	:The LAN DHCP Server is active	
00:00:40	 01 Jan.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:00:39	 01 Jan.	eth1:An Ethernet port is now connected (2/10/HALF)	
00:00:37	 01 Jan.	:This Rule has been applied successfully: [id:1	 InternalClient: 192.168.1.7
00:00:37	 01 Jan.	:Adding port mapping rule by UPnP	
00:00:37	 01 Jan.	:Updating port mapping rule (1) by UPnP	
00:00:36	 01 Jan.	:DNS name resolution is now active	
00:00:36	 01 Jan.	wl0:WLAN has been deactivated (BTWifi-X) (band : 5GHz).	
00:00:35	 01 Jan.	wl0:WLAN has been deactivated (BTWifi-with-FON) (band : 5GHz).	
00:00:35	 01 Jan.	wl0:WLAN has been deactivated (BTHub6-HM39) (band : 5GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTWifi-X) (band : 2.4GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTWifi-with-FON) (band : 2.4GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTHub6-HM39) (band : 2.4GHz).	
00:00:34	 01 Jan.	Default:Firewall change to Level: FRWL	
00:00:34	 01 Jan.	wl0:(0/44) Channel Hopping initiated/Manually initiated	
00:00:33	 01 Jan.	wl1:(0/11) Channel Hopping initiated/Manually initiated	
00:00:33	 01 Jan.	:The Modem has successfully powered up	
00:00:22	 01 Jan.	:WAN: ethernet as LAN 	
00:01:03	 01 Jan.	BR_LAN:UPnP functionality has been activated	
00:01:02	 01 Jan.	:The LAN DHCP Server is active	
00:01:02	 01 Jan.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:01:02	 01 Jan.	eth1:An Ethernet port is now connected (2/100/FULL)	
00:00:57	 01 Jan.	:The LAN DHCP Server is inactive	
00:00:51	 01 Jan.	BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:00:51	 01 Jan.	BR_LAN:UPnP functionality has been deactivated (manually)	
00:00:44	 01 Jan.	BR_LAN:UPnP functionality has been activated	
00:00:43	 01 Jan.	eth1:A device has been disconnected from an Ethernet port (2)	
00:00:42	 01 Jan.	:The LAN DHCP Server is active	
00:00:40	 01 Jan.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
00:00:40	 01 Jan.	eth1:An Ethernet port is now connected (2/10/HALF)	
00:00:37	 01 Jan.	:This Rule has been applied successfully: [id:1	 InternalClient: 192.168.1.7
00:00:37	 01 Jan.	:Adding port mapping rule by UPnP	
00:00:37	 01 Jan.	:Updating port mapping rule (1) by UPnP	
00:00:35	 01 Jan.	:DNS name resolution is now active	
00:00:35	 01 Jan.	wl0:WLAN has been deactivated (BTWifi-X) (band : 5GHz).	
00:00:35	 01 Jan.	wl0:WLAN has been deactivated (BTWifi-with-FON) (band : 5GHz).	
00:00:35	 01 Jan.	wl0:WLAN has been deactivated (BTHub6-HM39) (band : 5GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTWifi-X) (band : 2.4GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTWifi-with-FON) (band : 2.4GHz).	
00:00:35	 01 Jan.	wl1:WLAN has been deactivated (BTHub6-HM39) (band : 2.4GHz).	
00:00:34	 01 Jan.	Default:Firewall change to Level: FRWL	
00:00:34	 01 Jan.	wl0:(0/44) Channel Hopping initiated/Manually initiated	
00:00:34	 01 Jan.	wl1:(0/11) Channel Hopping initiated/Manually initiated	
00:00:33	 01 Jan.	:The Modem has successfully powered up	
00:00:26	 01 Jan.	:The Modem underwent a warm reset	
00:00:22	 01 Jan.	:WAN: ethernet as LAN 	
21:55:28	 27 Nov.	dsl:VDSL Link Down: duration was 1212658 seconds	
21:55:28	 27 Nov.	:VLAN VLAN_DATA disconnected	
21:55:28	 27 Nov.	:Connection to the Internet has been terminated.(Reboot	Reconfiguration
21:55:28	 27 Nov.	:Connection to the Internet has been terminated.(Reboot	Reconfiguration
21:55:28	 27 Nov.	BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0	 O_flag = 1
21:55:28	 27 Nov.	ppp1:The DYN ROUTE [00.139.00.100/32 gw ] is deleted	
21:55:28	 27 Nov.	ppp1:The DYN ROUTE [00.139.00.100/32 gw ] is deleted	
21:55:27	 27 Nov.	BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0	 O_flag = 1
21:55:27	 27 Nov.	ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36	
21:55:26	 27 Nov.	BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)	
21:55:26	 27 Nov.	BR_LAN: Revoked prefix = 0000:0000:64ce:2a00::/64 (valid time = 2026291200 / preferred time = 2026291200)	
21:55:26	 27 Nov.	ppp1: Revoked prefix = 0000:0000:64ce:2a01::/64 (valid time = 2026291200 / preferred time = 2026291200)	
21:55:26	 27 Nov.	ppp1: Revoked prefix = 0000:0000:64ce:2a00::/56 (valid time = 2026291200 / preferred time = 2026291200)	
21:55:26	 27 Nov.	:A device reset was performed (GUI/Button)	

It sadly rebooted again about 7.20 this morning, now we've dropped down another cap from 32.40 to 30.00 😞 SNR is at 6/9.4 now (was hovering around 6/6.9 before that having dropped from 6/8.6 from a couple of weeks ago)

 

Its a homehub 6a, firmware version SG4B10002236 (30-Oct-2016)

 

We were one of the first on our estate to get vdsl, not sure if its just cross talk being introduced from new connections thats dropping our speeds.

 

The event log is still failing TR69, but its overshadowed now by IPV6 "BR_LAN: Allocated prefix" messages.

0 Ratings
Reply
Dippu
Aspiring Expert
2,227 Views
Message 4 of 67

Re: Pages of TR69 ConnectionRequest Failed

I have noticed this TR69 ConnectionRequest failed issue for the last 2 days (Saturday and Sunday) and the pages are full of it. I am using HH6 with #2236 firmware. I have not suffered any disconnection though and the connection is stable other than the usual 14 day reboot phenomena which is due on Sunday 4th Dec.

 

0 Ratings
Reply
dfects
Contributor
2,224 Views
Message 5 of 67

Re: Pages of TR69 ConnectionRequest Failed

I have a feeling my disconnect this morning and lower speed is due to something else... the SNR has been decreasing over the last 2-3 weeks dropping into the sixes mid day yesterday. As I'm on a banded line, the higher the SNR the better so guessing it just got too low and lowered my band to compensate 😞 Was hoping it would go the other way. We're still in our speed estimate of 27.7 to 37.7 though so its not too bad at the moment. Our upload is exceeding the estimate by 2-3mbs still!?

 

IPv6 messages seemed to have stopped, still lots of failing tr69 messages though.

0 Ratings
Reply
Highlighted
Distinguished Expert
Distinguished Expert
2,223 Views
Message 6 of 67

Re: Pages of TR69 ConnectionRequest Failed

Thanks for your reply.

This seems to be a new, or unreported problem. Perhaps more cases will be posted.

My HH6, same firmware, has similiarly started to make failed TR69 connection requests at 4 minute intervals, over the past two days.

As with yours, there's one successful update / connection daily.

It doesn't affect data throughput though. You could try streaming Breakfast TV programs on your PC......

 

It doesn't look as if the 14 day scheduled reboot helps. Mine is due to reboot at midnight tonight.

 

You could try a factory reset, which may help.

(Unrelated, BUT, I've found that after a factory reset, the subsequent reconfiguring of preferred settings is best done over an Ethernet connection, in case there are wireless problems.)

 

There's just a chance that the new firmware - 223E, may come unexpectedly, so may may prefer to wait to do the factory reset after this.

0 Ratings
Reply
Distinguished Expert
Distinguished Expert
2,217 Views
Message 7 of 67

Re: Pages of TR69 ConnectionRequest Failed


@dfects wrote:

I have a feeling my disconnect this morning and lower speed is due to something else... the SNR has been decreasing over the last 2-3 weeks dropping into the sixes mid day yesterday. As I'm on a banded line, the higher the SNR the better so guessing it just got too low and lowered my band to compensate 😞 Was hoping it would go the other way. We're still in our speed estimate of 27.7 to 37.7 though so its not too bad at the moment. Our upload is exceeding the estimate by 2-3mbs still!?

 

IPv6 messages seemed to have stopped, still lots of failing tr69 messages though.


Sorry the replies crossed. Interesting that Dippu has posted similar problems, re. TR69.

0 Ratings
Reply
dfects
Contributor
2,209 Views
Message 8 of 67

Re: Pages of TR69 ConnectionRequest Failed

My BT hub is actually used only as a modem to the best extent it can... all wifi off with a much better router plugged in and set to be in the DMZ with a fixed lease. Works suprisingly well and those are the only setting changes i've made. I'm guessing something else could be screwed though with how it configures itself. It thinks roughly 37mb is the highest attainable speed so there has to be some form of noise or interference causing it to drop to 30mb but it is a long line (over 1km). The last I heard about a month or so ago my neighbour has only been able to get 16mb out of his line!

 

Is there a new firmware being slowly pushed out at the moment then? I don't wish to disconnect the hub any more than needed so will leave it connected for a few days after the update if so before trying a factory reset.

 

Thanks

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
2,195 Views
Message 9 of 67

Re: Pages of TR69 ConnectionRequest Failed

You would be much better off getting a proper Openreach modem rather than using the Hub.

0 Ratings
Reply
dfects
Contributor
2,187 Views
Message 10 of 67

Re: Pages of TR69 ConnectionRequest Failed

Do you mean like the HG612 3B?

0 Ratings
Reply