PacketReader thread name is misleading if used in parallel

[JozefDropco]

Hi,
in our setup where the SmbClient is created per processing unit could cause PacketReader thread to be named the same as other thread belonging to different processing unit. Its impossible to distinguish between them because the name of the Thread is only the hostname.

I would like to add at least the original thread name which created the PacketReader or most handy would be to add SmbClient an artificial ID like UUID and link it together within code