Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Chrysalis]

  My trial of 2.32e has ended with the 8800NL freezing after about 18 hours and not responding on LAN or WLAN.  TBB pings also stopped, hard to say if remained in sync or not.  Prior to that event it all looked good. I was running two instances of dslstats, one on  a pi and one on the pc.  The HG612 is always happy with two dslstats but i don't know if I have done that with the 8800NL before.

  I will do some tests today with multiple telnet sessions but is anyone aware multiple session or other lockup issues with the 8800NL?

my 8800nl had some kind of lockup with over 100 days uptime some weeks back, it did remain in sync confirmed by a test did by plusnet.

Bear in mind tho.

1 - I had a very long uptime and only ever seen this once.
2 - it was on the old firmware, it actually triggered me to update my firmware.

[les-70]

I have dropped back to the previous firmware for a while.  I had no issues with the previous firmware. 

[aruba]

With 2.32e, is anyone else still having the issue with regular ping spikes when the wireless is turned on? (I am!)

[les-70]

  I did, but I am back to the HG612 at the moment.

[aruba]

Thanks, it is good to know I'm not the only one.

I'm tempted to send the thing back as there always seems to be some niggle with it.

[les-70]

  I doubt whether the spikes are anything to bother about, it may only reflect ICMP priority in the 2.32e firmware.  Apart from the 2.32e firmware I have found the device totally fault and niggle free.  With 2.32e it was equally fine except that a lock out issue appeared, that lock out was unacceptable but the previous firmware was fine for me. 

[Chrysalis]

les will you try the new firmware again? you seemed quick to abandon it.

Its ok here, but I am using device in bridge mode, my one single lockup was on the older firmware after 100+ days.

[les-70]

  Yes I plan to try it again, I was not too keen to do much testing as the as the dsl driver was the same as the previous version and that version was issue free for me.  Curiosity is however slowly getting the better of me. 

[Jaggies]

I tried reverting to the previous firmware but got an error about it not being a valid file.

So, following the advice of others, I switched the QOS on and back off, and my upstream has gone up by 1Mb...





I think I can live with that for now, but will hang fire on future upgrades until I've checked out the feedback on here and on the Billion forum...

Oh, and ping has dropped from 40ms to 24ms, although a Command line ping is much more reliable as a diagnostic tool.

>ping www.google.co.uk

Pinging www.google.co.uk [216.58.210.3] with 32 bytes of data:
Reply from 216.58.210.3: bytes=32 time=22ms TTL=57
Reply from 216.58.210.3: bytes=32 time=22ms TTL=57
Reply from 216.58.210.3: bytes=32 time=22ms TTL=57
Reply from 216.58.210.3: bytes=32 time=22ms TTL=57

Ping statistics for 216.58.210.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 22ms, Average = 22ms



I do continue to have the ping spikes on my BQM, but I my experience hasn't been affected by it, so I can live with that as well... 

[kitz]

That 2 hrly spike may be nothing to do with the actual router.

Its something I sometimes see when using my Zyxel and Ive never been able to get to the bottom of it.   Ive mentioned it a couple of times on here.   It tends to be more obvious on some gateways than others and since it doesnt seem to affect anything performance wise I just ignore it now.