Been having some problems getting things working with a normal ubuntu build on a hyper-v server.

I've had no problems in the past running just about any openvpn setup you can imagine on a stand-alone server, but this is my first Hyper-V installation.

Basically my initial setup was a vm with a standard network adapter and setup the initramfs-tools/modules with hv_vmbus hv_storvsc hv_blkvsc and hv_netvsc. Everything appeared to be working fine, but I could never get the client to ping past the server. I tried with bridged setups and routed.. Read every single article I could find, and still could not get past the server from the client. I had no problems pinging any other system on the network from the server, I could ping across the tunnel also, just not past the vm from the client.

So I thought just for kicks to try out the legacy network adapter. Same exact setup minus the initramfs modules for hyper-v. It works OK, I can ping across the tunnel to all devices on the server lan, but its god awful slow. I'm getting pings of like 1000-3000ms most of the time. Even just pinging the host machine from the vm I'm getting 1000ms+ pings. Checked the dpkg logs also and there aren't even any entries from today, so it can't be that it's just bogged with updates at the moment...

Any direction would be incredibly appreciated.

Thanks

I suggest you for looking in the ubuntu's internal support for Netork Adapter from Hyper-V and how it is working with packets from another interface (ie routing). For example you can add to the VM the second Legacy Network Adapter and configure the routing as it is the tun adapter and see how it is working.

Also I suggest you moving to a xen server, insteed of Hyper-V, as freeware Hyper-V is designed by Microsoft for no-problem using of Windows systems as VMs. They will never go to the other systems native support.

In production I use OpenVPN on Windows VM under Hyper-V with Network Adapter (not legacy) without problem.