pfSense Hyper-V VM, DSL modem, VLANs
-
I have a pfSense 2.4.4 Hyper-V VM (host is Hyper-V Server 2012 R2) on an Optiplex 380, with a single physical GbE interface. I'm trying to use VLANs to support 2 virtual NICs (WAN and LAN), with an Actiontec GT724R (RFC 1483 transparent bridge mode) connected to a separate port on the same switch the Optiplex is connected to. The LAN side of things is working well (DHCP/DNS services on pfSense working great), but so far I can't get a WAN (PPPoE) connection. I would appreciate any suggestions. See diagram below.
-
I would put that virtual nic on WAN on untagged VLAN 100. Else I would think you would need to create VLAN 100 in pfSense and assign WAN to that.
But I don't use hyper-v so I don't know what it does there. It's either configured to pass the VLAN tag to the VM or it's untagged from the VM's perspective.
-
@derelict Hmmm...I'm not sure there is a way to assign a virtual NIC for a Hyper-V VM to an untagged VLAN. I had added a VLAN during pfSense initial config, to match the virtual NIC and physical switch port configs. The general ease of virtualization lured me into forgetting the requirement for VLAN support at the NIC hardware/driver level. Broadcom docs indicate Netlink 57XX series don't have VLAN support. My onboard NIC is a Broadcom Netlink BCM57780.
I ended up adding a multi-port PCI-E NIC (removed the bracket so it would fit my low profile Optiplex 380), connecting a second port between Hyper-V host and switch (untagged/PVID VLAN 100) for VLAN, and reconfigured switch, virtual NIC and pfSense interfaces accordingly. Success. Though for me it defeats the purpose of a VLAN in the first place. The switch, modem and Hyper-V host (pfSense) are all in close proximity, so I can simply connect the modem to the second port on the Hyper-V host. But I never used a modem connected to a switch port instead of directly to my router, and was curious whether it would work as expected.
Your response got me thinking in the right direction. Thank you!
