topic Re: Firmware upgrade in Archived Posts

Firmware upgrade

MrAngree — Wed, 09 Dec 2020 15:28:39 GMT

Anybody else had a Firmware upgrade dated 5-12-20

EE Smarthub

Firmware updated: 5-Dec-2020 Firmware version:v0.06.01.08190-EE

Previously =Downstream sync speed: 29.56Mbps Actual download speed 25-26Mbps

After Firmware downgrade.

Downstream sync speed: 25.00Mbps Actual download speed 19/20Mbps

Where has my speed gone ...why have you stolen it EE.

Re: Firmware upgrade

Chris_B — Wed, 09 Dec 2020 17:26:55 GMT

@MrAngree Have you tried restarting the router? Turn it off for 30+ seconds then restart it and test.

Re: Firmware upgrade

MrAngree — Wed, 09 Dec 2020 18:12:42 GMT

yes restarted from inside the hub manager....

waiting to see if loads of other people affected..

previously the hub has restarted automatically and given me a speed of 19mbs...This obviously not good enough rebooted the hub and got 25mbs back....dont know why they mess with it so much.........Previous isps speed the same every test this seems a random . Like a game of roulette you wonder what speed you are going to get when you test it.

I will try another reboot and see if im lucky.......

Re: Firmware upgrade

XRaySpeX — Wed, 09 Dec 2020 19:03:11 GMT

Welcome to EE's Home Broadband Forum.

If you would like help with your BB speed or connection issues, please would you carry out the following steps for starters, which will enable us to diagnose the problem and advise you further. Do not restart your router to do these tests:

1. Post your full router stats:

For a BrightBox: login and go to Advanced Settings/ System/ DSL Status. Also post 'System Uptime' from top of System Log page.
For a SmartHub: login and go to Advanced Settings/ Technical Log/ Information. Obscure your names & any numbers in the BB Username & also the SSIDs.

Full router stats are key to any speed & connection issues.

2. Try a wired speedtest, using an Ethernet cable supplied with the router, here http://www.thinkbroadband.com/speedtest.html . Click on the "Results Page" button at the bottom of the graph you first see and then copy to here just the "Link to this result:" link that you see below the next main graph.

3. What does BT Wholesale Broadband Availability Checker estimate for your phone number? Post just the whole table and the line above it, blanking out your phone number. If it doesn't recognise your phone number or you don't have one, use the Address Checker, not the Postcode Checker.

Re: Firmware upgrade

MrAngree — Wed, 09 Dec 2020 21:04:36 GMT

well that looks like a message from a robot.

I have already stated the facts.

EE have changed something their end.

New Firmware...SLoooooWer Internet speeds nothing else to sort.

Re: Firmware upgrade

MrAngree — Thu, 10 Dec 2020 10:57:30 GMT

