Billion UK Forum

The firmware can be found,

http://www.billion.uk.com/esupport/inde ... 4-firmware

Hi i've upgraded, all working.

Any improvements the new DSL code brings or is it just stability etc...

swatboy79 wrote:Hi i've upgraded, all working.

Any improvements the new DSL code brings or is it just stability etc...

I think it only improves stability (from one other customer that had VDSL drops, with this firmware seems rock solid)

I upgraded my 8800NL to 2.32d.dh14 yesterday, not because I had any dissatisfaction with the previous .dm2 , but just to be current. The upgrade worked fine and after restoring the backup config settings file, all connected fine. The stats immediately showed an increase in downstream power from the usual 17.2 to 17.4 and the sync rate remained almost the same at 3225 (used to be 3232).....but the max linerate dropped from its previous 3800 to 3580. OK, no problem, gave it 24 hours to bed-in. Oh dear, the usual extreme stability of the SNRM - previously varying during daytime by +/- 0.1db now varied by +/- 0.3db from minute-to-minute and the CRC error rate trippled from 20/min to 75/min (average over a 24 hour period.....a low 5/m in daytime and higher 250/m during dark hours).

So today I've reverted to firmware 2.32d.dm4 ..... I don't have a copy of the original 2.32d.dm2 but I understand the difference between .dm2 and .dm4 is purely cosmetic .... and lo and behold it is now performing brilliantly as it had done up till yesterday. Stats are power 17.2db, SNRM 5.1, Sync Rate 3225, Max Rate 3812 and SNRM variation is +/- 0.1db

So for my particular router on my specific very long line (57.5db on ADSL2), the older firmware is the better choice. It may be a different case for other lines and scenarios though.

The 8800NL is by far and away the very best modem/router out of the 130+ others I've experimented with since 2008 and I'm so happy with it that I've ended my quest for the best router I can find.......I've found it!

Bitsea wrote:I upgraded my 8800NL to 2.32d.dh14 yesterday, not because I had any dissatisfaction with the previous .dm2 , but just to be current. The upgrade worked fine and after restoring the backup config settings file, all connected fine. The stats immediately showed an increase in downstream power from the usual 17.2 to 17.4 and the sync rate remained almost the same at 3225 (used to be 3232).....but the max linerate dropped from its previous 3800 to 3580. OK, no problem, gave it 24 hours to bed-in. Oh dear, the usual extreme stability of the SNRM - previously varying during daytime by +/- 0.1db now varied by +/- 0.3db from minute-to-minute and the CRC error rate trippled from 20/min to 75/min (average over a 24 hour period.....a low 5/m in daytime and higher 250/m during dark hours).

So today I've reverted to firmware 2.32d.dm4 ..... I don't have a copy of the original 2.32d.dm2 but I understand the difference between .dm2 and .dm4 is purely cosmetic .... and lo and behold it is now performing brilliantly as it had done up till yesterday. Stats are power 17.2db, SNRM 5.1, Sync Rate 3225, Max Rate 3812 and SNRM variation is +/- 0.1db

So for my particular router on my specific very long line (57.5db on ADSL2), the older firmware is the better choice. It may be a different case for other lines and scenarios though.

The 8800NL is by far and away the very best modem/router out of the 130+ others I've experimented with since 2008 and I'm so happy with it that I've ended my quest for the best router I can find.......I've found it!

Attached is 2.32d.dm2 (stock firmware) incase you/others need it

Is it better to restart with factory default or current setting, or don't it matter.

nitrams69 wrote:Is it better to restart with factory default or current setting, or don't it matter.

Default settings, to ensure all changes within the firmware are implemented correctly (the DMT code being the main upgrade in this firmware)

Just updated the firmware yesterday and sadly this morning I just encountered a massive problem where I had to restart the all router.
Never had one single ISP issue and was getting mixed results from various mobile devices some working some not getting internet access properly until I did some quick troubleshooting

Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:

1 117 ms 24 ms 78 ms [192.168.1.254]
2 * * * Request timed out.
3 64 ms 126 ms 286 ms te0-4-0-0.pr1.enlba.ov.easynet.net [89.200.135.9
0]
4 67 ms 50 ms 1746 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]

5 * * * Request timed out.
6 113 ms 1540 ms 208 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
7 41 ms 128 ms 77 ms 132.185.255.165
8 * 356 ms 753 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Not just an ISP issue as the router itself was already failing to respond on a timely fashion (the usual 1ms) and the webpage of the router wasn't even opening properly in the meantime.

All good after the restart although I never had such an issue prior to this firmware and ever with my ISP
I did a factory default option when upgrading the firmware and then copied the config file saved before upgrading.

If this happens again I will default the router and build the configuration manually and otherwise if ever this happens again I will rollback with the previous built.

noriga wrote:Just updated the firmware yesterday and sadly this morning I just encountered a massive problem where I had to restart the all router.
Never had one single ISP issue and was getting mixed results from various mobile devices some working some not getting internet access properly until I did some quick troubleshooting

Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:

1 117 ms 24 ms 78 ms [192.168.1.254]
2 * * * Request timed out.
3 64 ms 126 ms 286 ms te0-4-0-0.pr1.enlba.ov.easynet.net [89.200.135.9
0]
4 67 ms 50 ms 1746 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]

5 * * * Request timed out.
6 113 ms 1540 ms 208 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
7 41 ms 128 ms 77 ms 132.185.255.165
8 * 356 ms 753 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Not just an ISP issue as the router itself was already failing to respond on a timely fashion (the usual 1ms) and the webpage of the router wasn't even opening properly in the meantime.

All good after the restart although I never had such an issue prior to this firmware and ever with my ISP
I did a factory default option when upgrading the firmware and then copied the config file saved before upgrading.

If this happens again I will default the router and build the configuration manually and otherwise if ever this happens again I will rollback with the previous built.

With this firmware it is advised to rebuid the config from scratch, using the web gui, it was never advised to restore settings from a previous firmware builds.

I have reset the router to default and manually entered the configuration where everything seem to be working at normal except from the Email Alert feature which before used to work but now it does no longer work as the pop-up window of the account test stays in a Testing status but does not get through the end.

I can confirm that I have no issues in sending emails from my outlook client with the same account and before this worked previous to upgrade to this firmware.
Can someone please test this for me before I try and default the router once again?

Thanks
Max