IP Profile Stuck?
FIXED
Update following Hub 2 direct dsl connection trial.
Over a few days I kept the Hub2 connected direct via dsl to the master socket, monitoring the IP Profile, until DLM dropped the SNRM to 5dB. At this point I swapped back to connecting through the Hub2 WAN port/HG612, updated table below;
What this has shown is that when the Hub2 is connected direct via the dsl port, the IP profile updates whenever there is a DLM re-sync, but when connected through the WAN port/HG612, it doesn’t. What I discovered however, is that a quick reboot (through the Hub2’s Restart tab), but leaving the HG612/VDSL up, correctly updates the IP Profile. It also updates by a quick Hub2 “Broadband Disconnect” and connect cycle.
So the question is why is there an IP Profile update issue with the Hub2/HG612 setup, when it works fine with the Hub One/HG612? I will avoid getting into possible technical reasoning as I’m not familiar enough with the intricacies of PPP/DSLAM/DLM/bRAS/IP Profile etc., all I can do is show my findings and work around.
I guess that the Hub 2 was only intended, or tested, with direct dsl connections or via the WAN on FTTP setups? It would be good though if this issue could be investigated and fixed, but probably well down the PN priority list, if added to it at all!?
I will attach the Hub2 Technical Log to the fault ticket as I can see that when the dsl port connection is lost, PPP detects it and re-establishes PPP again when dsl is restored. However, there is no PPP activity if the vdsl connection through WAN is lost. This suggests that PPP plays a part in the overall IP Profile update?
So now I know all this, going forward I can stick with the Hub2 / HG612, knowing I just need to restart/reconnect the Hub2 if the IP Profile is not updated. Now I’m nearly back on 3dB SNRM though, everything should settle back down to infrequent DLM interest.
Thanks for everyone’s support during this and I specifically thank and ask @Gandalf if this feedback could be reviewed internally. Also, to the Openreach engineer who originally questioned the Hub2/HG612 setup. At least there is a workaround if anyone else ends up in this space.
One niggle I do have now is that during the engineers visit I was "upgraded" from a fully working NTE5a mk1 faceplate to the new NTE5c mk4. This seems to be a routine upgrade on home visits now? After a couple of days though I heard crackling on voice calls and a dive in terms of broadband speed, with DLM taking steps to resolve like it does. We have no extension wiring and just a telephone plugged directly into the faceplate, other than the modem. I noticed that it took only the slightest of touches on the mk4 faceplate and the phone crackled, but is fine if I plug the phone direct into the test socket. So as seems to be documented in other forum posts, I'm now suffering from a poor connection between the NTE5C back plate and the mk4 faceplate. I have cleaned the contacts with isopropyl alcohol and slightly loosened the back plate fixing screws. Fingers crossed, this has now resolved the problem.
Thanks for the feedback!
I’ve left the office now and likely won’t be back until next week, but reading what you’ve said, it’s interesting behaviours and I’m certainly intrigued.
I agree though in that I suspect it may be hard to find a definitive answer or solution as the Hub Two likely isn’t designed to work with another VDSL modem, but our resident hardware guru @bobpullen may be able to shed some light and have some thoughts possibly…
The poor connection with the NTE5C shouldn’t happen and as it was only newly fitted, I’d be happy to call an engineer back out to look at this for you, but maybe let’s see if what you’ve done has sorted the problem.
Cheers
