Re-sync the unlocked HG612

I may be blind, but have never found how to do this from the GUI.

I have now looked to see if it is possible from the Command Prompt.

Yes.

Telnet in as usual.

xdslcmd connection --down
Wait a bit if you wish
xdslcmd connection --up

Apologies to all who knew this, but I have never seen it posted.

Cannot try it on mine at present however under <BASIC>; <WAN>; there is a WAN connection enable. Wondering if that would force a re-sync?

There is always the Reboot option! A little drastic however it would force a re-sync.

Maintenance --> Device --> Reboot should do it.

Edit: just noticed previous reply saying this was a bit drastic

Edited by kasg (Sun 12-Jul-15 15:28:47)

In reply to a post by MHC:

Cannot try it on mine at present however under <BASIC>; <WAN>; there is a WAN connection enable. Wondering if that would force a re-sync?

Ouch!

I thought you had it there, but try it at your own risk!

I un-ticked WAN connection Enable and submitted it. After a few seconds the page refreshed with it un-ticked and the Enable marker at the top right = 0.

Went and looked at the HG612, DSL light still on. My earlier telnet method turned it off.

Then I came back down here to turn the WAN Enable back on and when I tried to access the modem got the TG582N login page! Hmmm thinks me! But I couldn't log into that over wifi.

Went to look, and the "Internet" light on it was red. Tried the wired machine, again not able to log into the router. Everything dead as far as I was concerned, all lights on the modem green, router OK except for this red light, both computers thinking they had internet access. Which they hadn't - both just giving the router login page but not able to log in.

Took the modem power plug out, waited a bit, plugged it back in. Came up looking OK but the router stayed Red for internet. Perhaps then I didn't wait long enough for the PPP session to come up. I'm not going to try again, so I shan't know if the power cycle on the modem had re-enabled the WAN connection. I think it unlikely.

Did a factory reset on the modem, knowing that should re-enable WAN. Once that came back up I still had to wait a long time for PPP to come up, hence my comment in the previous paragraph, but all is well.

A very strange result from un-ticking that box.

Well, it cause a resync!

Not quite what might have been expected though!

LOL

I was a little concerned when the modem lights said connected to the net, the router didn't, and I couldn't log into it. I decided to leave the other option, of rebooting the router, until after sorting out the modem.

Largely on the basis of it being a router in bridge mode so turning off the WAN was a little unpredictable without the documentation.

I was right in ruling out the router, but not being able to get into it was weird. I didn't think of feeling how hot it was - I wonder if its processor was going at 100% to try to establish PPP and the WAN Enable Off in the HG612 was blocking it?

In reply to a post by RobertoS:

I may be blind, but have never found how to do this from the GUI.

I have now looked to see if it is possible from the Command Prompt.

Yes.

Telnet in as usual.

xdslcmd connection --down
Wait a bit if you wish
xdslcmd connection --up

Apologies to all who knew this, but I have never seen it posted.

Not sure why you would want to do this as pulling the mains plug has i'm sure worked ok for many of us before now, what is their to gain by rebooting/or causing the modem to drop sync from within the GUI ?

In reply to a post by tommy45:

Not sure why you would want to do this as pulling the mains plug has i'm sure worked ok for many of us before now, what is their to gain by rebooting/or causing the modem to drop sync from within the GUI ?

So you can automate it via a script.

I have, at times, wanted to keep my network here up and running without any connection to the outside world - that includes having the modem running. So, the ability to Turn Off the line without having to physically unplug it can be useful. Or when trying to test fail over to a different bearer.

And when experimenting with an ADSL line, I actually wanted to resync every few minutes - I was looking to find the optimum time, xx minutes after dawn or similar. So, again a nice easy way - I also found that on a forced resync, DLM did not intervene as it knew it was deliberate act. This was with a different modem, however no reason why it could not be done on an HG612

In reply to a post by BatBoy:

In reply to a post by tommy45:

Not sure why you would want to do this as pulling the mains plug has i'm sure worked ok for many of us before now, what is their to gain by rebooting/or causing the modem to drop sync from within the GUI ?

