@stephenw10
I dunno.... no clue, I rebuilt the 2 hyper-v adapters on the pfsense vm, the external and internal... and of course now it works. Oh well...
@raqib But it is not helping in every case, I had problems on Server 2022 and this only helped some of the time.
What "helped" me all of the time was using two separate, external vSwitches, one only for pfSense and one for all the other VMs. And that meant there had to be a physical switch in place to connect those two vSwitches. Thankfully it is working in the latest Plus-version.
I wish I knew why for those that follow after. I changed a few things at once so I'm not sure if one of or combination of them was responsible or the fix.
I turned off TCP/IP on the WAN NIC.
I rebooted the modem and router at the same time with cables connected.
@Wonko2k Danke für die Antwort, die ein bis zwei reboots im Monat sind verschmerzbar, da ich die Sicherheitsupdates auch immer selbst durchführe.
Hatte mir jetzt doch noch eine i350-T4 bestellt, dann bin ich zukünftig flexibel was getrennte Netze angeht, kann den zweiten LAN Port vom DrayTek anschliessen um die Daten auszulesen etc.
Sorry but I am with @ITFlyer - and I edited your post to remove what amounts to keywords and a link..
Glad your wanting to help - but keep it on topic to the question at hand.. And why would you join a forum, minutes latter add such a post to a almost year old thread, because it mentions something related to what your wanting to promote is what it looked like.
