Closed mythosking closed 1 year ago
Your bug is somehow missing the describtion of the problem that you experience.
Your bug is somehow missing the describtion of the problem that you experience.
I have modified the issue and submitted a detailed log.
You are creating a routing loop. You are connecting to 10.10.8.60 but also assign a 10.10.8.100/24 to your client. This is a configuration error more than anything else.
You are creating a routing loop. You are connecting to 10.10.8.60 but also assign a 10.10.8.100/24 to your client. This is a configuration error more than anything else.
Hello, I still have many questions. Firstly, is it allowed to configure DHCP pool and serve in the same network segment? Just ensure that the DHCP pool does not conflict with the IP of the existing terminal, right? Secondly, using the configuration of the client in question, on Win11, it was possible to successfully connect to the server without the same error. Is there any mechanical difference between Win11 and Centos8?
This is a bug tracker to report bugs and problems in OpenVPN to developers. This not the right place to explain routing and network setup problems. Connecting to a server from the same network to the server itself that serves the same network is always tricky and problematic and most times compeletly pointless since you are already in there. You can look into thing like redirect-private
etc. but ultimatively it is better to tried to avoid this situation. And yes differrent platforms can exhibit different behaviour.
Describe the bug client run command: openvpn --config /etc/openvpn/client/client.ovpn
Client encountered an error: 2023-07-14 15:54:22 read UDPv4 [EHOSTUNREACH]: No route to host (fd=3,code=113)
But for the same client configuration, using OpenVPN 2.6.4 [git: v2.6.4/b4f749f14a8edc75] under Win11 to connect to the same server successfully
The detailed logs of the client are as follows:
To Reproduce VPN server:10.10.8.60 VPN client:10.8.36.3
Expected behavior The phenomenon of Centos client and Windows client consistently being able to successfully connect to the server.
Version information (please complete the following information): VPN server:
VPN client:
Additional context VPN server.conf
VPN client.ovpn