firmware 2.52

[Pete-B]

6D 14H 15M 33S

[ZicoUK]

If it's not one thing it's another .

Went to bed a little late last night/this morning and the router hadn't restarted at a little over 1 day and 11 hours from what I recall.

I was hoping to get back in from work today and see it reaching almost 2 days but no, I have 3 hours!**

**Don't worry though, it's not the router that restarted but the damn boiler engineer that tripped the the electrics out earlier this afternoon .

Hopefully I may get to the point where I can give some proper feedback on the uptime .

[gerdesj]

None of my routers have restarted since I last posted. However, I'm going to update all of them to 2.52.d10_t1.

I have uptime charts going back nearly all year. The bigger the blue triangles the better and as you can see September has not been a good month. Ignore the order of the units on the x axis, there is a scaling factor issue which looks to be 100.

[picbits]

Well I've upgraded to 2.52.d10_t1 - fingers crossed.

It may not be a very fair test though as I've moved ISP's and now on a 40/10 profile compared to a 80/20 (running at around 63/19)

Fingers crossed.

[ZicoUK]

Well I've upgraded to 2.52.d10_t1 - fingers crossed.

It may not be a very fair test though as I've moved ISP's and now on a 40/10 profile compared to a 80/20 (running at around 63/19)

Fingers crossed.

I don't think that connection profile is likely to be a cause of any restarts (though obviously only Billion know what may be causing any issues).

Update on my own uptime; I'm at just under 1 day and 4 hours taking into account the power issue yesterday afternoon.

On a side note, I noticed that my VDSL connection is at a higher speed than normal at 65xxxKbps down and 17xxxKbps up (usually ~52xxxKbps down and 11xxxKbps up). The SNR margins are low at ~1.3 down and ~1.7 up at the time of writing (again normally ~6.5 down/up when connected at the lower speeds). I know that the cause of the low SNR is due to my line connecting before another line on the same overhead DP and thus If I were to manually reconnect, my line speeds will likely return to the lower connection speeds and higher SNR margins.

Strangely enough, since flashing the test firmware, my router is holding at the current connection. Only negative is the thousands of downstream FEC errors (not a major issue) and the increased downstream interleave depth at 1279 compared to 1 at all other times (likely to be linked to the continual restarts and the DLM kicking in from the cab).

[ZicoUK]

Looks like the test firmware is good. Little under 2 days at the moment. The longest uptime in the last month.

[picbits]

Annoyingly I've had to manually restart mine a couple of times. I was meant to be assigned a static IP which didn't happen so had to reboot.

It does seem quite stable though - not had a random reboot yet.

[billion_fan]

Annoyingly I've had to manually restart mine a couple of times. I was meant to be assigned a static IP which didn't happen so had to reboot.

It does seem quite stable though - not had a random reboot yet.

We can now confirm devices running the test firmware have been up for 12 days without any reboots.

Official firmware is now released and can be found below

http://www.billion.uk.com/esupport/inde ... are-252d11

[ZicoUK]

Current uptime from mine is 5 days, 3 hours and 20 minutes.

Question Billion_fan. Is the official release any different from the test firmware? If there is no other difference other than naming, I will stick with the test for the time being (I have downloaded the official release anyway).

**Edit**
Thanks also for the prompt fix. Thanks also to Pete-B for his testing.

[Pete-B]

@ZicoUK Your welcome.

The "System Up-Time" on 2.52.d10_t1 firmware was 12D 7H before I upgraded it to 2.52.d11.
2.52.d11 is currently on 7H 11M up-time.

The "DSL PHY and Driver Version" and "Wireless Driver Version" appear to be unchanged between 2.52.d10 & 2.52.d11.