07:35:59, 10 Dec. admin login success from 192.168.1.216
07:18:35, 10 Dec. admin timeout from 192.168.1.216
07:09:50, 10 Dec. DHCP device Connected: 192.168.1.216, ec:8e:b5:d9:52:48, heinzypantzy-510-p199na
07:09:49, 10 Dec. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
07:09:49, 10 Dec. A device connected to Ethernet port 1
07:09:49, 10 Dec. Wire Lan Port 1 up, Speed 1000 Mbps
07:09:49, 10 Dec. Receive a DHCP request
07:08:42, 10 Dec. A device disconnected from Ethernet port 1
07:08:42, 10 Dec. Wire Lan Port 1 down, Speed 10 Mbps
07:08:30, 10 Dec. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
07:08:14, 10 Dec. A device connected to Ethernet port 1
07:08:14, 10 Dec. Wire Lan Port 1 up, Speed 1000 Mbps
06:46:39, 10 Dec. CWMP: HDM socket closed successfully.
06:46:39, 10 Dec. CWMP: HDM socket opened successfully.
06:46:39, 10 Dec. CWMP: Set Parameter by TR069 Success.
06:46:38, 10 Dec. CWMP: HDM socket closed successfully.
06:46:38, 10 Dec. CWMP: HDM socket opened successfully.
06:46:38, 10 Dec. CWMP: session completed successfully
06:46:38, 10 Dec. CWMP: HDM socket closed successfully.
06:46:37, 10 Dec. CWMP: HDM socket opened successfully.
06:46:37, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
06:46:37, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
06:46:37, 10 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
06:45:44, 10 Dec. CWMP: HDM socket closed successfully.
06:45:44, 10 Dec. CWMP: HDM socket opened successfully.
06:45:44, 10 Dec. CWMP: Set Parameter by TR069 Success.
06:45:43, 10 Dec. CWMP: HDM socket closed successfully.
06:45:43, 10 Dec. CWMP: HDM socket opened successfully.
06:45:42, 10 Dec. CWMP: HDM socket closed successfully.
06:45:42, 10 Dec. CWMP: HDM socket opened successfully.
06:45:42, 10 Dec. CWMP: session completed successfully
06:45:42, 10 Dec. CWMP: HDM socket closed successfully.
06:45:37, 10 Dec. CWMP: HDM socket opened successfully.
06:45:37, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
06:45:37, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
06:45:37, 10 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
05:49:59, 10 Dec. 5G Client associate from 74:a7:ea:46:f0:c0 (IP=192.168.1.109) RSSI=-31, Rate=866Mbps, host amazon-ad228f167
05:49:58, 10 Dec. Receive a DHCP request
04:45:39, 10 Dec. CWMP: HDM socket closed successfully.
04:45:39, 10 Dec. CWMP: HDM socket opened successfully.
04:45:39, 10 Dec. CWMP: Set Parameter by TR069 Success.
04:45:38, 10 Dec. CWMP: HDM socket closed successfully.
04:45:38, 10 Dec. CWMP: HDM socket opened successfully.
04:45:37, 10 Dec. CWMP: HDM socket closed successfully.
04:45:37, 10 Dec. CWMP: HDM socket opened successfully.
04:45:37, 10 Dec. CWMP: session completed successfully
04:45:37, 10 Dec. CWMP: HDM socket closed successfully.
04:45:36, 10 Dec. CWMP: HDM socket opened successfully.
04:45:35, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
04:45:35, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
04:45:35, 10 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
02:45:36, 10 Dec. CWMP: HDM socket closed successfully.
02:45:36, 10 Dec. CWMP: HDM socket opened successfully.
02:45:36, 10 Dec. CWMP: Set Parameter by TR069 Success.
02:45:35, 10 Dec. CWMP: HDM socket closed successfully.
02:45:35, 10 Dec. CWMP: HDM socket opened successfully.
02:45:34, 10 Dec. CWMP: HDM socket closed successfully.
02:45:34, 10 Dec. CWMP: HDM socket opened successfully.
02:45:34, 10 Dec. CWMP: session completed successfully

Re: Firmware upgrade

MrAngree — Thu, 10 Dec 2020 10:58:12 GMT

02:45:34, 10 Dec. CWMP: HDM socket closed successfully.
02:45:33, 10 Dec. CWMP: HDM socket opened successfully.
02:45:33, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
02:45:33, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
02:45:33, 10 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
01:47:47, 10 Dec. DHCP device Disconnected: 192.168.1.216, ec:8e:b5:d9:52:48, heinzypantzy-510-p199na
01:47:46, 10 Dec. A device disconnected from Ethernet port 1
01:47:46, 10 Dec. Wire Lan Port 1 down, Speed 10 Mbps
00:59:32, 10 Dec. CWMP: HDM socket closed successfully.
00:59:32, 10 Dec. CWMP: HDM socket opened successfully.
00:59:32, 10 Dec. CWMP: session completed successfully
00:59:32, 10 Dec. CWMP: HDM socket closed successfully.
00:59:32, 10 Dec. CWMP: HDM socket opened successfully.
00:59:32, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
00:59:31, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
00:59:31, 10 Dec. CWMP: Initializing transaction for event code 4 VALUE CHANGE
00:59:00, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:57, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:54, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:50, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:49, 10 Dec. NTP synchronization success
00:58:47, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:44, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:41, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:39, 10 Dec. WAN Sensing Auto sensing Complete, interface selected
00:58:38, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:37, 10 Dec. WAN DHCPv6 events: INIT
00:58:36, 10 Dec. NTP synchronization start
00:58:35, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:33, 10 Dec. WAN Sensing Auto sensing Running
00:58:33, 10 Dec. Success - secondary DNS servers
00:58:33, 10 Dec. Success - primary DNS servers
00:58:33, 10 Dec. WAN connection WAN2_INTERNET_PTM connected
00:58:32, 10 Dec. PPP: IPCP up
00:58:32, 10 Dec. PPP IPCP Receive Configuration ACK
00:58:32, 10 Dec. PPP IPCP Send Configuration Request
00:58:32, 10 Dec. PPP IPCP Receive Configuration NAK
00:58:32, 10 Dec. PPP IPCP Send Configuration ACK
00:58:32, 10 Dec. PPP IPCP Receive Configuration Request
00:58:32, 10 Dec. PPP IPV6CP Send Configuration Request
00:58:32, 10 Dec. PPP IPCP Send Configuration Request
00:58:32, 10 Dec. PPP: CHAP authentication succeeded
00:58:32, 10 Dec. PPP CHAP Receive success : authentication successful
00:58:32, 10 Dec. PPP CHAP Receive Challenge
00:58:32, 10 Dec. PPP: LCP up
00:58:32, 10 Dec. PPP LCP Send Configuration ACK
00:58:32, 10 Dec. PPP LCP Receive Configuration Request
00:58:31, 10 Dec. PPP LCP Receive Configuration ACK
00:58:31, 10 Dec. PPP LCP Send Configuration Request
00:58:28, 10 Dec. PPP: Received PADS
00:58:28, 10 Dec. PPP: Sending PADR
00:58:28, 10 Dec. PPP: Received PADO
00:58:28, 10 Dec. PPP: Sending PADI
00:58:23, 10 Dec. PPP: Sending PADI
00:58:18, 10 Dec. PPP: Sending PADI
00:58:13, 10 Dec. PPP: Sending PADI
00:58:08, 10 Dec. PPP: Starting PPP daemon
00:58:07, 10 Dec. WAN Auto-sensing detected port DSL WAN
00:58:07, 10 Dec. DSL Link Up: Down Rate=24998kbps, Up Rate=6834kbps; SNR Margin Down=7.8dB, Up=6.0dB
00:57:35, 10 Dec. WAN Sensing Auto sensing Complete, interface selected

Re: Firmware upgrade

MrAngree — Thu, 10 Dec 2020 10:58:58 GMT

