29-12-2022 10:52 PM
Hello,
I have minor understanding of:
'CWMP: HDM socket opened successfully'.
My technical log is flooded with this, logs are minutes apart at different times of the day but usually notice more in the evenings, when I'm watching the box! Is it possible the 'click' noise from the router is associated with this 'CWMP: HDM socket opened successfully'? It seems to coincide.
Should I be reporting the constant 'CWMP: HDM socket opened successfully' to EE? Or, is it simply 'one of those things', possibly due to non-fibre rural location, for one?
Thanks.
29-12-2022 11:20 PM - edited 29-12-2022 11:35 PM
More than likely nothing to worry about, just stop looking at router logs.
Are you having any problems, or are you just curious?
29-12-2022 11:32 PM - edited 29-12-2022 11:46 PM
@Dookss : Which router are you using?
@Mustrum : Sorry! You know it's easy to pick the wrong @ dropdown.
29-12-2022 11:33 PM
I'm curious as to what 'CWMP: HDM socket opened successfully' is/does, most definitely! Why am I seeing this in the event log so much?
The problems are minor at present, known much worse. A clicking router is enough to make me flinch night after night! First World Problems.
29-12-2022 11:43 PM
@XRaySpeX why are you asking what router I am using ?
@Dookss The CWMP entries are just EE router management connections making sure your router is up to date.
The HDM socket entries are local connections.
Either way, not the first focus to look at if you have issues, better to say what problems, if any you are having.
30-12-2022 12:25 AM - edited 30-12-2022 12:29 AM
OK, it's an EE Smart Hub. The last time I used 1 these msgs were frequent. They are part of the TR-069 protocol for ISPs' remote management and provisioning of end-users' routers. TR-069 uses the CPE WAN Management Protocol (CWMP). They are just EE checking up on their settings & rarely updating them.
Look up TR-069 on Wikipedia if you like.
Otherwise you'll get eyestrain perusing router logs. There's only 2 important words in them, Down & Up 😉 !
06-09-2023 03:24 PM
This is the worst reply ever...