@gwaitsi I have a 4 port HDMI & USB KVM. However, in your case,it might be easier to bring the pfsense computer upstairs. Also, my Qotom has a serial port. If necessary I could use it. Running a serial cable isn't hard. In fact, you can use an Ethernet cable, with Yost connections. You just configure a DE-9 (It is not a "DB-9") connector for each end as needed.

Hmm, where are you seeing that log? ff00.Internal.private is the pfSense host name? Are you handing Internal.private to clients via DHCP to use as a domain? That's clients requesting the wpad file for their domain. Unless you have set it up specifically it won't be on pfSense. It looks like pfBlocker DNS-BL blocking those lookups maybe? Steve

Yeah, if all the app traffic is being proxied through that it's the first place to check.

@stephenw10 okay, I'll open the ticket.

@stephenw10 Thanks, so the enemy is within :)

I'm sorry you had such a hard time with this. I'm still not completely sure what you tried to do here and what happened. Restoring a config in the webgui, actually uploading it and converting it to the current config version, should be near instantaneous. Once that's done it will ask you to reassign the interfaces if there is a mismatch and then reboot into the new config. I assume that did not happen when you tried it though. I can't see any support tickets from the email address you used here but if you have a support subscription and didn't receive the expected level of support I would very much like to review that if you have a ticket number. Steve

@bmeeks said in iflib_netmap_config: Those are harmless information messages from the netmap kernel device during its initialization. It is printing out the current configuration of netmap based on the NIC driver being used. It is detailing the number of rings, TX/RX descriptors, and the buffer size that will be used. There is no way to stop the message. It comes from the kernel device itself. Nothing pfSense nor any packages can do about it. Thank you Bill...the only way I saw it was hooking up a monitor to my pfSense box, a rare occasion...was thinking to do a clean install since I had upgraded from v2.5.2> 2.6RC > 22.01 release.

Try restarting php from the menu if you can still ssh in. I had assumed you were connecting to the serial console, which should always be available. https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/connect-to-console.html What php error are you seeing? Steve

@serbus You will need to reinstall 2.6CE and then upgrade through to Plus.

@stephenw10 said in Proxy Support ?: I mean connect pfSense to the VPN and then use policy routing to send whatever traffic you need across it. That could be all traffic from a particular internal interface. Thanks for the help, I already have it!

@jimp Those times corresponds to Suricata updates. I've adjusted it to be daily at 5:37 in the morning which should be pretty slow. We'll see how it does.

@bingo600 said in Migrating from CE to Plus - Home & Work Commercial: As if you're not having pfSense L2L tunnels from your Home pfSense to the company, then it's not "commercial". Aka. using a PC VPN client from home (via pfSense) to the company is OK. But having a permanent L2L tunnel to the company is NOT OK. Ah - many thanks, thats clear now. fireodo

You can upgrade now: https://www.netgate.com/pfsense-plus-upgrade-information For nothing! Steve

@jimp I understand the empty CPU frequency is coming and going when the CPU is working at full speed on Adaptive PowerD mode. But, when I use Hiadaptive, my CPU stays at full speed all the time, that's why I have now CPU frequency.

There is no interface for ZFS snapshots yet. There is a new ZFS widget on pfSense Plus but currently it is only for viewing status information.

I've been running 2.6 for months, on numerous boxes, no significant issues. There seems to be some potential problems if you're running in Hyper-V. Some users are seeing throughput reduced (significantly) in VMs there. Steve

@kik The safest thing is probably to open a free ticket with Netgate and get a copy of the firmware, then install from that, and restore config from backup.

Your use case doesn't align with the intended use case of the package, and limiting it in the way you describe would also limit its usefulness for others. My point is that it's not necessary to run the watchdog package in nearly all cases. If you feel that the watchdog package is necessary there is almost certainly something else wrong with your setup that is making it appear like it's what you want, when it likely is masking the real problem. The watchdog package is unlikely to gain additional features due to the fact that it really shouldn't exist at all, and is only a workaround for other bugs people have hit over the years.

Hmm, probably better to report in that thread then whilst we try to pin this down. Steve

@stephenw10 said in When pfSense CE reaches Netgate TAC end of support will a pfSense+ ISO be available to download?: I couldn't tell you what the situation will be by the end of year but I anticipate there may be changes to meet subscribers requirements as those become clear. Fair enough that answers my question. I will just wait and see what happens later on. Netgate does have good informational blog posts etc so I assume if/when a pfSense+ ISO for x86_64 hardware becomes available Netgate will let us know. Thank you for the help.