incomplete info can be found here: https://doc.pfsense.org/index.php/Developing_Packages =)

STARTTLS works. The UI is a bit misleading, though. The "Enable SMTP over SSL/TLS" checkbox really means If checked, use SMTP/S If unchecked, use STARTTLS To use office365, you'll need the following settings: E-Mail Server: smtp.office365.com SMTP Port of E-Mail Server: 587 (Unchecked) From e-mail address: The email address associated with your account Notification E-Mail address: Whereever you want the notification to go Notification E-Mail auth username: The same email address as the From e-mail Address (your login email address) Notification E-Mail auth password: Your account password Notification E-Mail auth mechaniasm: LOGIN It's important to note that the FROM address and the Auth Username must be identical. Failure to make them the same will result in an error message saying you're not permitted to send as address.

Thanks for the info, I'm glad to see a project that I supported coming of age. The team has worked very hard for years, I'm excited for what the future holds for pfsense. I for one am thankful for what information you have released and will wait patiently for more news to come.

Ah OK, I'll try to figure out some other way of getting graphs out of RRD files then.

Ideally anything dealing with FreeBSD-ports should happen on a FreeBSD system at some point (either directly or in a secondary capacity) because then you have access to tools like portlint which can check the port structure to ensure it's complete and correct before committing changes, for example it will flag problems with the formatting or content of the Makefile.

When the package is made properly, the pkg add will perform the exact same install procedure as the GUI would.

I also found myself with this problem, which I was able to fix with this fix : https://github.com/freebsd/freebsd/commit/6884a6e482ca6effa702761a1e3fa98bb6946c30#diff-49d9a861ee932d5b656eb20466f2a292 But other problems have occurred. :-[ I had not had this problem with the RC version, which it was in "FreeBSD 11.0", so I put a compilation environment under this version, and compilation to work. I therefore conclude that the development team forgot to add a "BRANCH RELENG_2_4_0" on this repository: https://github.com/pfsense/FreeBSD-src The "Main repository for pfSense" is also unusable because it refers to a "BRANCH" that is missing: https://github.com/pfsense/pfsense/blob/RELENG_2_4_0/tools/builder_defaults.sh#L108 Can someone tell us about this omission ? Thank you !

As far as I'm aware, we have no intention of adding any wifi features like that. AP features belong in an AP. FreeBSD is great, but it does not lend itself well to being an AP.

@biggsy: Thanks Bill but I'm not sure how it would be related to Squid.  However, I'm not a Squid user either so I could easily be wrong. I run this bgpctl command from a tiny PHP script called through an afterfilterchange shellcmd. It causes the BGP peer to resend all the currently blacklisted IPs, which are loaded into an Alias table referenced by a block rule on WAN.  It does this very, very quickly, too. The only reason for having to do all this is that the Alias table is not managed through the GUI, so it gets cleared on a rule change or reload. Of course, I have no reason to expect this won't be achievable in some other way under 3.0 but it is a very useful function of openbgpd. Sorry…just realized today that I posted my reply to the wrong thread ...  :-[ Bill

If it was an optional package add-on, the GPL license doesnt taint the base at all. +1 to this. This guy brought it in via freebsd packages https://blog.dhampir.no/content/pfsense-as-a-cisco-anyconnect-vpn-client-using-openconnect

FauxAPI has received an update to v1.1 In brief:- new API call alias_update_urltables - forces the immediate update of remote URL tables new API call gateway_status - returns the current status of the gateways updated documentation tested against pfSense 2.3.2 and 2.3.3 The package has received some great feedback and users deploying in complex large environments - enjoy, send feedback. N

I had the same issue until I increased my RAM disk size.  I think what happens is the file tries to write to the RAM disk but fails since it's out of space with the default size.  The setting is found under System/Advanced/Miscellaneous.  I increased mine to 512 MB's.  Since I have 8 or 16 gigs of RAM and have plenty to spare.