Print

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

[bbnovice]

Hi,

I seem to be in a minority of one with this problem so am starting a separate thread.

I’m not sure the problem is “fixable”, but I’ll post anyway in case this happens to anybody else.

I am using an unlocked HG612. Up until last night (13 October) it had not received the latest firmware update from BT.

Last night I suspect that BT pushed the update to my modem. I am not certain about this but the DS profile has now marginally improved according to the BT wholesale speed tester.

Since last night modem stats no longer works (even using telnet). The stats error log says “connect( ) ERROR !!!” 

Attempts to telnet the modem at the command level fail with the message “Could not open connection to the host on port 23. Connect failed”.
LAN 2 disappeared from the network map following a router reset. A direct connection between the PC and the modem does not work, LAN 2 appears to be inaccessible. The modem unlock instructions no longer work.

All the tests I have done have been with the PC firewall disabled so  that’s not the cause.

Apart from this the modem appears to be working 100%..

So I’m now stuck with no way to unlock the modem and no stats. And I can hardly phone BT and complain!  Frustrating.

Regards BBN

[broadstairs]

Have you tried Asbokids instructions for unlocking an HG612? See here.

Stuart

[Bald_Eagle1]

It is possible/likely that the firmware update (& the need for an updated HG612 Modem Stats program) caused a number of 'stuck' HG612_stats.exe processes.

This in turn could be causing too many login attempts & blocking telnet access.

If that's the case, terminating any 'stuck' processes may well clear things out, thus allowing telnet access.

I have attached an updated version of HG612_stats.exe that MIGHT deal with the new firmware, but I must warn that it is not fully tested yet as my own modem hasn't received the firmware update.

I am now on the same bandplan as you, so it seems the DSLAM udate has already happened.

[bbnovice]

Have you tried Asbokids instructions for unlocking an HG612? See here.

Stuart

Yes those are the instructions that I use for unlocking the HG612.

It is possible/likely that the firmware update (& the need for an updated HG612 Modem Stats program) caused a number of 'stuck' HG612_stats.exe processes.

Thanks for the suggestion, but if I understand you correctly, there are no "stuck" HG612 processes. I have also tried to connect to the HG612 via another different PC on the home network that is not running HG stats and that gets no response from 192.168.1.1 either. There is no firewall on the machine.  The PC I normally use is currently turned off.

To repeat - as far as I can tell the LAN2 port is now completely closed but the modem appears to operate normally apart from that.

Regards BBN

[bbnovice]

Hi BE:

Further to my post I've downloaded the revised version of the executable you attached to your post, but again the program fails due to being unable to connect to the modem. Here is the relevant part of the error log:
 

14/10/2013 20:05:51.848 - Initializing Winsock
14/10/2013 20:05:51.848 - WSAStartup() SUCCESSFUL!!!
14/10/2013 20:05:51.848 - Starting getaddrinfo()
14/10/2013 20:05:51.848 - getaddrinfo() O.K.
14/10/2013 20:05:51.848 - Starting socket()
14/10/2013 20:05:51.848 - socket() O.K.
14/10/2013 20:05:51.848 - Starting connect()
14:10/2013 20:06:12.877 - connect() ERROR!!!
14/10/2013 20:06:12.877 - About to close (sockfd)
14/10/2013 20:06:12.893 - About to WSACleanup()
14/10/2013 20:06:12.893 - About to free(txbuf)
14/10/2013 20:06:12.893 - About to free(rxbuf)
14/10/2013 20:06:12.893 - CURRENT-ISRUNNING-200541-443 DELETED

Regards BBN

[burakkucat]

Would you be willing to experiment?    If so, please read on . . .

• Disconnect anything plugged into the LAN1 and LAN2 ports of the HG612.
• Disconnect the HG612's PSU from the mains supply. As the DC output voltage drops, the HG612 will sense it and send a 'power fail' 'dying gasp' to the cabinet MSAN.
• Disconnect the xDSL connection to the HG612.
• With the HG612 totally isolated, power it up.
• Wait for one minute.
• Press and hold the 'Reset' button for ~20 seconds.
• Release the button and wait for one minute.
• Connect a computer to the LAN2 port and attempt to establish a telnet connection to the HG612.

If a telnet connection was successful . . .

• Disconnect the HG612's PSU from the mains supply.
• Disconnect your router's PSU from the mains supply.
• Connect the router's WAN port to the HG612's LAN1 port.
• Connect the xDSL to the HG612.
• Power up the HG612 and wait for it to stabilise.
• Power up the router and wait for it to establish a PPPoE session.
• Proceed as usual.

If a telnet connection was unsuccessful . . .

• With the HG612 still powered up, press and hold the 'Reset' button for ~20 seconds.
• Release the button and wait for one minute.
• Disconnect the HG612's PSU from the mains supply.
• Follow the original unlocking instruction steps, exactly.

Unless something very untoward has happened to your HG612, you should see the boot-loader's 'firmware upload' page. 

[bbnovice]

Hi bcat,

Just seen your post with the helpful instructions.

I will give them a go - not sure when as purely by coincidence one of my adult children has returned to the nest for a short while to use the spare PC on my home network - his own PC has just "brewed up" and that is not helpful as he works from home.  So the network is busy at the moment.
 
I will let you know how I get on .......

Regards BBN

[bbnovice]

Hello again bcat:

Now had an opportunity to try your advice. Followed instructions 1-8 but telnet was not restored. However reloading the unlocked firmware did work and HG stats is working again.

However I have now got a slightly revised profile (now 63.81/20 - was 64.37/20) so have lost about 0.5 download speed.

Many thanks for your help.

I suppose the modem may now receive another firmware update attempt from BT?

Regards

BBN

[ryant704]

I suppose the modem may now receive another firmware update attempt from BT?

Yeah, you can disable BT Agent to stop the updates.

[burakkucat]

Thank you for confirming what did and did not work, BBN. 

Yes, as Ryan has mentioned, the BT Agent can be disabled via the CLI. Please see my response to Chrys' query for the details.

[bbnovice]

Hi bcat,

I see the command to stop the BT Agent is killall -KILL start btagent .

But what is the command to restart it if I subsequently want to allow BT to push through a firmware update?

Regards  BBN

[NewtronStar]

Hi bcat,

I see the command to stop the BT Agent is killall -KILL start btagent .

But what is the command to restart it if I subsequently want to allow BT to push through a firmware update?

Regards  BBN

Just turn off the modem via power cable that should start the BT Agent again

[ryant704]

Hi bcat,

I see the command to stop the BT Agent is killall -KILL start btagent .

But what is the command to restart it if I subsequently want to allow BT to push through a firmware update?

Regards  BBN

There is no need to do this, Howling wolf has posted how and it works (I've tested turning off and on multiple times BT Agent via commands).

See here.

Just turn off the modem via power cable that should start the BT Agent again

[burakkucat]

But what is the command to restart it if I subsequently want to allow BT to push through a firmware update?

BBN -- See the good advice from fellow Kitizens, above. 

Wolfy has explained how to restart the BTAgent via the busybox shell, confirmed by Ryan and N*Star has mentioned the simple method -- power cycle the device, which implies a cold boot.