Rob, I use OPNsense on hyper-v with no problem and it is fully up to date update/patch wise. Although this may not help, OPNsense was based on a fork of pfsense. I have had odd connectivity issues before which has resulted in stripping back the config and starting again, and thinking about it one did happen after an update a couple of years ago where the config didn?t seem to update properly. A rebuild of the config sorted it. Mark Sent from my iPhone

Rob - The physical NICs - is one Broadcom and the other Intell? --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet

Ok - the Realtek is part of the motherboard?s I/O panel and you have some sort of a PCI-e dual-port card with an Intel chipset. I ran into a very similar issue with my Sophos UTM9 software appliance running on Ubuntu (a quad gigabit Intel chipset card) - The numbers of packet errors would keep climbing up very fast. I switched to a Broadcom and that worked. --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet

In your case, you are running directly on hardware with NIC drivers that interact with that stuff. Rob?s question was specifically about running this within a Hyper-V VM. Given that, the host system?s hardware should not have anything to do with his problems since, even if his setup provided multiple NICs to the pfsense system, they would all be Hyper-V simulated NICs. From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of Supratim Sanyal Sent: Monday, August 10, 2020 4:12 PM To: hecnet at update.uu.se Subject: Re: [HECnet] Off Topic - pfSense on Hyper-V Ok - the Realtek is part of the motherboard?s I/O panel and you have some sort of a PCI-e dual-port card with an Intel chipset. I ran into a very similar issue with my Sophos UTM9 software appliance running on Ubuntu (a quad gigabit Intel chipset card) - The numbers of packet errors would keep climbing up very fast. I switched to a Broadcom and that worked. --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet<http://www.update.uu.se/~bqt/hecnet.html> On Aug 10, 2020, at 6:15 PM, Rob Jarratt <robert.jarratt at ntlworld.com<mailto:robert.jarratt at ntlworld.com>> wrote: The physical machine has three NICs. A Realtek one which is on the LAN and used to access the host for management purposes. A dual port Intel one (Intel PRO/1000 PT) which provides the LAN and WAN interfaces to the virtual machine. Regards Rob From: owner-hecnet at Update.UU.SE<mailto:owner-hecnet at Update.UU.SE> <owner-hecnet at Update.UU.SE<mailto:owner-hecnet at Update.UU.SE>> On Behalf Of Supratim Sanyal Sent: 10 August 2020 14:01 To: hecnet at update.uu.se<mailto:hecnet at update.uu.se> Subject: Re: [HECnet] Off Topic - pfSense on Hyper-V Rob - The physical NICs - is one Broadcom and the other Intell? --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet<http://www.update.uu.se/~bqt/hecnet.html> On Aug 10, 2020, at 4:57 AM, Keith Halewood <Keith.Halewood at pitbulluk.org<mailto:Keith.Halewood at pitbulluk.org>> wrote: Is it something to do with the virtual switch setting that permits/prevents multiple Mac addresses from the same virtual adapter? On 10 Aug 2020, at 08:35, Rob Jarratt <robert.jarratt at ntlworld.com<mailto:robert.jarratt at ntlworld.com>> wrote: ? I realise this is completely off topic, but I think this list has a lot of experienced networking people, so I am hoping someone might have a suggestion. I have pfSense running as my firewall at home, running on Hyper-V. In case you don?t know, it runs on FreeBSD. I have run it for a few years and really want to get it upgraded to the latest. But when I do the upgrade doesn?t work because every packet in the WAN interface seems to get lost, it just cannot send anything to the WAN. The LAN side is fine. I posted on the pfSense forums about this a long time ago. I got some questions about the MTU, but it was fine I was just wondering if you have any thoughts/suggestions/experiences? Thanks Rob

The thing I keep avoiding is a completely fresh build of the whole VM. I think that could be my best course of action. Regards Rob From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of Supratim Sanyal Sent: 11 August 2020 00:25 To: hecnet at update.uu.se Subject: Re: [HECnet] Off Topic - pfSense on Hyper-V Agree. In my case the physical NIC change worked. The virtual NIC to the VM has always been Intel. --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet <http://www.update.uu.se/~bqt/hecnet.html> On Aug 10, 2020, at 7:22 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com <mailto:Mark at infocomm.com> > wrote: In your case, you are running directly on hardware with NIC drivers that interact with that stuff. Rob?s question was specifically about running this within a Hyper-V VM. Given that, the host system?s hardware should not have anything to do with his problems since, even if his setup provided multiple NICs to the pfsense system, they would all be Hyper-V simulated NICs. From: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE> <owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE> > On Behalf Of Supratim Sanyal Sent: Monday, August 10, 2020 4:12 PM To: hecnet at update.uu.se <mailto:hecnet at update.uu.se> Subject: Re: [HECnet] Off Topic - pfSense on Hyper-V Ok - the Realtek is part of the motherboard?s I/O panel and you have some sort of a PCI-e dual-port card with an Intel chipset. I ran into a very similar issue with my Sophos UTM9 software appliance running on Ubuntu (a quad gigabit Intel chipset card) - The numbers of packet errors would keep climbing up very fast. I switched to a Broadcom and that worked. --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet <http://www.update.uu.se/~bqt/hecnet.html> On Aug 10, 2020, at 6:15 PM, Rob Jarratt <robert.jarratt at ntlworld.com <mailto:robert.jarratt at ntlworld.com> > wrote: The physical machine has three NICs. A Realtek one which is on the LAN and used to access the host for management purposes. A dual port Intel one (Intel PRO/1000 PT) which provides the LAN and WAN interfaces to the virtual machine. Regards Rob From: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE> <owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE> > On Behalf Of Supratim Sanyal Sent: 10 August 2020 14:01 To: hecnet at update.uu.se <mailto:hecnet at update.uu.se> Subject: Re: [HECnet] Off Topic - pfSense on Hyper-V Rob - The physical NICs - is one Broadcom and the other Intell? --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet <http://www.update.uu.se/~bqt/hecnet.html> On Aug 10, 2020, at 4:57 AM, Keith Halewood <Keith.Halewood at pitbulluk.org <mailto:Keith.Halewood at pitbulluk.org> > wrote: Is it something to do with the virtual switch setting that permits/prevents multiple Mac addresses from the same virtual adapter? On 10 Aug 2020, at 08:35, Rob Jarratt <robert.jarratt at ntlworld.com <mailto:robert.jarratt at ntlworld.com> > wrote: ? I realise this is completely off topic, but I think this list has a lot of experienced networking people, so I am hoping someone might have a suggestion. I have pfSense running as my firewall at home, running on Hyper-V. In case you don?t know, it runs on FreeBSD. I have run it for a few years and really want to get it upgraded to the latest. But when I do the upgrade doesn?t work because every packet in the WAN interface seems to get lost, it just cannot send anything to the WAN. The LAN side is fine. I posted on the pfSense forums about this a long time ago. I got some questions about the MTU, but it was fine I was just wondering if you have any thoughts/suggestions/experiences? Thanks Rob