Update 1.x pfsense-api to support PFSense 2.8.0

[ne1for23]

**The installation directions fail because the pkg is expecting FreeBSD 14 and pfSense 2.8.0 uses FreeBSD 15. Forcing the package to install I was unable to use the package.

**With the package force installed via this command, requests to the API hang indefinitely.
env ABI=FreeBSD:14:amd64 pkg -C /dev/null add https://github.com/jaredhendrickson13/pfsense-api/releases/download/v1.7.6/pfSense-2.7-pkg-API.pkg && /etc/rc.restart_webgui

**I am unable to use pfSense API v2 for my purposes and would like v1 to be updated for pfSense 2.8.0 compatibility

[alyarb]

I second this request. A majority of users are still on the v1 API and I think 2.8.0 is too soon to dump them.

Since both packages can be installed concurrently, why not maintain a package that serves both v2 and v1 with a toggle capability?

[jaredhendrickson13]

Unfortunately, it's not as simple as just building the package on FreeBSD 15. The v1 codebase was designed around older pfSense 2.4/2.5 functions that are now either deprecated or heavily changed in newer pfSense releases. It takes a lot of time and effort to track down all these changes upstream and figure out how to fix them without introducing breaking changes in the package itself; especially with v1. A big reason v2 was built was specifically to get the package's codebase up-to-speed with these pfSense changes, and to make future compatibility issues much easier to identify and handle. I am still working through the broken components to see what can be easily salvaged and what needs to be rewritten entirely. I don't currently have an estimation on a potential release time frame.

I also just want to note, as mentioned in #500 and #508, v1 isn't being maintained long-term. Its continued support was mainly to give everyone enough time to migrate to v2, and is limited to security updates and general bug fixes only.

I really recommend migrating to v2 as soon as you can. If you're missing any features that were in v1, please open issues for those. The vast majority of the reported feature parity issues have been resolved since v2 came out a year ago.

[alyarb]

Thank you so much for this badass project. I've been using pfSense for 10+ years but you've really made it into a killer app.

After my message, I realized I just have way too many that I work with that are co-managed with too many knuckle draggers who are still on 2.5.2 and 2.6.0. I'll never be able to move them all to v2 in a timely or coordinated way. I have a function that will detect the api version and I'm going to work on adding v2 support to my stuff, so I can work with v1 and v2. Thank you again

[ne1for23]

Thanks for the reply. With v1 not being maintained long term, I was inspired to look again at why v2 didn't work for me.

My use case is simply turning on and off a firewall rule. My problem was that the API and web UI indicated the changes were being made, but the effective rule wasn't changing. Figured it out. When I was calling the /api/v2/firewall/apply endpoint, I was using GET instead of POST. The JSON responses are identical between the two apply requests, but only POST actually applied the outstanding changes. I can finally upgrade to pfSense API v2 and pfSense 2.8.0 CE. 😊

There are probably still users that want to stay on pfSense API v1, but I'm not sure if they have good reasons.