00:57:34, 10 Dec. WAN Sensing Auto sensing Running
00:57:33, 10 Dec. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
00:57:28, 10 Dec. PPP: Stopped PPP daemon(0,1,5)
00:57:24, 10 Dec. PPP LCP Send Termination Request (User request)
00:57:21, 10 Dec. PPP LCP Send Termination Request (User request)
00:57:21, 10 Dec. PPP: IPCP down
00:57:21, 10 Dec. PPP: LCP down
00:57:21, 10 Dec. DSL Link Down: duration was 24081 seconds
00:46:34, 10 Dec. CWMP: HDM socket closed successfully.
00:46:34, 10 Dec. CWMP: HDM socket opened successfully.
00:46:34, 10 Dec. CWMP: Set Parameter by TR069 Success.
00:46:33, 10 Dec. CWMP: HDM socket closed successfully.
00:46:33, 10 Dec. CWMP: HDM socket opened successfully.
00:46:32, 10 Dec. CWMP: HDM socket closed successfully.
00:46:32, 10 Dec. CWMP: HDM socket opened successfully.
00:46:32, 10 Dec. CWMP: session completed successfully
00:46:32, 10 Dec. CWMP: HDM socket closed successfully.
00:46:32, 10 Dec. CWMP: HDM socket opened successfully.
00:46:31, 10 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
00:46:31, 10 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
00:46:31, 10 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
23:27:05, 09 Dec. DHCP device Disconnected: 192.168.1.228, 88:ad:d2:d9:80:28, android-db919d0232c431c4
23:26:59, 09 Dec. 2.4G Client disassociate from 88:ad:d2:d9:80:28  (IP=192.168.1.228) RSSI=0, Rate=0Mbps
23:26:59, 09 Dec. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
22:46:32, 09 Dec. CWMP: HDM socket closed successfully.
22:46:32, 09 Dec. CWMP: HDM socket opened successfully.
22:46:32, 09 Dec. CWMP: Set Parameter by TR069 Success.
22:46:31, 09 Dec. CWMP: HDM socket closed successfully.
22:46:31, 09 Dec. CWMP: HDM socket opened successfully.
22:46:30, 09 Dec. CWMP: HDM socket closed successfully.
22:46:30, 09 Dec. CWMP: HDM socket opened successfully.
22:46:30, 09 Dec. CWMP: session completed successfully
22:46:30, 09 Dec. CWMP: HDM socket closed successfully.
22:46:30, 09 Dec. CWMP: HDM socket opened successfully.
22:46:29, 09 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
22:46:29, 09 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
22:46:29, 09 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
22:13:34, 09 Dec. admin login success from 192.168.1.216
21:45:31, 09 Dec. CWMP: HDM socket closed successfully.
21:45:31, 09 Dec. CWMP: HDM socket opened successfully.
21:45:30, 09 Dec. CWMP: Set Parameter by TR069 Success.
21:45:30, 09 Dec. CWMP: HDM socket closed successfully.
21:45:29, 09 Dec. CWMP: HDM socket opened successfully.
21:45:29, 09 Dec. CWMP: session completed successfully
21:45:29, 09 Dec. CWMP: HDM socket closed successfully.
21:45:29, 09 Dec. CWMP: HDM socket opened successfully.
21:45:29, 09 Dec. CWMP: Server URL: https://ee.x.x; Connecting as user: ACS username
21:45:29, 09 Dec. CWMP: Session start now, server: https://ee.x.x, Event code: 
21:45:29, 09 Dec. CWMP: Initializing transaction for event code 2 PERIODIC
20:30:59, 09 Dec. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
20:30:58, 09 Dec. Receive a DHCP request
20:15:30, 09 Dec. CWMP: HDM socket closed successfully.
20:15:30, 09 Dec. CWMP: HDM socket opened successfully.
20:15:30, 09 Dec. CWMP: Set Parameter by TR069 Success.
20:15:29, 09 Dec. CWMP: HDM socket closed successfully.
20:15:29, 09 Dec. CWMP: HDM socket opened successfully.
20:15:28, 09 Dec. CWMP: HDM socket closed successfully.
20:15:27, 09 Dec. CWMP: HDM socket opened successfully.

Re: Firmware upgrade

MrAngree — Thu, 10 Dec 2020 11:06:28 GMT

This was where the upgrade happened but still showed

00:52:53, 05 Dec. DSL Link Up: Down Rate=29059kbps, Up Rate=6750kbps; SNR Margin

it has gradually become slower 28mbps 27mbps.... now 25mbps..............

db919d0232c431c4, lease duration is 86400 seconds

