Secondly, if the RUT is acting as a server, you will need to add a push option in your OpenVPN configurations. Specifically, you will need to push a route to RUTs LAN network to your OpenVPN client. For example:
route 192.168.1.0 255.255.255.0
If your RUT is acting as a client, you will need to add a route to your RUT device on your OpenVPN server. If this is a case, please take a look at these forum posts here and here.
I’ve just solved my problem.
The route was not correct.
If I want to authorise the OpenVPN connection to a single address on the lan network of the RUT, is that possible?
Example: RUT lan 10.114.1.0 /24
I only want to authorise ad 10.114.1.50, is that possible?
You can edit the OpenVPN firewall zone, remove LAN from ‘allow forward to destination zones’ so that the OpenVPN traffic is not allowed to LAN. Then, create a traffic rule where you allow traffic from OpenVPN zone to a single IP address in LAN specifically. This way, OpenVPN client will only be able to reach that single IP address in LAN.
For better understanding of traffic rules and how to configure them, I recommend reading our wiki article here.
I can ping point 6 but also point 1.
I manage to connect to the RUT in https via point 1, but it refuses my password.
Do you have any explanations?
Best regards
Do you have any other devices in LAN of your RUT? The firewall rule looks fine. The thing is that this rule allows access to 10.114.1.6 device in LAN. If you have removed LAN from the OpenVPN zone, then with this rule only the 10.114.1.6 device should be reachable. However, the RUT itself will still be reachable (I assume thats the 10.114.1.1 device you are refering to). If you want to restrict access to RUT as well, you need to create an additional, similar rule where the destination zone is Device (input). LAN zone is for LAN devices, while Device (input) is for the device itself.