-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'ck-client -u' crashes with "NumConn": 4 #96
Comments
This issue is fixed in master, yay. Tho OpenVPN seems to be very slow or unable to connect perhaps due to this:
Edit: nvm, it's my shadowsocks session it was closing. |
It's the build from current master (2.1.3 UDP works fine), TCP mode works very well. |
@Klaaktu I'm trying to use wireguard through cloak do u mind sharing your steps/config on how to get it done. |
@Weeka89 I'm not using WireGuard atm so I don't remember everything, tho the steps are very similar to OpenVPN: |
WireGuard, server
****:000a & b are unoccupied IPv6 addresses from the server, prefix length 127 because DigitalOcean gives 16 IPs instead of /64 prefix. And their IPv6 is also non-routed thus the ndp-proxy in PostUp. WireGuard, client
192.168.1.2 is a second PC running ck-client and dnscrypt-proxy. nftables
sysctl.conf
|
Cloak, server
Cloak, client
Change to |
@Klaaktu Hey, how can u handle EDIT: When i remove UDP: true field from config, I got "error reading first packet: read error after connection is established" |
@gokaybiz |
Why we can't use on same pc? WHY? Here is some log from ck-client:
@cbeuw ? |
Does WireGuard say...?
I vaguely remember the explanation "localhost interface is not valid" somewhere. However the answer I get from search now is to set the |
It's an old issue but still happens on latest version (2.1.3).
Tested both OpenVPN (plain text mode) and WireGuard, only
"NumConn": 1
works in UDP mode.Client config:
Also is it ok to run OpenVPN in plain text mode to avoid double encryption?
Is "StreamTimeout" idle connection timeout? Can I make it super long to make it only close connection when I Ctrl+C the client like what Shadowsocks recently did?
The text was updated successfully, but these errors were encountered: