• I'm fairly sure this is me, but I wanted to double check before I really dig further into my new config.

    I had a 2.1 setup with my main LAN traffic routing over the WAN (BT Infinity) and a 2nd LAN (virtual from VMWare ESXi) that went out over an OpenVPN connection (SlickVPN service).

    I've been putting off switching from ESXi to Hyper-V till pfSense had support. I've now started over, destroyed my ESXi and am running on Hyper-V. I've reconfigured a VM with pfSense and as far as I can see everything is set-up as per the old system, but all my virtual LAN traffic is routing over the main WAN and not the VPN. Whatismyip.com reports the same WAN IP if I'm on the main LAN or the virtual LAN.

    Can anyone confirm that OpenVPN should be working fine in the current alpha (27/5)? If so can anyone spare some time to help me figure out where I've screwed up please.


  • Rebel Alliance Developer Netgate

    No problems I know of with OpenVPN or routing/gateway groups, unless you hit on a snap that had other unrelated issues (which have been plentiful, it is still alpha after all)

    Try a new snap from today or later, see if it's any better.

  • Thanks. Pretty much as I thought it was likely a PEBCAK issue. I'll try a new update over the weekend and see what falls out the other side.

    Apart from this hiccup for me, considering the alpha status, it's been rock solid on Hyper-V…