-
Notifications
You must be signed in to change notification settings - Fork 15
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
old router can't connected to l2tp #18
Comments
the latest version from softethervpn 5.02.5180 and your docker still 5.0.1.9674 isn't updated properly? |
found the answer Softether GitHub version remove sslv3 completely. back to RTM version |
sir can you confirm this commit 1534 fixed the problem. |
Hey @malikshi , I do not know it would be tagged soon, so what I have decided to not keep you waiting is to create an edge tag that would build the master branch of the |
Sorry for the trouble 🙏. |
Na it's no trouble, please do not say it like that. Can you please give a try to the If you can give me feedback whenever you are able to try it out, I can also update the VPN-client with the same methodology. |
i having problem with openvpn protocol udp.
i found the commit related to that option replaced by other command SoftEtherVPN/SoftEtherVPN#1130 i found this https://www.vpnusers.com/viewtopic.php?t=63325 have you ever try enable ipv6 on softether? |
Hey @malikshi , Unfortunately no, I have not touched the configuration of SoftEther except for Dockerizing it in almost 7 years. Where is this error coming from, is it from the client or the server? Could be related to the changes due to the WireGuard or something else? |
I think the edge version several command been replaced by new one like this one from SoftEtherVPN/SoftEtherVPN#1130 (comment) You can check the full information on vpncmd. |
Oh okay, but how about the config file can that be in any way migrated to the new version. Because we do not really use the |
can't use old cipher
DHE-RSA-AES256-SHA
cause the old router can't connect l2tp.then compare to RTM build 17 august with that cipher it's work fine. is it related to a different softether version?
The text was updated successfully, but these errors were encountered: