Well, probably I solved the routing issue in a very simple way. This the schema I adapted to my scope:
+-------------------------+
(public IP)| |
{INTERNET}=============={ Router |
| |
| LAN switch |
+------------+------------+
| (192.168.10.1)
|
| +-----------------------+
| | |
| | OpenVPN | eth0: 192.168.10.10/24
+--------------{eth0 server | tun0: 10.0.0.1/24
| | |
| | {tun0} |
| +-----------------------+
|
+--------+-----------+
| |
| Other LAN clients |
| |
| 192.168.10.0/24 |
| (internal net) |
+--------------------+
And this is the routing added to the server through Routing and Remote access interface:
Now, from VPN client, connected from external network, I'm able to ping and reach only the IP: 192.168.10.10. That's enough for now, to reach other machines I have to add anoter route. Or, find I way to add the whole subnet 192.168.10.0/24
Thank you again to all users who followed me in this journey! 😃
NOW... I have to solve 2 other things.
1) Start OpenVPN server listening when Windows starts
2) Find a way to solve or find a workaround for the issue where OVPN server is not able to assign the correct IP address to its interface (for now manually solved by issue ipconfig /renew)
