SoftEther VPN User Forum

Deploying SE-VPN SERVER in AWS, disabling NAT and DHCP, creating a new local bridge associated with the only network card in EC2, connecting with a client, always displaying the acquisition of DHCP, and finally obtaining the IP of 169.254.61.43. Normally, the intranet IP segment of AWS EC2 should be obtained. If this problem cannot be solved, is it impossible to connect LAN to LAN? May I ask what the problem is? How to solve it?

fork wrote: ↑

Wed Apr 05, 2023 7:12 am

is it impossible to connect LAN to LAN?

Possible https://www.softether.org/4-docs/1-manu ... Routing%29

AWS EC2 public IP, private IP (172.17. x.x), establish a local localbridge, VPN dial in, assign 169.254.61.43 IP addresses to clients, and NAT is closed. Normally, the client should be assigned a 172.17. x.x IP. I don't know whether I understand it correctly or not, but what happened to another IP. The promiscuous mode is open, and doesn't it support AWS?

Look, AWS will not serve DHCP to your VPN clients and 169.254.x.x is Windows "Automatic Private IP Addressing" (APIPA) when no DHCP exists.

If LAN-to-LAN is really what you want, then L3 is the only option https://www.softether.org/4-docs/1-manu ... Routing%29

Otherwise, what's your objective?

The IP assigned by the local bridge is incorrect. I am unable to access the internet through AWS VPN SERVER

fork wrote: ↑

Thu Apr 06, 2023 2:32 am

The IP assigned by the local bridge is incorrect. I am unable to access the internet through AWS VPN SERVER

So it's not about LAN-to-LAN at all and you want us to second-guess your objectives. I'll do it once only. Here it goes:

• do not bridge anything

• enable SecureNAT with all defaults

Bye.