Package Details: kerio-control-vpnclient 9.3.6.5808-1

Git Clone URL: https://aur.archlinux.org/kerio-control-vpnclient.git (read-only, click to copy)
Package Base: kerio-control-vpnclient
Description: Kerio Control VPN client for corporate networks.
Upstream URL: http://www.kerio.com/control
Licenses: custom:eula
Submitter: None
Maintainer: Muflone
Last Packager: Muflone
Votes: 21
Popularity: 0.000000
First Submitted: 2012-09-04 09:35 (UTC)
Last Updated: 2023-09-10 15:05 (UTC)

Pinned Comments

Muflone commented on 2023-09-10 15:07 (UTC)

Thanks to this PR https://github.com/muflone/pkgbuilds/pull/25 the VPN client should automatically add the missing route

Please test it and let me know

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

Package updated to 9.3.0.3273

Warning for Kerio Control server 9.2.6. The latest compatible VPN client version is 9.2.7.2921. 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

« First ‹ Previous 1 2 3 4 5 Next › Last »

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 -> 138.201.81.199: zeroconf disabled

138.201.81.199 is apollo.archlinux.org - server used by network manager to check connection.

quangdang commented on 2020-11-09 17:35 (UTC)

Anyone resolve error: zeroconf disabled? I try to enable avahi-daemon but no luck

0wner commented on 2020-07-16 20:21 (UTC) (edited on 2020-07-16 20:30 (UTC) by 0wner)

I have a similar problem, but maybe a problem with KDE Plasma settings?

ifconfig
kvnet: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1400
        inet 192.168.150.144  netmask 255.255.255.0  broadcast 192.168.150.255
        inet6 fe80::1813:96ff:fe21:7621  prefixlen 64  scopeid 0x20<link>
        ether 1a:13:96:21:76:21  txqueuelen 1000  (Ethernet)
        RX packets 29  bytes 2780 (2.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 149  bytes 16806 (16.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 448  bytes 34643 (33.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 448  bytes 34643 (33.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 28:c6:3f:a0:8b:ec  txqueuelen 1000  (Ethernet)
        RX packets 158077  bytes 107096826 (102.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 99153  bytes 22921745 (21.8 MiB)

bazted commented on 2020-06-29 02:51 (UTC)

@FlyingRissole @shinshilas I have managed to get rid of "zeroconf disabled" error by enabling and restart avahi-daemon.service. 

sudo systemctl enable avahi-daemon.service
sudo systemctl restart avahi-daemon.service

But still, the ping is failing with "Destination Host Unreachable". Can you please try if it works for you?

FlyingRissole commented on 2020-05-29 17:45 (UTC)

Hi, @shinshilas. Sorry, but I still couldn’t fix the issue.

shinshilas commented on 2020-05-22 09:13 (UTC)

Hello, I'm having an exact same issue. Tunnel seems to be established just fine, but I can't reach anything on Kerio network (Nothing pings back). I also get zeroconf error in debug.log (If it has something to do with the issue) @FlyingRissole did you manage to solve your issue?

Thanks for the package @Muflone!

FlyingRissole commented on 2019-12-02 20:55 (UTC)

Hi! When I start kvpnc, I'm get address from remote server, however can't ping anything. Nothing in error.log, but in debug.log kerio write that zeroconf is disabled so it can't send IP packet. Does anyone know how to solve a problem?

fla commented on 2019-10-24 19:10 (UTC) (edited on 2019-10-24 19:11 (UTC) by fla)

hi.server is on 9.3.0-3273 version. Nothing happened after entering the password using: sudo /usr/sbin/kvpnc configure https://forum.manjaro.org/uploads/default/optimized/3X/a/0/a019ea788788c2a559a64d5f57ca193211dde4a9_2_533x500.png

[fla@fla-pc ~]$ cat /var/log/kerio-kvc/error.log

[fla@fla-pc ~]$ sudo /usr/sbin/kvpnc start

[sudo] password for fla:

[fla@fla-pc ~]$ cat /var/log/kerio-kvc/error.log

[24/Oct/2019 22:34:38] libVPN: Connection to peer with specified certificate was denied(199)

[fla@fla-pc ~]$ sudo /usr/sbin/kvpnc stop

[fla@fla-pc ~]$ cat /var/log/kerio-kvc/error.log

[24/Oct/2019 22:34:38] libVPN: Connection to peer with specified certificate was denied(199)

[24/Oct/2019 22:35:08] libVPN: Connection to peer with specified certificate was denied(199)

[24/Oct/2019 22:35:39] libVPN: Connection to peer with specified certificate was denied(199)

[fla@fla-pc ~]$

manjaro-kde

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

Package updated to 9.3.0.3273

Warning for Kerio Control server 9.2.6. The latest compatible VPN client version is 9.2.7.2921. 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

« First ‹ Previous 1 2 3 4 5 Next › Last »