[FIXED]Cannot get IP from Cablemodem with a vm pfSense 2.2 guest in Hyper-V

kaede15

Ok so I manage to get my pfSense up and running inside the hyper-v (windows 2012 r2 x640) with normal nic (not the legacy one) and they work great.
I have two nics in my box one is a Realtek and the other one is a usb ASIX eth0 both works flawlessly.
My vSwitches are these:


ext sw realtek (connected to realtek) --> Lan for pfsense
ext sw asix (connected to ASIX) --> Wan for pfSense

In Pfsense vm


eth0 ---> ext sw asix ---> hn0 (wan)
eth1 ---> ext sw realtek ---> hn1 (lan)

The Asix eth is connected directely to my cablemodem. After a couple of seconds I get a public IP which can be viewed in details "ext sw asix" in windwos 2012r2 and I can ping outside.

But strangely I cannot get public ip with my vm pfSense.


hn0 wan --->
hn1 lan ---> 192.168.1.1/24

I remember somewhere I red that in some old nerwork it cannot give an ip to a physical nic with 2 macs….
I test it with a cheap router with the following settings.


cablemodem ----> cheap router ------(lan dhcp)----------> ext sw asix(host) -------->hn0 (vm pfSense)
                 public IP        192.168.1.1/24            192.168.1.100/24          192.168.1.101/24

Is there a way for the vm pfSense to connect directly to the cablemodem???

cheers!

kaede15

Found a solution, have to uncheck "Allow management operating system to share this network adaptaer" option in your virtual switch in my case the nic intended for the WAN.

Also found that when creating vSwitch for wan, beside unchecking the "Allow management operating system to share this network adapter" option, enable the Single Root-Input Output visualization SR-IOV option.

After that select in the virtual nic for pfsense verify if Virtual Machine Queue VMQ and SR-IOV are checked under "Hardware Acceleration" of the virtual NIC.

One thing I found strange is the Internal vSwitch cannot be accessed by legacy network adapter… since pfSense 2.2 include vm drivers there is not need to use those legacy nics anyway.

I found this method very efficient when you want to use usb nic. Since those nics support are generally way better under Windows than FreeBSD. So in my setting I use a usb NIC based on ASIX chipset as WAN and my Realtek onboard nic as LAN in a VM pfSense in Hyper-V Windows server 2012 R2 x64.

Cheers! ;D ;D ;D

KOM

Nice work.

kaede15

@KOM:

Nice work.

Thx
been tinkering with this little box for over a week now, guess the fact that it doesn't work well with pfsense (with all the usb eth and all) and making it work is even more fun than actually using pfsense HA! ;D ;D

netmc

This is just what I needed. ;D I was having issues setting up this as well, and while I had set the SR-IOV in the network manager setup, I missed it under the VM/Network/HW Acceleration.