Problem fixed by forcing the gateway on the AP to PfSense's LAN IP. I had it set up through /etc/network/interfaces but turns out I had to set it up via route add default gw 192.168.1.1 wlan0

Ok tomorrow morning I work on it a little bit following that thread, for the moment I had to esculede Pfsense, if in case I can't solve it quickly I will downgrade to version 5.2.2 Vince

That's just down to how you have it setup in VBox. You want the WAN side NIC passed through to the pfSense VM WAN interface so it cannot connect to anything without the firewall. The LAN interface can be bridged to NIC2 so anything there will see it on the same subnet. Including the host. You don't want the host PC trying to use DHCP to pull an IP from the pfSense though because it obviously won't be able to until the pfSense VM has booted. So set the workstation to a static IP in the LAN subnet but outside the DHCP range. Steve

I've had a lot of problems with Hyper-V virtualizing firewall, the performance of Endian Firewall on it is poor, as well as problems with pfSense and other things. The ones I had the best results were VMWare and Proxmox, but since I hate VMWare (personal taste), Proxmox became my main virtualization tool! Nowadays with Proxmox Backup Server and the great adoption of KVM by several market players over proprietary solutions, after Citrix mistakes about XenServer, Proxmox has become even better!

@lburns this is not too complicated. You simply want your LAN to be a transparent bridge of two nic ports. The bridge itself provides the router ip address etc. mostly correct post showing how to do this while preserving current LAN settings. https://protectli.com/kb/how-to-enable-lan-bridge-with-pfsense/ a post explaining the correct advanced setting to make it transparent. The above post has this wrong. https://forum.netgate.com/topic/90384/help-clarify-my-understanding-of-the-net-link-bridge-pfil-tunables-please/2 If you can link the two in a transparent esxi bridge, then just pass that bridge to pfsense as your LAN and you are done. Please tell us how it goes.

@raizor_hd Not understanding what they are, how they work or how to set them up.. Yeah bit of a learning curve.. Do you even have a vlan capable switch? Most likely not.. Nevermind is right - waste of everyone's time, especially mine..

@bmeeks Thank you very much my friend it worked for me!

Well as time is precious, let's go to the beautiful and free road, already built an AMI free of charge YAY! Thanks for the help.

@bingo600 The first one was default, I bought the devices last December and the new one is from the Dlink website. Well, now I have put all the port as untagged and turnd the safeguard off. Now they are working again.

@finderos47 wow that is some OLD stuff.. 2k3 even extended support ended back in 2015.. That cpu is from 2008.. And only 32 bit.. Sorry but time to retire that hardware..

@gertjan Dear friend, Thank you for your time spending to reply in my request. Finally, i manage to configure it properly, following the instructions of the Official Netgate manual, using two virtual cards, one of them (LAN) as private. Previously, i used the host network card, and probably this was my fault. Many thanks again!

@octopuss What I do on Hyper-V is disable time sync from the host for the pfSense VM. NTP runs on pfSense, all local machines {including the host} look to PFSense for time sync, and the host maintains time sync for machines that are powered off. [image: 1642511228286-ac0b0807-72aa-46f6-9f3b-3f81e874505b-image.png]

The reason things outside of vm #2 can't reach vm #2 is there is no defined route. In the setup you have, machines on the 192.168.1.x network will not know how to contact the 192.168.2.x network that is behind pfSense. That's because your 192.168.1.x network devices will have 192.168.1.1 as their "default gateway". I assume that device at 192.168.1.1 is a typical wireless home router. In the setup you currently have, any traffic destined for any address outside of 192.168.1.x is going to be sent to 192.168.1.1, and that device is going to say "I don't have a 192.168.2.x network defined, so I'm just going to send this request upstream to my default gateway and let him figure it out". That next default gateway is at your ISP, and it certainly won't know where your 192.168.2.x network resides (and that address space should never appear on the public Internet anyway). You will need to create a routing table entry on the 192.168.1.1 device that instructs it to send requests for anything in 192.168.2.x to the pfSense box at 192.168.1.61, because that network lives "behind" the pfSense machine.

@dierooivalk12 said in PFsense 2.2.6 on VMware 3 Wanports: provide me with some ideas Update to current version would be first thing that comes to mind. Nobody is going to want help troubleshoot anything with version that is 6 years old..

@lifespeed said in best approach for pFsense on Windows VM?: I can only imagine trying to access a hyper-V core installation using a networked GUI tool Fixing a broken hypervisor update / install is the challenge when You don't have Internet access through the pfsense VM Your family does not have Internet access. Which is why I ended up configuring the old physical router I used prior to pfsense. I does not need to be fast, flexible or powerful. Just a limp along option is all that is needed.

I moved all my OPT1 network to pfsense, i use it as my new gateway in place of a synology router and I must admit i'm really happy with this set-up. With this pfsense virtualized on a simple i3-8100, a 2vcore VM with 2gb of ram, i'm able to run speedtest at 930Mpbs download and 610Mbps upload from computers in OPT1, not bad on a 1Gb/600Mb ISP connection :)