Working great here so far, Thanks a lot!!! :)

Yeah it was the migration to nginx that made that field necessary. I was looking at possible fixes yesterday and haven't had time to get back to it yet. Rather than breaking every custom portal page out there, we should be able to fix it in the URL it's filling in.

did send a fix for loading the all-flags back in the webgui when editing a rule: https://github.com/pfsense/pfsense/pull/2488

As for flags on non tcp traffic, and quick on a 'match' rule im not sure if those should be allowed… Pass and Block can be final actions on the traffic, but match i dont think is useful as a last rule.. Might be wrong there.. Also keep in mind that rules are only used if no state exists that is already handling the connection..

how you firewall show the hostname of blocked rules ( i hope you understand me )

info.png
info.png_thumb

Should be. I installed last night and I believe gui prompted me for updates 3 or 4 times since.

@josepgb:

Thanks Jimp,

already tried this, but console said that package was not available…

also I did a pkg search php56 and that one did not popup...

Now, in my rebuilded machine, if I do a pkg search php56 it shows up. Yes, I know that I should expect this in beta stages :)

Thanks for your reply, Pfsense Support is awesome as always.

cheers from Barcelona.

I've added php56-mysql (which is now deprecated in PHP 7, also added php56-mysqli and php56-pdo_mysql which are better options. Consider to upgrade your code to use one of them.

That change applies to both 32 and 64 bit. At the point you tried there might not have been a new 32 bit update yet, but it's available now for both.

ok thanks helper

just wanted to make it more known if someone else was having issues

Looking at this now. Thanks.

Fixed. My fault (but you probably guessed that) Working on a new feature for the rules page and broke that bit.

@cmb:

That's because of:
https://redmine.pfsense.org/issues/5748

Yup same issue. My wan_stf too gets an IP but it is still "tentative".

Just pointing out stuff as I come across them.

Thanks

Working like a charm!

@LFCavalcanti:

I saw at least 20 people complain about that Captive Portal patch being removed from Squid3, something that wasn't doing harm to anything, some people, close to you, said it was better to remove said code in order to clean the package, since "nobody was using it", see the BS here is in the "nobody" part.

We didn't remove that feature, a community member did, but it was harming people. That's why it was removed. It was badly, repeatedly patching (incorrectly in many cases) the captiveportal.inc and leaving people with broken firewalls. That is unacceptable. Use the system patches package, not an automated mechanism in squid, and it would be fine. That way it could be managed in a smarter fashion. The feature, as implemented, was broken and causing harm, thus it was removed.

The log question isn't one I can answer myself, it's above my pay grade, as they say, I suggest you make a new non-hijacked thread for that.

ok will try to research it maybe a good aspect for a hangout maybe i missed something already from the ipv6 hangout

@Valex:

Great, so i hope we can use the build-in nginx as reverse proxy and don't need the squid3 package?

Eventually that is the plan, yes. We're looking at Ledge.

It's a reverse proxy only though, so there is still a use case for squid as a forward proxy unless someone can whip up a client/forward proxy that works directly in nginx.

That was good to have it merged - saves messing about with possible conflicts.
Here is PR https://github.com/pfsense/pfsense/pull/2463 to fix the problem with not re-loading the updatefreq on edit.

I just noticed this today with the latest update:
2.3-BETA (amd64)
built on Sun Jan 17 11:55:43 CST 2016
FreeBSD 10.3-PRERELEASE

Mine is a bit different though:

Jan 17 19:24:34 php-cgi rc.bootup: Creating rrd update script Jan 17 19:24:34 php-cgi rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt1-dhcpd.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 3 data source readings (got 8) from N:U:U:U:U:U:U:U:U' Jan 17 19:24:34 php-cgi rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/lan-dhcpd.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 3 data source readings (got 8) from N:U:U:U:U:U:U:U:U'

After reviewing the dpinger source code and doing some associated changes/fixes to the pfSense GUI front-end, I looked at the previous text explanation of the parameter relationships, added some validation checks in the GUI for stuff that I thought "must be on in any use case I can think of", and then wrote that text explanation based on what I observed.

If anyone has later thoughts about extra use cases that should be allowed or better wording of the explanation… feel free to make suggestions and PRs...