@Gertjan

For some reason, I wrongly assumed that cron would only read the crontab file when the service re/started.
Thanks for the explanation, and the tips for how I could check this myself next time.
+1

A package update containing the fix for this bug is building and should show up for users shortly.

The new Snort package containing this bug fix is 4.1.6_9.

@BlueCoffee said in Snort fails to install.:

got the new box and all is well guess the other one was bad. Ive installed Suricata (looks alot like snort) Would you set this up on lan also? Do you know where I can read more about the setup? don't want to not have it set correct this time around.

You can find several Sticky Posts at the top of the IDS/IPS sub-forum here: https://forum.netgate.com/category/53/ids-ips.

As with Snort, I recommend putting Suricata only on internal interfaces (LAN, DMZ, etc.). The only time I would veer from this approach is on a box with very limited RAM and/or CPU horsepower and I had a fairly large rule set enabled. That might be a point where you conserve RAM and CPU by just putting a single instance on the WAN instead of several instances on internal interfaces. But you will have the limitations I mentioned in my earlier post. Best practice would dictate that the different interfaces on a firewall likely will need different IDS/IPS rules enabled. Rules should be tailored to the unique vulnerabilities and threats present on the protected network. So, in that scenario, individual IDS/IPS instances on internal interfaces works better (if you have the necessary RAM and CPU power).

As you noticed, Suricata and Snort have an almost identical GUI. That's because a ton of the Suricata PHP GUI code was a copy and paste from the Snort GUI.

Any basic set up instructions you find for Snort on pfSense will also apply to Suricata on pfSense. One key difference is that Suricata does not use Preprocessors in the way that Snort does. Suricata just works differently internally. The preprocessors were a way for Snort to add new features over the years. Suricata accomplishes that a bit differently internally, so no need for specific preprocessors. There are settings similar to the Snort preprocessor settings under the FLOW/STREAM and APP PARSERS tabs in Suricata.

A big difference in the packages is the rich EVE.JSON logging system in Suricata. Initially EVE.JSON logging is disabled causing Suricata to log essentially the same way as Snort did. But if you enable EVE.JSON logging for an interface, you can capture a lot of data about network traffic and of course any alerts. Suricata can log a lot of data with EVE.JSON logging and many of the options underneath that feature enabled. Just be sure you go to the LOGS MGMT tab and enable automatic log management. The defaults you find there should be fine for an initial install.

Here is a link to the official documentation: https://docs.suricata.io/en/suricata-6.0.13/.

@romulo-reuwsaat I also would love to see this as a package.

Thanks to all involved in creating this.

I am now able to cast to 'Google Home device/speaker groups' across VLANs, which wasn't previously possible.

@munson Hi, I'm not saying it's wrong but in short it works like this, without creating so many rules.
I allow the ITO Network to have access to the Lan Network OPT1 ect ect ect ....

RulesIOT.png

There is a new video, perhaps it can help you..
It was released today.

@jimp was kind enough to update the LCDProc package to include a NTP server screen georou @ GitHub originally created and we updated. Current package is 0.11.5. There is a pending update to 0.11.5_1 (screens below) that improves the display of PPS, GPS, vs GPS+PPS in certain edge cases.

https://github.com/pfsense/FreeBSD-ports/commit/b3a3a4bf28ad8a50211b6775ed20011097ceeef9

If you have a PPS source, it will display either the number of satellites (GPS) or stability value (PPS). Otherwise, it will display the Active Peer Server IP address.

Notes: I am by no means a NTPD algorithm expert, but I noticed if a source is marked as a valid PPS Peer "o", NTPD uses that to sync and serve time to clients regardless if there a separate Active Peer "*" used for time data. If a GPS is being used for both a PPS Peer "o"and source of time data, it will be marked as PPS Peer "o" and there will be no other Active Peers "*" marked (see screen cap below). The NTP Widget seems to display the Active Peer "*" even when the PPS Peer "o" is actually being used to sync and serve time to clients. Which source is actually served to clients can be confirmed with "ntpq -c sysinfo". If you want to see the stability value when using a GPS with PPS, you can simply set the Clock ID of the GPS source to "PPS". I intentionally did not include seconds on the display since even with the LCDProc Refresh Frequency set to 1 second, time will jump multiple seconds with each screen refresh. Not sure if there is another mechanism that would improve the refresh rate of the first row to eliminate increments of multiple seconds.

Feedback welcome, subject to the limitations noted above.

I happen to be using a Garmin 16X (PPS Only) and 18X (GPS+PPS). NTPD only supports one PPS source at a time, thus marks the second as False Ticker "x"

https://github.com/elvisimprsntr/pfsense-ntp-gps. (WIP)

Screenshot 2023-08-08 at 9.25.04 AM.png

LCDGPS.png

LCDPPS.png

LCDIP.png

I tried to install Wazuh agent too following this article https://marcius.pro/index.php/2022/03/11/wazuh-criando-regra-no-pfsense-para-bloquear-ip-de-atacante/, and I've success on FreeBSD12/pfSense 2.6 CE.
However, in FreeBSD14/ pfsense 2.7 CE or pfSense+ 23.1.1, I haven't succes. The error is

code_text ```Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1 2404007936:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/sources/FreeBSD-src-plus-RELENG_23_05_1/crypto/openssl/ssl/statem/statem_clnt.c:1921:

Snort gets its time from the firewall system. It has no special or unique time setting.

@Neosmith20 said in LLDP not starting after latest update (0.9.11_2):

Installed packages to be DOWNGRADED:
pkg: 1.19.2 -> 1.19.1_1 [pfSense]
...
after that, I uninstalled lldpd, reinstalled it, and then it immediately came up.

Fantastic.

I added this rule on a VLAN to allow mDNS to work across subnets. I've had this rule in place well before recent updates though:

2023-07-27 at 20.20.58.png

☕️

@aaronssh Well, I’m using mac-auth and my clients are entered on the MAC addresses sheet, so it does work in the right configuration.
But if you are not going to use 802.1x you can just create the MAc addresses as users.

seems that the service entry in config.xml is not updated automatically.

on an untouched system, after update to nrpe 4.1, config.xml still looked like this:

<service> <name>nrpe</name> <rcfile>nrpe3.sh</rcfile> <executable>nrpe3</executable>

with this the service was not starting.
after removing the "3"s I can start the service from web gui.

Obviously a troll post.

@flink4 - thanks! I've hacked something else in place for the time being, but will try this out when I find the time!