brendan i have openvpn working with the server-bridge nogw directive set, and the dhcp server is handing out the settings to the client. i am not giving out a default gateway in my dhcp scope for openvpn clients, because i read that that will remove the original default gateway of the client and break things. i am thinking that i should be using push "redirect-gateway def1" in addition to the server-bridge nogw. does this make sense? will the client be able to operate in this fashion? also, what does that do for routing? when the above is put into place, assuming it will work, does the openvpn server become the router for the clients? i have a router on the segment that is dedicated to the openvpn server and clients already. can i point the clients at that, instead of the openvpn server? i do have ip forwarding turned on, on the openvpn server just in case it is needed, anyway.
maikcat simply add this to your server config push "route 0.0.0.0 255.255.255.255 net_gateway" Michael.
brendan from what it looks like, that adds a static host route for every IP, pointed through the tunnel at the net_gateway IP I would provide. is that correct? this does seem to accomplish what I am looking for (disable split tunneling), but how does that affect things like DHCP for the physical hardware device? since the 0.0.0.0/32 route is pointing down the tunnel, would broadcast traffic be outside the tunnel, allowing DHCP to continue working?
