Upgrade 2.4.4 to 2.4.5, vlans on shared NIC become unreachable
-
This is a VM on a Hyper-V host (sole VM on the machine.) Multiple NICs (8). I have some that are dedicated to their own NIC, but 1 NIC has 4 attached to it.
The VLANs that are on their own continue to work fine, but the ones sharing a NIC stop working. From outside of the VLAN, I can ping the Interface IP but inside the VLAN I can ping other clients, but not the gateway.
This all works fine before the upgrade, but stops after.
Because everything works fine before the upgrade, I am confident that the trunking and tagging are configured correctly on the switch and in the Hyper-V host (the NIC in question allows vlan tags 1-1000.)
I've tried blowing away the VLAN and assignment in pfSense and recreating it, but it would not come backup. I don't have enough NICs to reserve one for every VLAN I want to support so I need at least some to be shared; I'm stuck not being able to upgrade until I can determine what the cause is.
I have rolled back the device to 2.4.4, but I have a config backup of what it looked like in 2.4.5.
Each VLAN is assigned a /24 with the gateway on .254 of the scope.
While troubleshooting, I only worked on VLAN 10, the other VLANs attached to HN7 (9,5,6,20) were left untouched. I tried changing the interface IP from .254 to .252I can try the upgrade again in a week; any suggestions to try when I do, or questions I can answer using the config file would be appreciated.
-
Resolved the issue. I had to reset the trunking for the NIC after upgrade. I have no idea why an update inside of a VM would affect the network configuration of the VM in the host, but the following command fixed the issue:
Get-VMNetworkAdapter -vmname "pfsenserouter" | ? macaddress -eq "<mac address of NIC used>" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-1000" -NativeVlanId 1