Print

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

[Bald_Eagle1]

Still unsure what this new software is supposed to fix as it's different to 2013 update I can't see any change visually in bandplans 

As per usual, there is a distinct lack of info from BT regarding this update.

As nothing appears to have changed stats-wise, it is rumoured to be the VPN issue fix that became apparent following the October 2013 firmware update.

[NewtronStar]

Still unsure what this new software is supposed to fix as it's different to 2013 update I can't see any change visually in bandplans 

As per usual, there is a distinct lack of info from BT regarding this update.

As nothing appears to have changed stats-wise, it is rumoured to be the VPN issue fix that became apparent following the October 2013 firmware update.

Right then it sounds like a software update for the HG612 firewall/security when using Virtual Private Networking.

[Bald_Eagle1]

It might be, but that's only a 'guess' at this stage.

[Chrysalis]

it changes nothing dsl side as its same blob.

why arent you flashing the nobtagent version? that will stop it upgrading again.

[Ronski]

To be honest there is no need for the GUI on the modem, except for changing the IP address, and wasn't there a telnet method for that?

[Bald_Eagle1]

To be honest there is no need for the GUI on the modem, except for changing the IP address, and wasn't there a telnet method for that?

There is a telnet method that works - I have tested it.

However, it doesn't survive a modem reboot.

It is something I could build into the resync procedure though, to initially use the default 192.168.1.1 & then apply the IP address as specified in the ini file & use that.


I think that changing the IP address causes an 'on the fly' resync though (from my vague recollection).

If that's the case, there would then be 2 resyncs in quick succession at each resync.
DLM might not 'like' that happening too often & as we know, it can sometimes appear to be over aggressive.

[NewtronStar]

To be honest there is no need for the GUI on the modem, except for changing the IP address, and wasn't there a telnet method for that?

I turn off leds when the HG612 is stable and turn them on when swapping dsl devices and the only option that does this via the HG612's built in GUI and unless someone codes a stats moniter for Andriod then 192,168,1,1 is as close as you'll get to see any stats on your tablet.

it changes nothing dsl side as its same blob.

why arent you flashing the nobtagent version? that will stop it upgrading again.

was waiting to see if there was any developments before reverting back to wolfys firmware this time with the no-btagent active.

[Ronski]

There is a telnet method that works - I have tested it.

However, it doesn't survive a modem reboot.

It is something I could build into the resync procedure though, to initially use the default 192.168.1.1 & then apply the IP address as specified in the ini file & use that.

Thats a pain not surviving a reboot. If the PC in use was on a totally different IP subent such as 10.10.10.103 like mine at work, would it even be reachable on 192.168.1.1? I suppose you'd need a static route setup, then it may as well be left at it's default. Or just flash the GUI firmware, change the IP and let it update

I turn off leds when the HG612 is stable and turn them on when swapping dsl devices and the only option that does this via the HG612's built in GUI and unless someone codes a stats moniter for Andriod then 192,168,1,1 is as close as you'll get to see any stats on your tablet.

Doesn't DLStats have a webserver feature you can use on your internal network?

[Bald_Eagle1]

Thats a pain not surviving a reboot. If the PC in use was on a totally different IP subent such as 10.10.10.103 like mine at work, would it even be reachable on 192.168.1.1?

Thinking about it, it probably wouldn't.

I suppose you'd need a static route setup, then it may as well be left at it's default. Or just flash the GUI firmware, change the IP and let it update

Flashing with the the GUI firmware & letting it update is probably the easier method.

Doesn't DLStats have a webserver feature you can use on your internal network?

FWIW, tbailey2 is currently developing a webstats page for HG612 Modem Stats, for which I'll have work out some code to upload data at intervals (possibly each minute).

See the attached for development to date.

[Chrysalis]

To be honest there is no need for the GUI on the modem, except for changing the IP address, and wasn't there a telnet method for that?

the gui auto refreshes every second, so useful for frequent snrm monitoring.

I used it when testing snrm fluctuation during calls.

[Ronski]

FWIW, tbailey2 is currently developing a webstats page for HG612 Modem Stats, for which I'll have work out some code to upload data at intervals (possibly each minute).

See the attached for development to date.

Looking very good, if it's easier I may be able to create the required data from within the GUI, but obviously it would need to be running.

[Ronski]

Looks like my software version at home updated the other morning.

17/07/2014 at 18:30 - Software version change detected, changed to V100R001C01B030SP08 from V100R001C01B030SP06

[NewtronStar]

Looks like my software version at home updated the other morning.

17/07/2014 at 18:30 - Software version change detected, changed to V100R001C01B030SP08 from V100R001C01B030SP06

Thanks Ronski for keeping us updated into this odd Software Version change.

Do you think Wolfy will be able to mod V100R001C01B030SP08 and give us back the HG612's GUI ?

[Ronski]

I would of thought so, but until he or someone else capable takes a look who knows.

[AdriHD]

*sigh* mine died this morning. I had a momentary power cut (well the neighbourhood did) and when it came back it, this time it didn't have GUI/telnet. usually it does after a reboot :-/ When I get some time, I'll try and get an eprom dump from it to see what mess BT left me