So you can automate it via a script.

But why would someone want or need to do this? it seems a pointless exerise to me

In reply to a post by MHC:

I have, at times, wanted to keep my network here up and running without any connection to the outside world - that includes having the modem running. So, the ability to Turn Off the line without having to physically unplug it can be useful. Or when trying to test fail over to a different bearer.

And when experimenting with an ADSL line, I actually wanted to resync every few minutes - I was looking to find the optimum time, xx minutes after dawn or similar. So, again a nice easy way - I also found that on a forced resync, DLM did not intervene as it knew it was deliberate act. This was with a different modem, however no reason why it could not be done on an HG612

Not something that most of us would need really, as for DLM, that doesnt care how you reboot the modem, as dying gasp isnt utilised by DLM
anyway, power the thing off and leave for 30+mins before powering it up again and your good to go

In reply to a post by tommy45:

dying gasp isnt utilised by DLM

You know this for a fact?

In reply to a post by RobertoS:

In reply to a post by tommy45:

dying gasp isnt utilised by DLM

You know this for a fact?

that info regarding that is on the WWW

An unforced retrain is when it is assumed to be EU turning off the modem. DLM counts and uses unforced retrains and not dying gasps.

Edited by tommy45 (Mon 13-Jul-15 01:32:51)

You could probably just issue the single command

xdslcmd start --up

When i want to re-sync my (ADSL) connection I telnet in to my broadcom based router and issue the command

xdslcmd start --up --snr 90

This means I connect with a 5 dB SNRM at the lower end of an IP Profile.

In reply to a post by tommy45:

In reply to a post by RobertoS:

In reply to a post by tommy45:

dying gasp isnt utilised by DLM

You know this for a fact?

that info regarding that is on the WWW

An unforced retrain is when it is assumed to be EU turning off the modem. DLM counts and uses unforced retrains and not dying gasps.

Oh! How very interesting ... .

I wonder where that leaves this little quotation:-

R.OAM.4 The modem should support �dying gasp� as defined in Section 11.3.3.2 of G.993.2 and Section 7.1.1.2.3 of G.997.1.

Note: �Dying gasp� is not a mandatory requirement but CP�s are encouraged to implement this in their modems as it will enable the Openreach Test & Diagnostic systems to differentiate between a modem being turned off by the end user (loss of power) or a loss of signal (loss of connectivity) caused by a potential network or home wiring issue. This will support CPs in their diagnostic approach to ensure that their End Users have checked the relevant setup prior to submitting a fault to Openreach, thus avoiding a potentially chargeable engineering visit.

BT (Openreach) SIN 498, page 31.

I expect you're right Ian . I hadn't thought of that. Time to go back to bed with my second cup of morning tea .

Yes BT 's Sin, lol Where they also say that the CPE should be compatible with G.inp ect Some how they failed to find issues with some of their supplied CPE
such as the HH5 vA and the ECI modems

Whilst the Dslam may well be able to see this dying gasp, there is no conclusive evidence that DLM knows about it, Fine go ahead and reboot your modem multiple times in a 1hr window using a script or via the Gui and see what happens,are you volunteering to be guinea pig?

No need for him to be a guinea pig. It is known that a BT DSLAM will recognise the "dying gasp" from modems that support it and the alarm message generated at the DSLAM will indicate a "Loss of Power" and not "Loss of Frame" or "Loss of Sync". DLM will respond appropriately which in the case of "Loss of Power" means note it and do nothing.

If you want to prove us wrong, try it yourself and post the changes in sync speeds you see after each disconnect.

In reply to a post by MHC:

No need for him to be a guinea pig. It is known that a BT DSLAM will recognise the "dying gasp" from modems that support it and the alarm message generated at the DSLAM will indicate a "Loss of Power" and not "Loss of Frame" or "Loss of Sync". DLM will respond appropriately which in the case of "Loss of Power" means note it and do nothing.

If you want to prove us wrong, try it yourself and post the changes in sync speeds you see after each disconnect.

