There are no options to control which events generate e-mail notifications. The only one of the items you listed that is somewhat possible is the interface one, though that is only possible via gateway monitoring, not from the interface event itself.

Don't forget to set the default gateway in the routing section. I recently had a similar problem with the WAN being shown as up, but LAN clients being unable to connect to the internet. It was because I had migrated the router from a different location and the old default gateway was still set.

@jhunt Certain models of TP-Link switches, including your don't handle VLANs properly, in that they allow multicasts to leak. There are apparently issues with VLAN 1 appearing on all VLANs. This may have been fixed with an update.

@ntranx /var/db

Hmm, how about snort and the openappid-vpn_tunneling.rules. ruleset? If you do go through with locking down VPN, please do your users a solid and make sure your Wireless environment is secure and users aren't at risk of packet sniffing or MiTM attacks.

@user_three $15 a month with ATT.

@pfguy2018 Yes, that appears to come from the first server tried. However, it also seems to have a bad checksum, so it would be discarded.

There is a server side issue at the moment. We're working on getting it restored.

Nice.

@aminbaik To send the ip addres of the client/webbrowser to the server/webserver behind haproxy there are a few options: 1- option forwardfor 2- send-proxy 3- source 0.0.0.0 usesrc clientip Each has its own (dis-)advantages.. https://github.com/PiBa-NL/pfsense-haproxy-package-doc/wiki/haproxy_pass_clientip_to_webserver

Cannot delete this post. No longer asking this question.

ok.

I am sorry for bump, but still looking for a solution to get curl to work with NAT 1:1.

$ cat /etc/syslog.conf # Automatically generated, do not edit! Do not edit that file. The include line I mentioned tells the system to load custom syslog configuration files from /var/etc/syslog.d/. Try this: $ printf "local1.notice\t\t/var/log/access.log\n" > /var/etc/syslog.d/apache.conf $ service syslogd restart In your apache.conf (not the syslog.d/apache.conf) you should having something like this: CustomLog "|/usr/bin/logger -t httpd -p local1.notice" combined Also, one more time so I feel like I properly warned you. Do not run your own webserver on your firewall. All it takes is you making a mistake in your server code and now someone has compromised your firewall. DO NOT DO THIS.

Hi Guys, It is very good idea! did you find solution to setup this ? thanks

@johnpoz thanks a lot ;)

@stephenw10 Thank You Alot...I just reinstalled pfsense on the device and it worked

Hmm. Yes I believe there are a number of providers who will just use the source IP of an update. The customer option there may also work rather than using one of the built in presets. The pfSense update client will do that anyway if the monitored interface has a private IP but that makes it tricky in your case.... Steve