I was unable to replicate this. The client communication was not isolated.
Perhaps you updated the firmware with ‘keep settings’ enabled and it caused this issue? Usually, if there is a major differences between your current firmware version and the one that you are planning to update the device to, then it is recommended to disable the ‘keep settings’ option.
If you know a way to replicate this issue, please, let me know the process.