00:57:37, 05 Dec. 2.4G Client associate from 88:ad:d2:d9:80:28 (IP=192.168.1.228) RSSI=-31, Rate=1Mbps, host android-db919d0232c431c4
00:57:37, 05 Dec. Receive a DHCP request
00:57:36, 05 Dec. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
00:53:26, 05 Dec. NTP synchronization success
00:53:11, 05 Dec. WAN Sensing Auto sensing Complete, interface selected
00:53:10, 05 Dec. NTP synchronization start
00:53:09, 05 Dec. WAN DHCPv6 events: INIT
00:53:06, 05 Dec. WAN Sensing Auto sensing Running
00:53:06, 05 Dec. Success - secondary DNS servers
00:53:06, 05 Dec. Success - primary DNS servers
00:53:06, 05 Dec. WAN connection WAN2_INTERNET_PTM connected
00:52:58, 05 Dec.  5G   WiFi auto selected channel 40 Bandwidth:80M(Reason:boot)
00:52:57, 05 Dec.  2.4G WiFi auto selected channel 6 Bandwidth:20M(Reason:boot)
00:52:53, 05 Dec. WAN Auto-sensing detected port DSL WAN
00:52:53, 05 Dec. DSL Link Up: Down Rate=29059kbps, Up Rate=6750kbps; SNR Margin Down=6.3dB, Up=6.0dB
00:51:58, 05 Dec. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
00:51:57, 05 Dec. Upgrade and system start TR069
00:51:56, 05 Dec. System up
00:51:56, 05 Dec. Detect and configure Ethernet port1 as LAN
00:51:56, 05 Dec. Hub has activated against the device management system
00:51:56, 05 Dec. WAN Auto-sensing last connection port: DSL WAN
00:49:02, 05 Dec. NTP synchronization success
00:48:52, 05 Dec. WAN Sensing Auto sensing Complete, interface selected
00:48:49, 05 Dec. NTP synchronization start
00:48:49, 05 Dec. WAN DHCPv6 events: INIT
00:48:46, 05 Dec. WAN Sensing Auto sensing Running
00:48:46, 05 Dec. Success - secondary DNS servers
00:48:46, 05 Dec. Success - primary DNS servers
00:48:46, 05 Dec. WAN connection WAN2_INTERNET_PTM connected
00:48:38, 05 Dec.  5G   WiFi auto selected channel 40 Bandwidth:80M(Reason:boot)
00:48:37, 05 Dec.  2.4G WiFi auto selected channel 1 Bandwidth:20M(Reason:boot)
00:48:33, 05 Dec. WAN Auto-sensing detected port DSL WAN
00:48:33, 05 Dec. DSL Link Up: Down Rate=29036kbps, Up Rate=6690kbps; SNR Margin Down=6.1dB, Up=6.0dB
00:47:38, 05 Dec. Booting firmware v0.05.02.04290-EE (Wed Apr 29 18:51:15 2020)
00:47:37, 05 Dec. Upgrade and system start TR069
00:47:37, 05 Dec. System up
00:47:36, 05 Dec. Detect and configure Ethernet port1 as LAN
00:47:36, 05 Dec. Hub has activated against the device management system
00:47:36, 05 Dec. Hub has activated against the device management system
00:47:36, 05 Dec. WAN Auto-sensing last connection port: DSL WAN
00:10:34, 05 Dec. A device disconnected from Ethernet port 1
00:10:34, 05 Dec. Wire Lan Port 1 down, Speed 10 Mbps
00:10:22, 05 Dec. A device connected to Ethernet port 1
00:10:22, 05 Dec. Wire Lan Port 1 up, Speed 10 Mbps
00:10:21, 05 Dec. DHCP device Disconnected: 192.168.1.216, ec:8e:b5:d9:52:48, DESKTOP-CIT2O45
00:10:20, 05 Dec. A device disconnected from Ethernet port 1
00:10:20, 05 Dec. Wire Lan Port 1 down, Speed 10 Mbps
23:30:10, 04 Dec. Receive a DHCP request
17:56:24, 04 Dec. NTP synchronization success
17:56:08, 04 Dec. WAN Sensing Auto sensing Complete, interface selected
17:56:06, 04 Dec. WAN DHCPv6 events: INIT
17:56:06, 04 Dec. NTP synchronization start
17:56:02, 04 Dec. WAN Sensing Auto sensing Running
17:56:02, 04 Dec. Success - secondary DNS servers
17:56:02, 04 Dec. Success - primary DNS servers
17:56:02, 04 Dec. WAN connection WAN2_INTERNET_PTM connected
17:55:30, 04 Dec. WAN Auto-sensing detected port DSL WAN
17:55:30, 04 Dec. DSL Link Up: Down Rate=28386kbps, Up Rate=6818kbps; SNR Margin Down=6.1dB, Up=6.0dB

Re: Firmware upgrade

MrAngree — Thu, 10 Dec 2020 11:13:00 GMT

BT DATA

VDSL Range A (Clean) 45.3 32.4 8 6.1 25 Available Available --
VDSL Range B (Impacted)44.1 26.5 8 5.9 20 Available Available --

Max Observed Downstream SpeedMax Observed Upstream SpeedObserved Date

27.63	3.79
6.81	1.19
2020-11-10	2020-08-15

