Replies: 3 comments 16 replies
-
|
The package will only install and operate on pfSense, not FreeBSD directly. The use of FreeBSD is only to build the package since pfSense itself does not contain the required tools to build the package. The steps to build and install the package for testing are:
After it's installed, you can perform your testing. Some prefer to just copy any files changed during testing over to pfSense at this point instead of rebuilding the package for each change. The Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
<snort>
<snort_interfaces>
<0>em0.102</0>
</snort_interfaces>
</snort>This is likely the config area that is causing the restore. Double check that this is not also present in your active config. It's possible for pfSense to get stuck in a bad state where the active config is bad, and the previous config is also bad. This could also explain the slowdown you're experiencing as it can result in a write loop. Make sure your config is in a good state, reboot and try again. If things are still slow, consider spinning up a new pfSense test instance and see if the issue is still present there. |
Beta Was this translation helpful? Give feedback.
-
|
We have taken the step to reset our pfSense system to ensure we are working from a clean slate, but unfortunately, this did not resolve the issue. The configuration you mentioned was indeed part of our setup, and we have double-checked to ensure no remnants of problematic configurations were left in the active config after the reset. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm okay, it's likely something else then. Do you have a package build you can provide me? I can do some deeper troubleshooting later today. |
Beta Was this translation helpful? Give feedback.
-
|
Here is a copy of my package :) |
Beta Was this translation helpful? Give feedback.
-
|
I can't seem to reproduce the issue using that build on a fresh install of pfSense 2.7.2, it works as I'd expect it to. Maybe I'm doing something wrong trying to reproduce the problem, here is my process:
{
"status": "ok",
"code": 200,
"return": 0,
"message": "Success",
"data": {
"interface": "lan",
"descr": "Test",
"snaplen": "1518",
"performance": null,
"fpm_split_any_any": null,
"fpm_search_optimize": null,
"fpm_no_stream_inserts": null,
"cksumcheck": null
}
}{
"status": "ok",
"code": 200,
"return": 0,
"message": "Success",
"data": {
"interface": "wan",
"descr": "Test",
"snaplen": "1518",
"performance": null,
"fpm_split_any_any": null,
"fpm_search_optimize": null,
"fpm_no_stream_inserts": null,
"cksumcheck": null
}
}
Is there something I'm doing differently? |
Beta Was this translation helpful? Give feedback.
-
|
We tried the solution on another pfSense firewall, and it worked. We realized that a reset of pfSense wasn't enough, so we deleted and reinstalled the OS, and now everything is working fine again. Thank you for your help! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I hope you're well :) I was previously developing endpoints for Snort on v1, but since v2 has been released, I decided to restart the implementation to follow the continuity of the project. To do so, I wanted to start with a less complex endpoint, such as Captive Portal, to understand the functioning of v2. However, I am encountering several issues on v2 that I cannot understand. Issue 1: GET Request on a Specific IDWhen I make GET requests for a specific ID that I know exists: I get the following response: { It seems to say that the ID is missing even though it is provided. However, when I make a GET request to retrieve all captive portals: I get a correct response without any errors: Issue 2: POST Request to Create a Captive PortalWhen I try to make a POST request to create a Captive Portal, I encounter a PHP system error. Request: Response: I apologize for taking so long, and unfortunately, I don't have good news. I am facing these issues and would appreciate any help or guidance on how to resolve them. Specifically, why the GET request for a specific ID is failing and why the POST request results in a PHP error. Thank you in advance for your assistance! |
Beta Was this translation helpful? Give feedback.
-
|
For your first issue, the ID is not being seen because you've specified the content type as application/json but the ID is provided via URL encoded parameters. This command should work: The second issue appears to be an issue with PHP loading the pfSense configuration. pfSense has a global variable $config that should be an array representation of the pfSense configuration. However, references to the $config global are returning |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your quick response. For the first issue, I will try using the application/x-www-form-urlencoded content type as you suggested. Regarding the second issue, I don't have a config.xml.bad file because I'm working in VM and I restore them to their original state whenever I encounter a problem. And here's the Model class I'm working with for the Captive Portal (I haven't included all possible options in this model intentionally, to try to simplify debugging...) Thank you ! |
Beta Was this translation helpful? Give feedback.
-
|
Your Model looks fine, do you by chance have a file at |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am currently working on developing API endpoints for the Snort package as part of our project enhancements. During my development process, we have encountered an issue when trying to build the endpoints using the provided management script.
Environment:
Vagrant VM setup on FreeBSD
Issue Description:
When we attempt to build the endpoints by running the command:
I receive the following error messages:
It appears that the script is unable to find the APITools.inc file in the expected directory. I have verified that the path and filenames are correct as per the repository files.
Steps to Reproduce:
Could you please help me understand what might be going wrong here? Any guidance on how to correctly build and integrate new endpoints would be greatly appreciated.
Thank you for your assistance!
Best regards,
Beta Was this translation helpful? Give feedback.
All reactions