Print

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

[Chrysalis]

apparently 20 or so disconnects a day is tolerated so its odd people report DLM taking action after one power cycle.

I have even power cycled my modem before whilst waiting to be put back on fast path and then had DLM put me back on fast path the same 24 hour period as a power cycle.

[perry081064]

apparently 20 or so disconnects a day is tolerated so its odd people report DLM taking action after one power cycle.

I have even power cycled my modem before whilst waiting to be put back on fast path and then had DLM put me back on fast path the same 24 hour period as a power cycle.

i can provide my last 3 months stats that would prove otherwise. (maybe even 5 months if i can find them ).

in the three disconnects ive had over that period (managed powerdowns ), all three have caused DLM to increase interleave higher than before and never drop back.

im obviously in the minority , but its there in black and white , im dreading a powercut or severe weather

[NewtronStar]

apparently 20 or so disconnects a day is tolerated so its odd people report DLM taking action after one power cycle.

I have even power cycled my modem before whilst waiting to be put back on fast path and then had DLM put me back on fast path the same 24 hour period as a power cycle.

It's seems you have put yourself forward to test the 20 disconnects in a 24 hour period using the 30 minute delay off/on theory

[Chrysalis]

apparently 20 or so disconnects a day is tolerated so its odd people report DLM taking action after one power cycle.

I have even power cycled my modem before whilst waiting to be put back on fast path and then had DLM put me back on fast path the same 24 hour period as a power cycle.

It's seems you have put yourself forward to test the 20 disconnects in a 24 hour period using the 30 minute delay off/on theory

I think it was a plusnet rep who mentioned 20.  It will be lower tho on the stable DLM profiles.

[boe323]

So is the bt agent removed? or is it just the tab?, and is it better to disable 801.1p values, ive read that 7 is the highest priority yet the main bandwidth is set lower than bts update and control bandwidth, unless its changed now, what I read was made in 1998. Ive also changed ip bridge to pppoe bridge and turned off dhcp transparent transmission, is that wise?, whats the difference between the 2?, also as its only passing internet to the hub and that's doing the rest, don't see the need for transparent transmission, seems to be more responsive on web pages but I don't know much about it ans would like to know whats best.

[twdsamy]

Many thanks yet again

[Ixel]

Does anyone know yet if this updated firmware reduces the number of errors, especially from someone connected to an ECI cabinet? I'm currently using the ECI /r modem as it's only device that seems to keep my line on fastpath.

[Chrysalis]

probably not as is same blob version.

[les-70]

  The new firmware performance of the vdsl/adsl side is the same as before.  If you willing to manually limit the HG612 sync speed down to a value not a lot more than the speed you would get on interleaved the HG612 you should maintain fastpath in most cases.  Using e.g. "xdslcmd configure --maxDataRate 64000 16000  100000" and  aiming for a snrm of about 8-9 rather than 6 reduces my error rates by about a factor of 4-5.

[Ixel]

  The new firmware performance of the vdsl/adsl side is the same as before.  If you willing to manually limit the HG612 sync speed down to a value not a lot more than the speed you would get on interleaved the HG612 you should maintain fastpath in most cases.  Using e.g. "xdslcmd configure --maxDataRate 64000 16000  100000" and  aiming for a snrm of about 8-9 rather than 6 reduces my error rates by about a factor of 4-5.

I see.

Yes I did all that a long way in the past (maxDataRate), it didn't make a huge difference to the odd and occasional errors, enough in some cases to cause DLM to switch to interleaving. I'll stick to the ECI /r since that keeps me on fastpath without needing to cap the speed further.

[boe323]

Using all default settings ,ive had my first resync , my profile is the lowest its ever been in 3 years  , last night around 1.30am, it started spitting out crcs by the hundreds and made the modem resync, it happens on my line rarely as I think nextdoor as got something faulty, but the previous firmware was able to keep sync.

[planetf1]

I just upgraded my HG612 - running the previous unlocked/webgui firmware using the file:

bcm96368MVWG_fs_kernel_HG612V100R001C01B030SP08_webgui
from
https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w

After doing this, the modem itself reports under "status":

V100R001C01B030SP06

Is this expected, or a bad package?

I used the web admin UI to upgrade

[Chrysalis]

is fine

[Bald_Eagle1]

I just upgraded my HG612 - running the previous unlocked/webgui firmware using the file:

bcm96368MVWG_fs_kernel_HG612V100R001C01B030SP08_webgui
from
https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w

After doing this, the modem itself reports under "status":

V100R001C01B030SP06

Is this expected, or a bad package?

I used the web admin UI to upgrade

Doing it through the modem's GUI isn't recommended (if that's what you meant) as it doesn't fully update the firmware/software.

Following Asbokid's original instructions is the only sure fire way to ensure a 'full' update.


Strictly speaking, you should now be seeing this:-

software version: V100R001C01B030SP08

(Not V100R001C01B030SP06)

[planetf1]

Ok, I'll try that at some point soon.

Odd that the fw did update to some extent but to the july version ? So can someone running the unlocked web gui confirm they see 08 ?

Full info is

Product type   EchoLife HG612 
Device ID   <withheld>
Hardware version   VER.B
Software version   V100R001C01B030SP06
Firmware version   A2pv6C038m.d24j
Batch number   BC1P6.030.A2pv6C038m.d24j
System up time   0 days 4 hours 32 minutes 27 seconds