On Fri, Sep 14, 2018 at 07:04:45AM +0000, Anders Selhammer wrote: > Yes, that would be great also but it will not solve the clockIdentity problem > since the > Identity will stay the same until next restart. And it the port setup is > different, the > identity will change. (and the connented slaves for example will have to > "change" gm > if stack is acting as gm) .
What is wrong with keeping the clockIdentity the same? Isn't that the whole point to this exercise? This is what I propose: - stack starts up with clockIdentity as we have it now - you add a port via custom management message; clockIdentity same - you remove a port via custom management message; clockIdentity same See? Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