Re: Firmware upgrade

jennifersen — Wed, 02 Jun 2021 17:13:26 GMT

Wow I see you did what the robot requested, in full. Did EE ever bother to acknowledge?

Re: Firmware upgrade

XRaySpeX — Wed, 02 Jun 2021 17:40:24 GMT

Yes, 4 pages of complete guff produced by a robot itself , not at all what was requested! No help to man or beast for looking at OP's issue. LOL!

Re: Firmware upgrade

MrAngree — Wed, 02 Jun 2021 18:01:30 GMT

Not fixed its running at an embarrassing 15mbps at the moment

to be honest i might as well turn it off

EE broadband a bag of crap.Although i am quite enjoying doing 100,s of speed tests

and giving EE 1 star..............

Re: Firmware upgrade

XRaySpeX — Wed, 02 Jun 2021 18:59:16 GMT

@MrAngree : Well, you had your chance to have it looked at but you refused to cooperate. No wonder it hasn't improved when you cba'ed to allow us to investigate.

Re: Firmware upgrade

mikeliuk — Wed, 02 Jun 2021 19:36:15 GMT

Hi @MrAngree ,

Speaking as a person with five routers in the house, all of which have been the main house router in the past, if you suspect that new firmware has caused your router performance to degrade, the best way to prove this is by borrowing or buying an equally capable, or more capable, router and demonstrating that the line is able to support better performance.

The issue is then a case of who owns the faulty router. Where the service provider (e.g. in the case of Virgin Media) owns the router, the evidence will be sufficient to get a replacement. If the customer owns the router, it is more difficult.

Personally I don't think it's worthwhile to mess around with the only router available in the house because it could become bricked, and the evidence is just not as compelling with data from a single device (it's essentially the same as having a single data point even if you could downgrade the firmware). A capable router can usually be purchased for around GBP 50, and very good ones around GBP 200 (obviously go for one that is known-good with your service provider, with known-good configurations).

I understand your pain as I've been contracted with various providers giving very poor performance over a number of years and it was not nice. 🤓

Re: Firmware upgrade

XRaySpeX — Wed, 02 Jun 2021 19:48:59 GMT

There is absolutely no evidence. other than the OP's suspicion, that the issue lies with the router. It is more likely to be the state of the line & DLM, which I unsuccessfully tried to glean.

@mikeliuk wrote:

If the customer owns the router, it is more difficult.

Not so with EE. They will offer to replace a router at the drop of a hat even when it is evident that there is nowt wrong with it & the issue lies elsewhere.

Re: Firmware upgrade

mikeliuk — Wed, 02 Jun 2021 19:51:51 GMT

Hi @MrAngree ,

On the basis of the above, I would recommend you just try to ask for a replacement router on the basis that firmware provided by the service provider has apparently caused an issue. If the replacement performs the same, you can just return the replacement and there will be no loss to the service provider so it should be quite easy to persuade the service provider to send out a replacement, if only for debugging purposes. 😀

Re: Firmware upgrade

MrAngree — Wed, 02 Jun 2021 20:01:00 GMT

Mike

I don't know how this thread got started up again. this was from ages ago.

It wasn't the firmware upgrade that caused the problem but it was a coincidence that the

problem appeared at the same time as the firmware upgrade.

I have had two engineer visits since and two repairs that didn't last very long.

My problem is the crappy telephone wiring that supplies my house.

This would be the 3rd time i would let the open-each clowns have ago at fixing the problem. Its a stupid idea to try and run new technology with 70 year old cabling.

I was a mug to sign up to such dinosaur technology.

Re: Firmware upgrade

mikeliuk — Wed, 02 Jun 2021 20:09:01 GMT

Hi @MrAngree ,

My apologies, looking up the thread, I see it was @jennifersen who resurrected this thread.

I hit a similar problem in the past where I moved from cable to non-cable and the experience was awful. Definitely, new hardware and new technology is the way to go. From cable I've moved on to 4G mobile broadband and hope to move to 5G mobile broadband in the next year or two. Dinosaur technology and hardware is definitely not the way to go.

Glad you got things sorted. 😀