Absolutely, you can do this. However, during initialization, WireSock identifies the instances of the virtual network adapter, selects the first one to be used for the routing purposes, and renames the selected connection to “WireSock”. This is done for your convenience, allowing you to easily recognize the network adapter currently utilized by the client. If you have any suggestions for improvement, I would be happy to consider them.
I’m sorry, but it does not seem reasonable to rename the network interface from ‘Wiresock’ to ‘Example’. Instead, it could be more sensible to name it after the configuration file, which would provide better context and clarity.
At the moment, the functionality to name the virtual network adapter based on the configuration file does not exist. However, I acknowledge the value of this feature and will consider implementing it in the upcoming update.