Link state and interface assignment in Hyper-V

[JadeKnight]

Hi.

I'm currently in the process of migrating from ESXi to Hyper-V. The new firewall instance is in place on the new hypervisor running Windows Server 2012 R2. I'm using latest build of Pfsense 2.2.1, which to my knowledge is supported on Hypver-V using the standard network adapters (synthetic adapter, not legacy).

I do have some trouble with identification of the adapters during initial setup. The system is using five network adapters. All adapters are reported as up, despite the fact that they are not connected (only present). When I invoke auto detect, Pfsense is not able to recognize any changes in the connection, although I do connect the WAN interface when asked in setup.

Anyone knows about the issue and a solution? How does this affect things in production if a connection is lost?

Any help would be appreciated :)!

[moo82]

How I identify network interfaces:

In Hyper-V's Virtual Network Manager, I make a net for each interface.

LAN1 Intel blah blah #2
LAN2 Intel blah blah #1
ISP1 Intel blah blah #1
ISP2 Intel blah blah #2

I named these virtual networks after the cables I put into the corresponding ports. Easily verified in Windows.

Then, in settings for the VM, I added 4 cards with the 4 aforementioned virtual networks, and MAC dynamic.
Start the VM, enter settings again, and all the cards will now have MAC addresses.

Network adapter LAN1 MAC ends with D2 0E
Network adapter LAN2 MAC ends with D2 10
Network adapter ISP1 MAC ends with D2 11
Network adapter ISP2 MAC ends with D2 0F

In pfsense, I don't auto detect, but instead choose the hn interface with MAC corresponding to those I noted above.

So LAN becomes the interface with MAC D2 0E, WAN becomes the interface with D2 11, OPT1 becomes D2 10 and OPT2 becomes D2 0F. Then I rename OPT1 and OPT2.

There might be a better, or other way, but this way works for me.

[JasonJoel]

That's exactly how I did it too.