HI Jimp, I confirm resolv problem in the buld Fri Jul 06 15:23:49 EDT 2018. Thanks for the helps. Best regrads, fred

Ta Jim :)

@dbayplaya2k3 thanks!

You can also pipe to logger for logging command output: $ echo BLAH | logger $ clog /var/log/system.log | grep TEST Jun 28 11:01:51 clara root: TEST

Uhm that's bad, i was a bit lazy with backing up the config (because pfsense is sooo stable, of course :) ) The only one i could use is from 2016 and i've changed a lot in the meantime. So my bad. I will try to be patient or use a router for the meantime.

Thanks for the reply Jim. Sounds like this is pretty far off. I guess for now I'll just make a simple script and cron entry to scrub every now and then and dump the results into syslog.

My fault. Not enough performed a network interoperability check. The problem is on the Open VPN server side. Thank you jimp.

I'm sending my credential information to https://${PFS_HOSTNAME}/index.php

any news?

I added a note and closed out the ticket for you. We now require a cross-reference between Redmine issues and PRs for submissions, so we can catch things like this, but this was merged just before we started doing that.

Hello LemonParty1 It seems we are doing the same thing but for different reasons. Anyway, I see you renamed the firewall to GNS, but taking a closer look to your log file, it seems you forgot to rename one of the build.conf lines to GNS, cause it is still showing "MyFirewall" as the PIBA-NL wiki is showing. Not sure if you already figured it out, but if you don't, try it again renaming all fields to "GNS" as you did to the other fields/lines. I could generate a brand new ISO file with a different name. It took me a week to understand everything, but it's now much more clear to me. I didn't try to generate a RELEASE ISO file yet, just a DEVELOPMENT. Let me know if you could finally finish your compilation. Meybe we can exchange good information. Regards Fabricio.

https://github.com/hrs-allbsd/wide-dhcpv6/tree/freebsd I see Many thanks!

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.