OVPN Server tap bridged on Windows Clients
Posted: Tue Mar 06, 2018 4:29 pm
Hi all,
I'm trying to make my way around the inability to push routes from ovpn server on mt. One idea that came to my mind was to implement tap interfaces, and vía dhcp options set the required routes trough the vpn. Works flawlessly on mac-linux clients, but as always Windows has it's own picture and fails with message: There is a clash between the --ifconfig local address and the internal DHCP server address -- both are set to 0.0.0.0
Problem dissapears if you set IPs on secrets, but also loses dhcp capabilities, ergo dhcp options.
Is there anyone around who has experienced mt's ovpn tap server with Windows clients and effectively got dhcp ip addresses?
TIA
I'm trying to make my way around the inability to push routes from ovpn server on mt. One idea that came to my mind was to implement tap interfaces, and vía dhcp options set the required routes trough the vpn. Works flawlessly on mac-linux clients, but as always Windows has it's own picture and fails with message: There is a clash between the --ifconfig local address and the internal DHCP server address -- both are set to 0.0.0.0
Problem dissapears if you set IPs on secrets, but also loses dhcp capabilities, ergo dhcp options.
Is there anyone around who has experienced mt's ovpn tap server with Windows clients and effectively got dhcp ip addresses?
TIA