TiTex wroteHe was saying above that you were using "TAP" adapter which forwards layer 2 broadcasts (DHCP requests) between your vpn clients.
So you should definitely use TUN adapter for routing, that alone should stop the broadcasts from your network to your vpn clients network, if not ... then something else is going on.
Using 'TUN' adapter , Allocate from DHCP option should also be disabled, i have no idea how did it work if it was already with TUN
Thank you for your answer mate 🙂
Well, we sort of got the VPN to work with TUN and "Allocate from DHCP" to Disabled.
However..
Now the VPN Server pushes 10.0.13.X to our routers - and while we manage to ping the media server (a Windows 2012R2 w/Kodi Media Server) - we cant see it on our own local networks. While i can ping its original LAN adress (10.0.10.151) - i cant find it in my friends routers even as after we have added multiple IP's to the ethernet adapter.
The servers main adress is 10.0.10.151 (Static). On my friends networks, it should be 10.0.11.151, and 10.0.12.151 - as we have mapped these adresses in the ethernet adapter in Windows Server. Subnet all over is 255.255.255.0
This solution worked perfectly when running with TAP. And we would like to make this work with TUN also, as this has removed the problems with DHCP servers forcing and pushing ip's all over the place.
Is there any way that i can get the server to be found by the connected routers (OpenVPN Clients) on their respective LAN's? Would a solution be to connect to the server via the OpenVPN software directly on the server?
I appreciate all the feedback i get from you guys. VPN is fun, and we learn something new every day 🙂