Answer the question
In order to leave comments, you need to log in
How do I configure the OpenVPN server to issue a white IP for each client?
The situation is the following. There is a server with Debian OS and OpenVPN installed on it. This server has two network interfaces. One looks to the local network (10.x.x.x), and the other to the Internet. The local network also has a router for clients of this local network with a DHCP server on board. The OpenVPN server is currently configured in LAN bridge mode.
There is also a remote server, similarly having two network interfaces (local network and Internet). This server is bridging our local network. Thus, clients of a remote network receive IP addresses and the Internet from a router from our local network.
Everything works great. But suddenly we needed to connect separate remote clients to the local network, which should also receive IP addresses and the Internet from the router.
That is, the problem is that when a client connects to the OpenVPN server, an interface with an IP address issued by the OpenVPN server is raised. But there is no access to our local network after that. Apparently it is necessary to configure routes explicitly. What I just did not write in the configuration files of the server and client, but could not solve this problem. It seems that Windows, Linux and Android clients simply ignore these settings.
How to be in that case?
PS Is it possible to configure OpenVPN so that clients receive an IP address not from OpenVPN itself, but from an external DHCP server?
Answer the question
In order to leave comments, you need to log in
I agree that you need additional routes.
> It seems that Windows, Linux and Android clients simply ignore these settings.
Look at the client launch logs, when the connection is established, everything is written nowhere in more detail. For example, it is immediately clear that routes will not be added if you run the OpenVPN client on Windows without elevation. It is possible that the situation is similar on other platforms. Look at the routing tables after starting the client and establishing a connection. If the expected routes are there, then do traces.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question