Re: Softether Download

0 views

Skip to first unread message

Message has been deleted

Toccara Delacerda

unread,

Jul 15, 2024, 4:59:40 AM7/15/24

to derslitope

The question is pretty much in the title. I'm currently running Apache with a https cert, and softether on two different servers currently. But due to cost cutting measures, I will be installing both programs on one server. Is there any way that I can run Softether and Apache on the same server, with both programs using port 443? The server is running Ubuntu 16.04.

softether download

Download File https://urlin.us/2yS7VO

Hi, I have successfully running SoftEther VPN server(version 4) on OpenWrt 22.03, and I have VPN client successfully connected to the server. This is mainly by the help of SoftEther user forum thread L2TP vpn client report 720 Error when try to connect SoftEther VPN on OpenWrt and our forum post: How to tweak the firewall of OpenWrt 22.03 to support Softether VPN server.

I was using the TAP device before(Bridge with New TAP Device), but I'm not sure how to "Attach the newly created TAP device to the "br-lan", in my OpenWrt Web configure interface, I don't see the choice options in your last image shot as you posted, so I do not know how to select the "tap_softether" to the br-lan's "Bridge ports".

This this changes(I have also created a TAP device in the SoftEther management tool GUI), and I can correctly got the VPN client has the same IP address subnet(192.168.2.x) as my LAN PCs. That's Great! Now, I see that I can access the VPN client directly from the LAN PC.

I have see that one of my vpn client was assigned IP address 192.168.2.172, and the other vpn client got 192.168.2.163. Which is depends on who connect first. My question is: is it possible to fix the IP address of the assigned vpn client? I mean I would like the PC-A always got a fixed assigned VPN address. But it looks like the mac address was not transferred by the internet, how can I do that under SoftEther VPN server running under OpenWrt?

I am trying to use softethervpn-client-manager from the aur to connect my laptop to a softether vpn server I have running on a Windows machine. I have searched for days trying to find a solution without success, although I have made some progress: I am able to use Windows to connect as a client quite successfully. So I exported its client config and imported it into Arch to use. When I try connecting, it shows as being connected in the client manager and on the server. . . but it's not working.

Here's the problem: when I connect, the server says it's connected with an ip of 192.168.30.101, but when you use the client manager interface to look at the vpn adapter, its IP address, subnet mask, gateway, dhcp server are all zero.

I am not at all sure what's wrong here. I've tried assigning an address to the vpn
adapter by using dhclient. The address lands in the right range 192.168.30.xxx, but it's not the same address as the server thinks it should be, and it doens't work. It ought to be set by the dhcp server on the vpn server. . .

I've tried to use nmcli to create a connection using the vpn adapter, but I'm not sure if I should continue with it as a tun type adapter, or try to change it to a vpn or ethernet type of connection. If I try to use it as a tun type adapter and set it to auto, well, I've had no luck there.

I am well out of my comfort zone here and have pretty limited knowledge of what I'm doing networking wise, so I'm really not sure how to proceed at this point. Until the virtual vpn adapter has an address, that the client side sees, I'm pretty stuck.

After even more messing around, I have edited this post to improve reliability and performance. I also have updated the script to start the vpn service, connect to the client service, and connect to the server.

I resolved the issues I was having when using dhclient to assign an ip address to the vpn virtual adapter. My vpn client virtual adapter is named vpn_vpn. I found that modifying the routing table right right after connecting to the vpn server doesn't work as well as first creating a new route to the vpn server ip via the active network adapter gateway before using dhclient to get an ip address for the virtual vpn adapter. Formerly it was necessary to create a new default route, but by adding a route to the server before calling dhclient, the default routes are created automatically.

I created a simple script to automate this. It determines the hardware adapter on the fly, so it can be used when I connect using my cellphone adapter or when using wifi. I also show the script to disconnect and stop the vpn service.

Now that I've had a chance to test it more exhaustively, I have discovered one issue that may or may not arise, depending upon whether the local router gateway is the same as the vpn server's router gateway. In other words, if your local network segment is the same as your vpn server segment, there can be problems accessing the server shares or other machines within the vpn lan. This is easily solved, if you only have one or two machines you want to access on the vpn lan. Just add another route after the script runs; you will need to know the gateway of the vpn server. For example, if the local subnet is 192.168.0.0/24 and the vpn server lan segment is the same, your virtual vpn server adapter gateway is 192.168.40.1, your vpn server is at 192.168.0.100, and you want to access its shares, just add the following after the script runs: