Package Details: kerio-control-vpnclient

Git Clone URL: (read-only, click to copy)
Package Base: kerio-control-vpnclient
Description: Kerio Control VPN client for corporate networks.
Upstream URL:
Licenses: custom:eula
Submitter: None
Maintainer: muflone
Last Packager: muflone
Votes: 21
Popularity: 0.001211
First Submitted: 2012-09-04 09:35 (UTC)
Last Updated: 2022-07-18 22:14 (UTC)

Pinned Comments

muflone commented on 2019-08-31 11:25 (UTC)

Package updated to

Warning for Kerio Control server 9.2.6. The latest compatible VPN client version is Since 9.2.8 the VPN client is incompatible and requires updated Kerio Control server. In the cause you are a Kerio Control 9.2.6 user please switch to the kerio-control-vpnclient-9.2.7

Latest Comments

1 2 3 4 5 Next › Last »

aminvakil commented on 2022-07-03 08:48 (UTC)

libxcrypt-compat should be added to depends

Otherwise it fails with:

/usr/lib/kerio-control-vpnclient/kvpncsvc: error while loading shared libraries: cannot open shared object file: No such file or directory

krafZLorG commented on 2021-03-07 20:22 (UTC) (edited on 2021-03-09 18:09 (UTC) by krafZLorG)

You can create /usr/local/bin/ script:


sleep 2
ip link set dev kvnet address "$(awk '/VPN driver opened/ {print $NF}' /var/lib/kerio-control-vpn/logs/debug.log | tail -n1 | sed 's/-/:/g')"
resolvectl -i kvnet dns kvnet x.x.x.x
resolvectl -i kvnet domain kvnet

then run sudo systemctl edit kerio-kvc.service and write


jeleniste commented on 2021-01-03 13:02 (UTC) (edited on 2021-01-03 13:02 (UTC) by jeleniste)

@krafZLorG Thanks. Works for me well.

sudo tcpdump -t -i kvnet -e

quangdang commented on 2021-01-02 19:01 (UTC)

@Zvnrt Thank you. I managed to follow your steps and successfully connect to the server. But I still have some problems. I can connect to a remote DB with IP address but not with domain. Also apply with website. Maybe there are some problem with DNS

Zvnrt commented on 2021-01-02 17:29 (UTC)

@quangdang I'll try to explain as best as i can, since english is not my first language.

Basically once you have kvpnc configured and running, but without reaching your destination network, open your terminal and ping one of your devices in the network you can't reach (like a printer, or a switch, or your gateway, as long as you know the ip address), obviously it wont answer, but leave it running for now, you open wireshark and start to capture in the kvnet internet interface, then look for a package that will have the device you are pinging in the source, and will say Echo (ping) reply" in info, stop the capture, open that package just double clicking on it.

Then you will see something that will say "Dst:" and some letters and numbers with dots, something like 11:22:33:44:55:66, that's the mac address we are looking for, copy that

Then, using the command @krafZLorG shared (ip link set dev kvnet address XX: XX: XX: XX: XX: XX) you change those XX with the mac address that you copied from the package, then run that command and voila! It will work.

So far my downside is that everytime i restart, i have to do this again since kvpnc interface's mac address changes everytime, i'm looking for a way to set it with an specific mac address so it won't change every single time, but at least it works now. Hope i was of some help.

quangdang commented on 2021-01-02 16:18 (UTC)

@Zvnrt Could you help me with step by step to make this work?

Zvnrt commented on 2021-01-01 23:50 (UTC)

@krafZLorG It worked! Thank you so much!

krafZLorG commented on 2020-12-08 18:19 (UTC)

If you run wireshark or tcpdump on the kvnet interface, you can see the destination mac address in the packets from the server. It is not the same as mac on the interface. If you change the address on the interface (ip link set dev kvnet address XX: XX: XX: XX: XX: XX), then everything will start working.

anatolyb commented on 2020-11-28 21:44 (UTC)

I have the same problem with no incoming packets. And it's definitely because of a system setting, but which one I don't know yet. I have at the same machine on different drives up-to-date arch systems. The old one I've installed many years ago, and the new one a couple of weeks ago. The same kerio-control-vpnclient package works fine on the old system. All the differences I see for the moment is that the old configuration leaks IPv6. I've tried to disable IPv6 on the fresh arch lead to no luck. Can anybody point me to see something else?

jeleniste commented on 2020-11-26 20:21 (UTC)

Disabled zeroconf record probably isn`t related to reasons why is not possible to etablish ssh connection, ping or whatever through tunnel.

Unable to send IP packet, xxxxxxxxx -> zeroconf disabled is - server used by network manager to check connection.