Contents > BT v6.1 firmware:
Deployed in 2009 to existing BT 2700HGV hubs running v126.96.36.199 firmware.
(Jan 2014): BT are still deploying v188.8.131.52 firmware to existing BT 2700HGV hubs running v184.108.40.206.x firmware. You may wish to use Adrian C's static route hack to block the update if you prefer v6.1 firmware.
'Zedman' from The-Scream forums reports his Dual SSID hub has been automatically upgraded to the new v220.127.116.11 firmware.
His 2700HGV Hub details:
Dual SSID model, assembly no. 4201-003003-007
Prior to upgrade: Official BT v18.104.22.168
DNS poison entries pbthdm.bt.motive.com 10.0.0.0 & cwmp.cms.smehomehubrms.bt.com 10.0.0.0
ISP is BT 'Home' Broadband.
The above DNS poison entries failed to block the firmware update to v22.214.171.124. (I seem to recall when I used to use BT v4.25.33 firmware on a Single SSID hub in late 2006, the DNS poison entry also failed to block an automatic upgrade to v5.29.107.x at the time)
'Zedman' also tried to manually downgrade the firmware.
The home/tech/upgrade page does not work.
The home/upgrade page is accessible but any attempts to downgrade the firmware appears will fail with the following message when using v5.x recovery firmware:
The upgrade was unsuccessful.
Unfortunately, the software upgrade could not be completed.
Please click "Back" to try again or click "Cancel" to return to the gateway page.
The home/mdc page is also no longer accessible.
Some screen shots of the new firmware for the 'Home', 'Settings' and 'Site Map' pages.
Some pages which were previously only accessible via the Management Console, now appear to have been relocated for easier access. eg. DNS resolution table and access to System logs.
The hub also polls the provisioning server: pbthdm.bt.motive.com
Once again, a big thank you to 'Zedman' for the information and pictures provided so far on this new BT v126.96.36.199 firmware.
Frequently Asked Questions:
(Added Aug 2011): Is BT still upgrading any BT 2700HGV with v188.8.131.52 to v184.108.40.206.1 firmware? It's been almost 2.5 years since BT started the v6 upgrade programme during 2009. If you have acquired an unused hub with v220.127.116.11 and it has or has not been upgraded to v18.104.22.168.1 firmware recently, please let me know.
Is the v6 firmware being propagated to any 2700HGV with v22.214.171.124 or v126.96.36.199 using BT keycode which are NOT on the BT business or home broadband networks? BT v188.8.131.52 Dual SSID hubs which were not on BT networks were first targeted in early March 2009. Hubs running v184.108.40.206 firmware and where BT had already updated them to point to their new provisioning servers, will have been subsequently upgraded to v220.127.116.11 firmware, before being upgraded to v6 firmware.
Have any Single SSID 2700HGV hubs been upgraded to BT v6.x firmware? I have one confirmed report from Chris who has a single SSID hub (Assy No. 4200-003003-004) which has been upgraded to BT v6.x fw. His ISP is ADSL24.
Can the v6 firmware upgrade be blocked using DNS Poisoning? No. It doesn't work.
BT v5.29.107.x firmwares have a 'Remote Management' check box in the Advanced Firewall menu. Will unticking it block the firmware upgrade? No.
Can changing the key code block any forced upgrade? No, as an o2 user has reported he was using 2wire's manual setup generic key code.
Is there any other way of blocking the v6 upgrade? Yes, Simon has developed a way of changing the name of the provisioning server on a hub with BT v5.x firmware which can be used to block upgrades. Click here for details
Is any BT firmware immune from this v6 upgrade? We believe all BT v4.x and the BT v18.104.22.168 'recovery' firmware, and hubs using BT v22.214.171.124 'Recovery firmware' are immune. The v6 upgrade only appears to affect hubs running BT v126.96.36.199 firmware.
Has BT started shipping brand new 2700HGV hubs with v6 firmware already pre-installed? Yes, brand new Dual SSID hubs with Assembly no. 4201-003003-008 shipped with earlier v188.8.131.52-enh.tm with serial no. commencing 4308 (which places the manufacture date around Oct 2008).
If I enable OpenZone function on my hub, does this mean it becomes an OpenZone hotspot? Yes.
Does BT v6 firmware support uPnP ? From observations and application tests with v184.108.40.206.1-enh.tm, there is no evidence to suggests it supports uPnP.
Where has the home/mdc page gone? There is no Management Console page on BT or Telecom v6 firmwares.
Is the new BT v6 firmware better than BT v5 firmware? Simple answer is 'No'. Wireless power cannot be changed at present on BT version of firmware;
Cannot be used with 3rd party VOIP provider; there are bugs in the firmware, and the menus can be somewhat sluggish to navigate compared to older v4/v5 firmwares.
Is the new BT v220.127.116.11 firmware available as a file which I can use to upgrade my 2700 hub? No. An early trial BT v18.104.22.168-enh.tm firmware is available – see the dedicated BT v22.214.171.124 firmware page.
(11 Oct 09): What is the difference between v126.96.36.199-enh.tm and v188.8.131.52.1-enh.tm ? v184.108.40.206.1-enh.tm contains an interim fix to address some problems with VPN. There is now a later v220.127.116.11 firmware which is available to BT business customers on request who continue to have VPN issues. It is not for global release - it is also unlikely to address all the technical issues identified to date.
(Aug 11): Can I downgrade to v4 or v5 firmware? No. However, you may wish to consider installing the Qwest v6 firmware if the 2GB file download limitation is not an issue. (Personally, I've had fewer issues with BT v18.104.22.168.1 than the Qwest firmware)
v22.214.171.124-enh.tm is the version number of the new BT firmware which is gradually being rolled out by BT to their business customers with main rollout apparently starting from November 2008.
Firmware versions reported to me since February 2009 appear to be:
The new v6 firmware enables BT OpenZone hotspots to be created.
Well done Simon, he deserves a medal. I can confirm too I am able to change and save settings in the Setting > Broadband > Link Configuration page too.
Simon also notes that after the factory reset, the OpenZone function was enabled by Default. When he clicked the 'Disable' button, the status changed to 'Pending' with an explanation message:
The changes may not be instantaneous. It could take up to 30 minutes for the service to be fully enabled or disabled because of the need to communicate with the BT network. The status shows as pending until this process has completed.
With my own hub which was recently upgraded to v126.96.36.199.1, it took 2 or 3 working days to enable or disable OpenZone.
(Update 3 Jul 09): We have got hold of the HTML source code for the wireless settings page provided Telecom v188.8.131.52 firmware which supports wireless power setting. Unfortunately, we are still unable to hack the BT v184.108.40.206.1 firmware - 2wire have well and truly blocked any attempt to adjust the wireless power setting in the BT branded v6 firmware.
'Simon' also notes that on the Settings > LAN > Statistics reporting page, the wireless power is displayed and appears to be set to '1' on his hub, but there is no means of changing the value as this is an information only reporting page. My own hub still reports a value of '2' which was how I had previously configured the wireless power prior to the forced v6.x upgrade.
My hub offers 13 wireless channels. Simon reports his hub also offers an 'Auto' option.
I don't recall this feature being available on v5 firmwares but you can now set the speed of the four individual ethernet ports.
(Added 7 Mar 09) According to this BT webpage, all brand new factory shipped BT 2700HGV hubs with v6.1.x firmware pre-installed since January 2009 appear to have a default system password. The password corresponds to the serial number of the hub. The serial number can be found on the label attached to the underside of the hub.
If you need to clone the hardware MAC address of your ISP supplied modem or router, to a 2700HGV with BT v6 firmware, I'm afraid this is no longer possible.
Similarly, it is no longer possible to define a HOST name for the hub.
Next Page: BT v6.1 Technical Issues and Bugs
Use 'Back' button to return to previous page or click here to return to main menu