Great! Thank you guys! I'm understanding how this works a little better. I am learning networking and cybersecurity so I am wanting to eventually set this up so I can have a separate network/VLAN for a home lab, but that is later. Right now I just wanted to understand pfSense enough to not knock my wife off the internet...lol

pls show me your full /etc/network/interfaces file from proxmox host i cant seem to make it work plssssssssssssssssssssssssss

Naaah, it's absolutely free (and fast). -Rico

@akuma1x I understand this, and you are pretty much reiterating what I wrote. Thanks.

Realtek is bad hardware and software (drivers). And not really well supported in FreeBSD. -Rico

Can this install be done from the command line without pulling the CF card? Not sure of the process.

That's where I copied pasted it from ;)

Hello DaddyGo, I usually use a 4 ports (with RJ-45 eth.) NIC and use a 4-ports SFP NIC, this is already 8 interfaces, but this is network and segmentation dependent... I'd like to have four rj45 ports reserved for my pc, usb mfc scanner, vivint dvr, and printer. More rj45 ports the better..; -) So here is a question - I use the two available ports on the pci-e nic, the other two can be reserved for a switch etc or two ip devices if I decide. Is this correct logic? With this PC that was donated to me, it only has one pci-e bus. So I am at the mercy...;-( One of the reasons started to think about using m.2 wifi 6 to broadcast the SSID. But as I reviewed m.2 it appears that speed suffers. So I started to look at AP or Mesh. Another option I have, I still have my tp-link router which I could use as an extender. But I want Wifi 6 and best I can do is Wifi 5 on the router. Now, how does my motherboard onboard nic come into play? Can I use this connection into from my cable modem and then the pci-e nic for lan connections? And yes, the onboard NIC is realtek..;-) @tvos " I purchased: Ziyituod Gigabit Ethernet Card" this was a bad idea as this NIC contains a Realtek ethernet controller and the latter quality of Realtek is poor and not recommended in a firewall... the forum is full of why not use Realtek based NICs, I wrote above which does not cause headaches and that is Intel based NICs (I'm not even talking about Realtek driver problems anymore) I ditched this and returning - wouldn't even line it up correctly to the expansion slot...;-( I will definitely go Intel as recommended. Again, appreciate the insight. Thank You for the links, I will definitely be spending time watching the vids and documentation. All the best, tvos

@sanketgroup did you find your answer ? I had version 2.3.4 and need to increase disk space.

Agree with @sheen73 on simplifying the setup especially for home use. Expand later with VMs once the basics are working. Another reason being power use, I would imagine a box capable of running multiple VMs would require significantly more power to run than a little box (e.g., SG-1100) running pfSense alone. I understand the urge to play around with a setup like the one you have above. Most of us on here like playing around with stuff like that, but doing so behind the scenes as suggested might be better. The unifi is reporting DNS and DHCP problems? I'm assuming you tried the unifi forums as well since the unifi logs might not be very helpful here. What makes you think it is a setting in pfSense which could be the issue if the problem is only on the wifi? Are there wired VLAN devices that are working perfectly fine? If so, which specific application(s) or site is running on wired clients which is not running on the wireless clients?

ruled out. this issue is duplicated now even in the manufacturer

@tleadley Holy crap, somehow pkg, pkg-static and pkg2ng in /usr/local/sbin all got overwritten and showed zero bytes. I was just lucky enough to have access to one of my other SG3100's and copied the files over. I ran the repair process once again and we are good to go, no factory reset required.

@viragomann thanks dude! :)

Ok so everything appears normal again. The issue I believe is related to the igb driver. I had it set to use 2 queues, configured in loader.conf.local, after I reverted it to single queue mode the issues went as fast as they came. I dont know what the default is now days. Some may remember setting the driver to two queues on some igb hardware used to cause kernel panics, but then that got fixed in FreeBSD, so the dual queue mode does have a history of problems. If anyone else has these symptoms and they using igb, then this might be a place to look. The variable is 'hw.igb.num_queues'.

<Lightbulb goes off!> Thank you!

@jimp /root/.profile appeared to be a generic FreeBSD file. I replaced it with one from a working pfsense install and things appear to be back to normal. Thanks!

I'm a bit embarrassed. Tried to delete this, but seems I don't have permission to do so. Incase anyone is having similar issues..... REBOOT. All I needed to do was reboot the workstations and they were working perfectly with the pfsense as the gateway.