Hello,
although eM Client works with Kerio partially, there are limitations such as non-displayed shared folders, inability to use multiple contact folders and few more. We have been trying to cooperate with Kerio on making this work (all these issue are rather on the server side). However, Kerio officially supports only Apple clients and does not plan to change this policy soon, hence they are not willing to cooperate on these issues.
Installed Kerio control vpn client from AUR and everythink went fine during the install. Archlinux system is very clean, it's been installed for a couple of days only. kvnet interface goes up with no problem :
Short: Packets from remote dropped by kernel because wrong MAC-address.
Long: On each login vpn client create new random MAC-address and say it to server. But client don't set that mac to kvnet interface. And if you look at packets incoming from remote, you can see that header contain MAC-address from debug.log. And, because destination and iface addresses not equal, it lead to dropped packets.
I found another "solution" for me, which I do not understand. When I run the VPN client from the command line with strace, it works fine without any further work. It does set the mac address on the interface correctly. Running it from the command line without strace does not have this effect.
We are having an issue where clients behind a Kerio Control firewall are unable to communicate with our Connectwise Control server - it sits on "negotiating". We cannot connect to them, and if we go onsite and log into the web interface, we cannot connect to other computers.