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.
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 :)

@patch said in Virtualized PFsense - host (linux) cannot ping Pfsense Wan Interface (and vice-versa) - Not rule related:

@spyshagg
Yuk

As a desperate measure I would prefer:

using pass through NICs for pfsense. Monitoring the interfaces within pfsense and resetting them via an pfsense watchdog / interface monitor if required.

But whatever works

Hardware and software configuration are not possible at this point. The problem manifested itself 3 full weeks after deployment and not in the 2 weeks of internal testing prior to deployment.

A simple reset does not fix the issue. The vm must be shutdown and restarted.

It appears the problem is indeed with the hypervisor blocking packets.

thank guys

Well, I reckon its a firmware version issue.

When Proxmox boots up, it installs t5fw-1.26.2.0.bin If I pass the whole card through to pfSense, it installs t5fw-1.25.0.40.bin and the interfaces are available for assignment as expected
If I just pass a VF through with fw 1.26.2.0, pfSense ignores the card and doesn't load the driver, even though it is present as a PCI device in the VM

Its a bit of a catch 22. I can install 1.25.0.40 by passing the whole card through to pfSense, but after that the host can't see the card until it is rebooted and then it updates to 1.26.2.0.

I haven't been able to figure out how to prevent Proxmox from updating the firmware. I used ethtool to downgrade the firmware on the host but the pfSense VM no longer boots with VFs attached.

Days and days on this :(

@elewsmer please share with us, how you able to set queues greater than one.

on pfsense 2.5 doesn't work:
https://forum.netgate.com/topic/138174/pfsense-vtnet-lack-of-queues/9?_=1638715122702

@stefansz said in Pfsense 1 nic:

I can purchase usb network adaptors and try to do pass though (if using proxmox), but I don’t know how good they are if going via usb

USB network cards are not recommended to be used with pfSense.
You may set it up on Proxmox and bridge it to pfSense though, but then it's on Proxmox / Debian, how they perform. I don't know.

Anyway, to connect all your devices behind pfSense, you need a switch at all. So get a VLAN capable switch, then you can also go with only one NIC on pfSense and set up WAN and LAN on VLANs.

@viragomann I will try after work. Thank you!