Looks like it's fixed in 2.6.0 GA

This is the perfect way to end this v2.6RC thread, isn't it?

Screen Shot 2022-02-14 at 4.31.39 PM.png

@daddygo Nice...

@viktor_g

Pfsense Version 2.6.0-RC (amd64) built on Mon Jan 24 18:44:12 UTC 2022 FreeBSD 12.3-STABLE

DHCPd6 : when switching from assisted to managed , the error disappeared

Assisted -Will advertise this router with configuration through a DHCPv6 server and/or stateless autoconfig.
Managed- Will advertise this router with all configuration through a DHCPv6 server.

dhcpd.leases:

"#This lease file was written by isc-dhcp-4.4.2-P1"

"#authoring-byte-order entry is generated, DO NOT DELETE"
authoring-byte-order little-endian;

server-duid "\000\001\000\001(;\311<\254\037k\261\355\006";

ia-na "\000\000\000\000\000\003\000\006\224\246~\261\225\311" {
cltt 3 2022/02/02 06:07:21;
iaaddr XXXX:XXXX:XXXX:d9d:10:1:44:245 {
binding state active;
preferred-life 43481;
max-life 86300;
ends 4 2022/02/03 06:05:41;
}
}

ia-na "\000\000\000\000\000\003\000\006\224\246~\261\225\314" {
cltt 3 2022/02/02 07:56:34;
iaaddr XXXX:XXXX:XXXX:d9d:10:1:44:253 {
binding state active;
preferred-life 53937;
max-life 86300;
ends 4 2022/02/03 04:57:49;
}
}

ia-na "\234\216\353\353\000\001\000\001'\324)o\270'\353\353\216\234" {
cltt 3 2022/02/02 11:27:42;
iaaddr XXXX:XXXX:XXXX:d9d:10:1:44:255 {
binding state active;
preferred-life 53937;
max-life 86300;
ends 4 2022/02/03 11:26:02;
}
}

ia-na "\257\370_\275\000\004VM\313;6\3450\354\027te\016J\022\363w" {
cltt 1 2022/01/31 15:30:55;
iaaddr XXXX:XXXX:XXXX:d9d:10:1:44:247 {
binding state abandoned;
preferred-life 53937;
max-life 86300;
ends never;
}
}

ia-na "\000\000\000\000\000\003\000\006\224\246~\261\225\311" {
cltt 3 2022/02/02 12:09:42;
iaaddr XXXX:XXXX:XXXX:d9d:10:1:44:245 {
binding state active;
preferred-life 43481;
max-life 86300;
ends 4 2022/02/03 12:08:02;
}
}

@tbird635 +1, Just updated an install that uses NUT and has e-mail and other notification types enabled to 2.6.0.r.20220124.1828 and got a bunch of

[02-Feb-2022 07:26:33 Etc/UTC] PHP Warning: file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 261

Great to see it is being dealt with already :)

I opened a bug to track this: https://redmine.pfsense.org/issues/12747

Thanks, fixed now :)

This might be horrendously off topic, but I'll mention anyway since I've bumped into it a few times.
The newer instance isn't set up with snort/suricata on inline mode is it? My speed has always taken a massive dive if I let it sit inline. It is a large price to pay for those few packets compared to legacy mode.

@jimp enabled the admin account, it's working now.

@skogs said in Syslog output in GUI-Cli:

Tests fine here.

Edit: found the issue - its a translation problem - in my case if I switch the GUI to german language there is a generated entry in syslog that has some weird coding of german umlaut signs! This leads to no output. Correcting the corresponding translation in pfsense.mo (de_DE) resolve the issue!

@jimp Yeah when it didn't show me the usual downloading/patching and about to reboot, good chance I clicked that button an extra time.
Silly users doing unexpected things.

The error appears to have been caused by the changes made to fix https://redmine.pfsense.org/issues/12475, and that issue was still open, so I will reuse that and commit a fix shortly.

I'm still experiencing this. The only non-success message, that I can find, comes when the services_dyndns_edit page times out.

ServicesDynDNS.png

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

All but the names are consistent with the last backup for 2.6.0.
How the names stuck???

The configuration file contains the customisation you have done to pfsense including any renaming you have done.

So when a configuration is restored the names are restored.

If names are restored they were in the configuration file you imported.

So the part of your question which does not make sense to me is why you expected the names not to be restored on this occasion. Perhaps:

you believe they were not set in this particular configuration backup you assumed configuration backup for 2.6 would be very different to the configuration file for 2.7 (despite then being currently a few days different in code freeze)

Please clarify why you feel the names being there was unexpected then perhaps more helpful replies would be possible.

@louis2 TrueNAS and jail VLAN networking is confusing to me. I never figured it out and just bridge my jails to the main network. Not that there isn't a way or that it somehow can be made to work. I just got tired of messing with it and punted. That was a couple years ago and I never revisited it.

Seems you have proven it's not pfSense though.

Redmine and Github are the places to check for changes. Github would have more detail in most cases. Check the main source repo, the ports repo, and the devel-12 branch of the FreeBSD src repo.

2.6.0.b.20220103.0600

I can confirm that with outbound nat "any", system can nat itself and reach the Internet.

Regards