Consumer VPN use is widespread now. Eset 12 has many bugs related to VPN use, and the devs are negligent in fixing these bugs. In fact they're never fixed for years, and the impression is, Eset package is simply not tested by devs to be continuously used in consumer VPN environment. Eset also has no controls or interface features related to VPN use.
Examples are regular excessive lengthy Eset CPU and HDD load when switching VPN on and off. Also Eset Firewall failure to restore settings in Interactive Mode after firewall is switched off while VPN is enabled, and then switched on while VPN is disabled, or vice versa.
When reading Eset Help docs, the impression is Eset team purposely ignores the overwhelming trend on the consumer market during last years of using VPN, and devotes no technical or knowledge base articles to this very issue. Further, when contacting Eset support, they bring every fake reason to refuse investigating issues related to Eset failures to work properly in VPN environment.
In Help docs, Eset writers make it look that VPN is only used and of interest to enterprise market, and consumers should not ask any questions, or report any bugs related to Eset consumer products systematically failing for years to work properly with VPN.
Instead of saying "Thank you" for reporting never fixed bugs, Eset reps claim they can't find one's license, or its expired, or how it was obtained etc, trying to find a reason to refuse the bugs investigation.
Meanwhile, reporting bugs is users free gift to Eset, and the bugs must be fixed to benefit all paying and testing product customers, regardless who reported them and under what conditions. Most large companies have Bug trackers where anyone can enter bugs, it does NOT require any license proof at all, because bug reports are free donations to the very rich Eset company, allowing it to get ever richer.
On this forum, Eset reps also systematically ignore all user posts and threads related to VPN issues with Eset. This seems to be thick culture within Eset company of aggressively ignoring and denying existence of burgeoning consumer VPN market, thus making Eset less and less attractive to consumers despite cosmetic changes in slightly updated new product versions.
I know my post will be deleted, ignored again, or attacked by Eset paid guns, who also attacked them in the past, while Eset has no intention to change this ill long obsolete culture of ignoring consumer VPN market.
For me, full device names on LAN as broadcast show up on mouse hover or clicking the device, and they are editable. Company name isn't always part of the device name, one may change device names in their own GUI. 😄
Many Windows VPN clients don't have own Firewall or Kill Switch. A VPN Client usually creates a virtual network adapter or MiniPort, which is used by the client instead of physical Ethernet or WiFi adapter, thus creating a separate "Network Connection" in Eset Firewall. Please advice how to best configure Eset Firewall in a way, that all traffic from the PC would pass only through VPN, and any other traffic outside VPN is blocked by Eset Firewall?
Also, when VPN connection is temporarily interrupted, Eset Firewall should block all PC traffic on all adapters until the VPN connection is restored.
Can you also explain whether Eset does Real Time Protection on traffic passing through the VPN virtual adapter? If yes, is it done after the traffic has passed the adapter and was decrypted by VPN Client?