@ErnestoRey perhaps you could use the 'cron' package instead of manually editting the config?

You'll be needing a compatible device with at least two NICs (network interfaces).
This could be a VM, this or an ordinary PC.
The SG1100 will get to you preloaded with pfSense.
Or visit https://www.pfsense.org/download/ and download a copy - and burn it to a USB key.
Then as usual, read the notice first https://docs.netgate.com/pfsense/en/latest/install/index.html and do what's explained.

Basically, installing pfSense is like installing, for example, Windows 10. The hardware requirement are not the same : you do not need the latest graphics card to run it - just a second internet card (do not choose build-in wifi as a second LAN interface ....).

When I read the notes I wasn't sure what was wrong. I had thought it was just a ruleset issue or something similar. Not a code base change... My bad.

Thank you guys for all the work you put into pfSense and FreeBSD.

Tyler.

@jimp
2.5.x dev builds.

I am in the exact same scenario - using 2.5.x to be able to run AES-GCM and it was working flawlessly for months and months until I updated around Christmas, and then it choked out 2-3 times since, prompting this post.

I switched to non-AES-NI on both IKEv2 setups and it is solid for 24hrs plus right now.

I will update both machines on Friday and re-instate the AES-NI ike v2 and see how it goes.

box 1:
2.5.0-DEVELOPMENT(amd64)
built on Fri Jan 03 22:01:28 EST 2020

box 2:
2.5.0-DEVELOPMENT(amd64)
built on Fri Jan 03 22:01:28 EST 2020

What was in the backup you restored?

Maybe the backup had a different update URL which caused it to fetch something it shouldn't have and break the installation.

Otherwise it's not clear what might have happened. Nothing should have removed files from packages like that which are required parts of the base system.

Unless maybe you have some other kind of problem like a disk issue.

@jjstecchino This was noted previously and resolved (at least it was when I loaded the most recent build this AM).

tunnels are up again.
Thanky you jimp for fast and competent support.
Really appreciate it.

Cheers,
luphi

That looks like cygwin or msysgit. It still is limited by the underlying filesystem support. You need something that emulates a non-Windows filesystem and environment.

You can use a completely isolated VM for that, as has been mentioned already, but I just tested using the Windows/Ubuntu integration (Windows Subsystem for Linux (Link 1, Link 2)) and it checked out OK there as well.

@jimp Many thanks for you clarification.

Remove it !

Thanks!

Now I also found the proper documentation for a pull request!

https://docs.netgate.com/pfsense/en/latest/development/submitting-a-pull-request-via-github.html

Have a nice day!
//magnus

There is no apache on pfSense. Perhaps you meant nginx?

You shouldn't call the shell exec programs indirectly like that. It isn't going to work. You're telling PHP to spawn a subshell and then run more PHP code from there.

If you are looking to make your own page, just copy the contents of the easyrule script and adjust it to suit your needs. Though odds are, whatever you end up making will be less secure than granting users rights to edit firewall rules in the GUI directly.

Trying to run a pfSense shell script from the GUI won't work as you expect (if at all). Use an actual shell.

If people have info - then they would post it here, not personally email you with it.. Such action would defeat really the whole purpose of a forum ;)

Also that would also give you the persons email address - which many are not open to be sharing with some guy on a forum asking for help..

edit: BTW what is more likely to happen with you posting your email like that is some yahoo will think its funny to sign you up for every kind of spam or fetish porn they can.. If I were you I would really remove that email address from your post.. If you need help doing that - just let me know.

@stephenw10 said in Question about list, tables and pfctl:

pfctl -a openvpn/test1 -t automatic_41319fc_0 -T show

did it!!! thank you!!!

The fix for the issue identified in this thread is now available in the Snort-4.0_8 package version. The update is available for install for users of pfSense-2.5 snapshots only.