Lol no thank's i'll just continue to do what i have been doing for the past 2yrs , that being power off, and leave 30mins or more before powering the modem back up.but there again 1 or 2 resyncs in any 24hr period should never trigger DLM regardless of if forced or not , But where is the evidence that what BT says in it's sins is what happens in reality? whilst the dying gasp from modem maybe recognised by the dslam, it is down to DLM what happens or doesnt, and it is known that DLM does not react to such dying gasp signals, but works in a different way when it comes to it determining a power off/loss or loss of
sync,
And is why power cuts are sometimes the cause of DLM acting adversly where it shouldn't of done,

Edited by tommy45 (Mon 13-Jul-15 14:40:13)

If you think BT SIN's don't say what happens in reality, then send your evidence to Ofcom. They would be very interested, and so would all CPs.

You are talking about the specifications upon which six or seven-figure investments are made by CPs.
_{Cue rant about Ofcom being pathetic and toothless.}

To be fair, G.INP is a late addition to the SIN so it wasn't part of the original spec for which ECI supplied the modems.

Correct .

these sin's dont seem to mean much now.

lots of guidelines and what not and now its like the wild west, anything goes, people even connecting modems and turning of the upstream power back off

In reply to a post by RobertoS:

If you think BT SIN's don't say what happens in reality, then send your evidence to Ofcom. They would be very interested, and so would all CPs.

You are talking about the specifications upon which six or seven-figure investments are made by CPs.
_{Cue rant about Ofcom being pathetic and toothless.}

Ofcom are alll bark and no bite that has been fact since they where created just a waste of tax payers money a quango, they create rules for SP's to follow, and then do nothing when SP's ignore them,
Then their melding with the MAC system how is this any real benefit to EU's ? they tell BT OR and BTW to reduce their prices , don't fail to also make SP's pass on these savings to EU's yes very helpful is the useless quango Ofcom

I still can recall the days of Tiscali and Toucan ISP's who frequently flouted ofcom's rules they even ignored the MAC code regulations, what did ofcom do there?

Edited by tommy45 (Mon 13-Jul-15 17:18:25)

In reply to a post by ian007jen:

You could probably just issue the single command

xdslcmd start --up

When i want to re-sync my (ADSL) connection I telnet in to my broadcom based router and issue the command

xdslcmd start --up --snr 90

This means I connect with a 5 dB SNRM at the lower end of an IP Profile.

I half-remembered this post Ian, and as I wanted to find out if upstream G.INP had been re-enabled on my cabinet I tried xdslcmd configure --up, which worked with Retrain reason 0. A few minutes later realised my OP was using connection --up so tried that without the -- down and that worked as well, with Retrain reason 2000.

I now see you suggested start --up and I'm sure that would work as well, but not trying now as currently it is shifting downstream speed to upstream on re-sync's.

Just for info, I used to alter the SNRM in a similar way on ADSLx, using configure, but on the HG612 it completely screws things up. Also SIN498 specifically says we shouldn't do it.

I think the Fritz box does it OK.

The main question I have to ask is, why would you want to resync? Isn't any DLM alterations supposed to be done overnight if needed - what would a forced resync do other than (allegedly and potentially) trigger DLM?

To make sure the modem stays in sync with the caesium clock .

Is that really worth it?

Of course - got to make sure it doesn't get upset by any of these escaping.

Trolling my cluelessness about the use of this I see

No. I don't think you are trolling.

And in fact my re-sync'ing to see if the latest MSAN update had been applied was in fact probably pointless, as suggested.

However there can be reasons to re-sync the modem, for instance if it has sync'ed low during a thunderstorm that has well and truly moved many miles away or ceased. But when the question comes out of the blue that and any other other examples - (none of which come to mind now for instance!) it somehow hard to think why you do it.

Sometimes you just have an intractable problem, where doing things on the computer or router don't solve it, but a re-sync does. You normally try all the other things first, unless it's a recurrent one and you know re-sync'ing is the thing to do.

All the caesium clock stuff was intended light-heartedly. Though I found out about that pentaquark yesterday and was fascinated. One theory is it contains 4 quarks and an anti-quark (effectively anti-matter).