Hello again,

I tried my best and the solution qua replacement-script of the files that are renewed at every boot seems to work.
I placed the script into /usr/local/etc/rc.c. It looks like that:

#!/bin/sh kill -9 $(cat /var/run/syslog.pid) cp /root/Skripte/syslog.conf_ersatz /etc/syslog.conf /usr/sbin/syslogd -s -c -c -l /var/dhcpd/var/run/log -f /var/etc/syslog.conf kill -9 $(cat /var/run/cron.pid) cp /root/Skripte/crontab_ersatz /etc/crontab /usr/sbin/cron -s

Best wishes
Michael

That's the minimum version requirement. Whilst I haven't actually tried it yet in 2.1.5 I would expect it to install and run without issue.

Edit: works fine with Android iperf client.

Steve

Thanks for the suggestions. At the end, even if I liked the idea of the online syslog service, the lack of encryption dissuaded me. Maye in the future it would be nice to have rsyslog with TLS support in pfSense.

I opted for a bit of an unorthodox solution. I had my old Nexus S phone just sitting in a drawer so I tried installing the Server Unlimited Pro app on it, set up a syslog server and smb share, power it with a usb cable from the Alix box and it worked. Now I have a very small power efficient syslog server that I can access from my Windows clients :)

@KOM, thanks it worked.

After having some problems with my install, I just did a complete wipe and fresh install of pfsense. I went to grab DansGuardian, and low and behold, it has been updated already - somebody beat me to the punch!

Thanks Steeve.

Ok empty fields in the cron job are not allowed.  ???  So the above example would only fire on Wed. @ 20:30 even though it has an * in the "mday" field.

I haven't come across any information that states which fields take precedence. :o

It is a font issue, see:
https://forum.pfsense.org/index.php?topic=81073.15

@jailbreaker:

I have just put a PFSense firewall in at home and have setup snort rules everything appears to be running correctly however i cannot get snort to report alerts to the alert tab.  I have reinstalled snort a couple of times and had no success is someone able to point in the right direction to try and troubleshoot this?

Thanks

Jail

Are you a new Snort user?  If so, when you say "have setup snort rules", can you provide some more details.  Did you go to the CATEGORIES tab and select either an IPS Policy or some rule categories?  Did you go to the RULES tab and verify that for the categories you selected, they actually contain one or more enabled rules?  I ask because some of the Snort VRT category files are actually empty these days as the VRT has shuffled their rules around into some new file names, but they left the old filenames there just empty to prevent errors on startup for legacy users.

If you are a novice user of Snort, here is a thread on how to get it jump-started:  https://forum.pfsense.org/index.php?topic=61018.0

If you have done all the above already, or are an experienced Snort user, then ignore what I posted above and tell me what interfaces you run Snort on and whether or not you have tried nmap and some targeted scans at interfaces protected by Snort.

Bill

I think stephenw10 has a good point, assuming its true that the current release pfsense although based on a BSD version not current, is supported via the pfsense staff.  I'd put the burden on the testers to show me that pfsense is not properly patched if that is their stance.

Their logic works for closed source stuff like XP, but not opensource as much.

Diagnostics > Tables. Pick the alias name from the drop-down.

Or look up the pfctl man page and check the section on table commands for the CLI way

Lightsquid is designed to be 'lite' so it generally doesn't go to extreme detail. It more for collecing stats.
You can always look at the squid logs directly or use some other log analyzer. Not that i've tried that personally.

Steve

Yes, MindfulCoyote is right, a "gold" or whatnot, subscription to ESF includes the paid support, online "cloud" backups, and a book.

Seems I'm not the only one curious about the release of the bundle of paper for v 2.0.

Alas, not everyone has the budget to "go commercial".  Some think that "commercial", is really the future direction of pfSense & ESF.

Some prefer to run their own "cloud", say, for example, using FreeNAS or NAS4Free.

Ok, I found that I can enabled NAT Reflection and that solves my issue.

Yay!!!  ;D  That would be awesome and a huge help!!!  Selecting Everything in the Syslog categories adds a few Mbps of traffic to my Syslog server.  haha

Thanks Jim.

@stephenw10:

Yet it worked ok when you manually edited the syslog.conf file?

Yes it worked. Thanks !!

@stephenw10:

Use the Shellcmd package to run a specific command at each boot.

Thanks to point this out ! I will test this package in the next days for further tasks.

Now we can close this thread  8)