I found the administration GUI from the Softether project very easy. That’s because SoftetherVPN uses the HTTP protocol to masquerade its VPN payload.Īnd the Raspberry-Pi with your Diet-Pi and your SoftetherVPN is online. I was finally able to connect from behind an “Industrial-Grade” firewall. Thanks to your Diet-Pi distribution, and your SoftetherVPN installer, That’s because these firewalls not only block every port, except 80 and 443,īut they also inspect the IP datagram to see if the protocol is in fact HTTP.Īnd OpenVPN is not using HTTP, so: no client-connect… I have found it to be impossible from behind a more strict firewall,Įven if the OpenVPN server was listening on port 443. While OpenVPN clients could easily connect to the OpenVPN server from behind “SOHO” routers, Here is the DietPi source code for installing SoftEther VPN server, before it was removed.įor several years I have run OpenVPN servers in bridge mode on several Linux distros. You can however install SoftEther VPN server manually on any DietPi system. Its over complicated and we can’t automate that side for the user. The other reason is due to its end-user setup with the client software. Implementing and supporting Softether VPN is too time consuming and I have limited time I can devote to DietPi as it is. Unfortunately, SoftEther VPN will not be returning to DietPi for the moment. Please-please-please consider restoring it! SoftEther is the only VPN that works behind NAT, and its support was the very reason I migrated to DietPI. Could you please return SoftEther VPN option? OpenVPN is slow and ugly, moreover that it is impossible to use without forwarded ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |