@bingo600 said in SOLVED: pfsense vm or physical?: @lewis I'm not talking about a VM going down unexpected. I'm talking about the times. ie. my ESXi servers has been down this year due to critical patches, that had to be applied to ESXi or vCenter (well servers doesn't need to be taken down to patch vCenter). /Bingo Oh yes, very good point. In that respect, pfsense running on its own hardware is never an issue. I've never had an update cause down time. That alone seems to seal the deal. I've also run pfsense as a vm using two of the blade nics. It works as expected, just a bit tricky to set up but you're right about the host.

Hyperthreading enabled. [image: 1641594336666-screenshot-2022-01-07-172457.png] Hyperthreading disabled. [image: 1641594839150-screenshot-2022-01-07-173308.png]

@stephenw10 I may not use it. It fits my design goal, free. Totally not needed. And I'm not all that eager to have a video card fan start squealing. The box is in a work at home office. Someone gave me an electric boat trolling motor. I'm looking at connecting it to the battery in the PFSense box UPS. Stick the propeller into the case. Cool that sucker DOWN. There'd have to be some tweak to the NUT package though.

@viragomann Yes! Thanks!

Ahh that's brilliant, I didn't equate that option in the advanced settings with the config file. Many thanks

What are those IPs? How is the OpenVPN server configured? What change caused this to start? Steve

@ericarias1984 Figured it out. Looks like the password I was using was too long (must have been truncating it).

@accidentalit said in Configure Comcast static IP on WAN: Static IP Range: 50.199.13.49 - 50.199.13.49 CIDR Block Number: 50.199.13.48/30 Gateway IP Address: 50.199.13.50 Subnet Mask IP Address: 255.255.255.252 If they have assigned you those IPs you should just be able to enter them in pfSense and it will work. There's nothing else you can do in pfSense to make that work. If it's not working it's with the Comcast modem that isn't configured to use it or Comcast is not routing that subnet to you. It sounds like your connection is configured for a dynamic IP and hasn't been reconfigured as static yet. Steve

@pvasirani your clients asking pfsense for dns should have whatever search suffixes they want to use on themselves. If you want unbound to ask specific NS your running locally on your network when a client asks for something, this would be setup in a domain override on unbound.

Nope the upgrade will take care of it. The patch will remain in the package but will show as applied because it's already in 22.01. You can just delete it at that point, do not revert it! Steve

@jimp Thanks so much

@stephenw10 OK...thanks for the quick answer on that... ...romany

Yup, that's most likely. Apply the patch here against 21.05.2 to disable it before 22.01: https://redmine.pfsense.org/issues/11933#note-7 Steve

Yeah, it's fixed in 22.01. pcdcd is not run unless it's needed, which is almost never. Steve

Yup, that ^. You can't run pfSense and something else there unless both are virtualised. Steve

Nothing I can think if currently. Yeah any sort of packet loss will kill throughput.

Hmm, those are really the only config options available to you? If so you can only connect outbound. One option there is to have some external server at a public IP, say something cloud based, and connect out to that from both the internal pfSense and external clients. Steve

@trumee Glad to see you got it working. I don't have any access to a system with a PPPoE interface to test with but I'll see if I can put these notes in the instructions for others who might want to do the same.

Right so add an IPAlias at 10.0.0.100 on the pfSense LAN in that subnet. Then add a port forward (or 1:1 NAT rule) for 10.0.0.100 to the new IP on the other side of the tunnel. Steve