Contents.Feature descriptionOpenVPN 2.1 has a relatively recent feature that allows a TAP-basedOpenVPN session to be established where the client gets its IP addressassignment and other attributes from the server-side DHCP server.The feature is enabled by the 'route-gateway dhcp' directive on the client.It's a pretty cool feature because it allows you to set up a TAP-basedVPN server without configuring IP addresses, routes, etc. Because youcan simply leverage on the existing server-side DHCP serverconfiguration. When a client connects to the VPN, it gets an IP addressassignment just as if it were physically 'plugged into' the server-side LAN.The problem is that 'route-gateway dhcp' only works on platforms wherethe TAP driver negotiates a DHCP client handshake. Currently, onlyWindows support this out-of-the-box (Windows supports it not because ofany special code in the Windows TAP driver, but because the Windows DHCPclient automatically binds to TAP adapter instances when they transitionto the 'up' state).I'm hoping that we can make 'route-gateway dhcp' work on Unix platformsas well. I'm thinking there are two possible ways we could do this:(1) Simple method: Trigger a DHCP client bind on TAP interfaces whenthey are instantiated. Waves ssl 4000 collection mac free download.

If you (unlike the OP) have access to the OpenVPN server configuration, you can add this option in your OpenVPN server.conf if you want to push for all the clients: push 'dhcp-option DNS 8.8.8.8' You can change the 8.8.8.8 to your desired DNS.