Roquefort
Hi guys,
I've been implementing OpenVPN Access Server VHD in Hyper-V in my network, and after about two weeks, it's going really well. I also have it upgraded to Ubuntu 13 and Server 2.0.1. I use LDAP logins with auto-connecting desktop profiles.
My problem is that the server won't route properly in multi-daemon mode. If ONLY TCP (443) is enabled, or ONLY UDP (1194) is enabled, then things work just fine. But if both are enabled, the problems start. Specifically my DHCP clients (assigned to 10.200.10.0/24) cannot speak with anything on the internal network (10.200.11.0/24). Except for the Access Server (10.200.11.46). They can hit that. The firewall does not appear to even log anything... like the traffic isn't even leaving the access server.
My network is pretty simple:
1) The Access Server sits in a virtual appliance behind the firewall (10.200.11.1), at IP 10.200.11.46.
2) The firewall has just a single rule in place, to route anything going to 10.200.10.0/24 to 10.200.11.46. I had to do this just to get TCP or UDP to work on their own.
Any idea what may be going on? It's not a game-breaking problem, but I'd like to be able to utilize UDP (currently this problem forces me to stick with TCP).
Any help would be appreciated. I'm totally green when it comes to linux/OpenVPN, but I haven't really had any trouble getting all of the bells and whistles set up.
