Oh FFS

I spent all night trying to get this working, this morning I posted to the forum for help, then decided to try one more thing….

and now it works

UPS Cable = 940-0119A (my cable is 940-0119B, but that is not coded into the program)
UPS Type / Device = dumb /dev/cuau0
Device = /dev/cuau0

Now to see if it really shuts down gracefully

Eric…

APC1.png
APC1.png_thumb
APC2.png
APC2.png_thumb

I finally solved it using "agnoster duplicator"…
It does exactly as i wanted..  :D

https://github.com/agnoster/duplicator

@BBcan177:

Take a look at the port scan Pre-processor. There are settings there to not alert on certain scanners and also has some other tuning settings.

BBcan177 is correct.  There are a number of tunable parameters for the portscan preprocessor.  It's on the PREPROCESSORS tab for the interface.  One thing you can do is a create an Alias containing hosts that should never trigger a portscan alert.  That is the "Ignore Scanners" box.  Create the alias with those hosts under Firewall…Aliases, then come to the PREPROCESSORS tab and enter the alias name in the "Ignore Scanners" box.

Bill

Hello Simby,

Snort will use as much memory as it needs. If you goto the Snort Interfaces and edit the WAN interface, in "WAN Settings" you will see an option "Detection Performance Setting"

For this, follow jflsakfja's recommendation and set it to "AC-BNFA-NQ"

Then depending on what Rules you enable and how you set the Pre-Processors, Snort will use the memory that it needs.

If you are looking for some other information, maybe try to re-phrase the question?

From what I understand, HTTPS filtering is tricky because the proxy only sees the IP addresses at the two ends of the tunnel and not the actual URL.  For SquidGuard to see the content of the traffic, it would have to have a trusted cert installed on the user's PC, and this would make pfSense the "man" in what's essentially a Man-in-the-Middle attack.  Modern browsers can detect this to a degree and may warn the user.

You can block all of HTTPS through the firewall of course, but if you need to selectively block some HTTPS sites and not others, you will have to use IP addresses.

I've seen some stuff on the latest releases of Squid/SquidGuard that supposedly support filtering HTTPS, but I haven't tried it or really paid it much attention as I use Squid2.

Just FYI… pfSense seems to be a continuous work in progress, but it is still one of the best FREE alternatives out there. There are many issues on getting packages configured properly, and information is spread all over (although this forum is a great place to get started). Anyway, I found out that in many cases (more often then not), simply re-installing a package is NOT enough. Also, restore using the "Factory Defalts" from the Diagnostics menu, does NOT clear everything. That is a VERY MISLEADING name. The only thing it resets is some superficial settings of the XML config file and web user interface. Many stale configurations and files remain around, and specially those that where manually changed/created via shell.

So, my 2 cents are: once anything gets miss-configured (unstable), simply backup you configuration, do a brand new fresh install ("formatting" the drive), EDIT your config-pfSense.XXXX.xml file, and manually remove everything related to the bad/hung package, and then restore you config back. YES, stale settings will also remain the XML config file, even if after you remove packages our related items using the web interface!!!

Turns out this is a bug in sarg. Old reports are not deleted if 'Generate the index tree by file' is not selected in General settings.

http://sourceforge.net/p/sarg/bugs/159/

OK, from what I understand, Squid handling HTTPS traffic will only see the IP address and not the actual requested domain.  Other people's solution for blocking Facebook on HTTPS is getting their CIDR block, create an URL table alias and then using firewall rules to block access to the alias:

https://forum.pfsense.org/index.php?topic=69860.0

Check out the reply by Phil Davis.

I think I may have read that Squid3 can handle HTTPS traffic, but it involves installing a certificate and essentially acting as the man in the middle, which might alert the web browser of an attack.  I haven't played with Squid3 so I can't say for sure.

@Heisenberg1977:

Is there a specific link that you are referring to regarding "Bill Meeks advice"?

Thanks for the other suggestions.

Click on Bill Meeks name, and then select "Show Posts" You can follow thru on his advice in Several Threads. He is a wealth of knowledge!

Here is one of them:
https://forum.pfsense.org/index.php?topic=77952.msg425066#msg425066

Hi Gurus
Let me explain my scenario (Network Diagram)
Router (ISP)  <===>  Firewall PFsense <===> My Lan Segment
In the PFsense I installed the the squid (Version 2.7.9 pkg v.4.3.4).
The problem that I am finding is that This Proxy (Squid) only block web that use ports 80 (Like www.youtube.com) but not ports 443 (like www.facebook.com).
The problem to filter all port 443 I am solved by apply a rule Like this:

Well, let me know if exit an alternative to filter in base to group.
For example Group 1 (permit traffic 80 and 443 to the following pages - Like banks, facebook, emails, www.youtube, etc the rest are blocks)
Group 2 (permit traffic 80 and 443 to the pages of banks)
Group 3 (some policy That I would considered)
Also I would create some different another different

Profile of user 1 ( User VIPs, acccess to all pages)
Profile of user 2 (User which belong to Group 1)
Profile of user 3 (User which belong to Group 2)
….............
Profile of user n (User which belong to Group n)

My version of firewall is:

Also, exit any type the report where I can review (an extrat this data) and elaborate a Report to inform the top of Traffic that the user consume.

I appreciate your comment /suggestion

Pretty much, if you know how to navigate a Linux/UNIX filesystem.  cd / will get you to the root folder, not to be confused with the 'root' folder.

No solid date. Should be moving to BETA sometime in the next couple weeks if all goes well.

Why not just filter based on the domain name?

To get details about a new package, click on its version number in the list.  That will take you to the change log.

On your Installed Packages screen, if any package has a red Version column, it's means there is an update to that package.

@lautrecote:

hello
thank you for your post and details of configuration  :)
What is correcting the problem is :

have postfix forwarder listening to LAN instead of WAN write a NAT rule to redirect smtp traffic to LAN address of pfsense

I think it's the same you recommend having postfix forwarder listening to loopback ?

I don't understand why it works, why it suddenly didn't work anymore, and why this trick solves the problem.
Can you explain that to me ?

thank you again  :)

It isn't the same as having the forwarder listening on loopback.  Did you mean to say "listen on WAN instead of LAN"?

Are you relaying from an internal mail server to the outside world?  That might explain it but I don't know how you would get emails from outside if you're listening on LAN.