New pfSense Plus 25.03-BETA is here!

[mcury]

Testing now.. so far so good.

Upgrade from 24.11 in a SG-4100 took around 10 minutes.
All packages still working , no problems to report yet.

• acme
• arpwatch
• aws-wizard
• iperf
• ipsec-profile-wizard
• lldpd
• Netgate_Firmware_Upgrade
• nmap
• nut (UPS not directly connected to pfSense, remote server configured).
• pfBlockerNG-devel (DNSBL disabled, only using IP block lists).
• Service_Watchdog
• System_Patches
• WireGuard

Thanks Netgate team.

[Gertjan]

@chudak said in New pfSense Plus 25.03-BETA is here!:

No upgrade path 24.03 => 25.03?

I saw the same question somewhere already, the answer was : go to 24.11 first. You don't need to stay long there, you can then access the second Beta : 25.03.b.20250306.0140.

Btw : 25.03.b.20250306.0140 rock solid for me.
( not using pppoe )

[mr_nets]

Regarding the PPPoE optimization, is it on track I didn't see any mention about that in the release note and no one has given any feedback?

[mcury]

Weird, I'm observing some weird logs after updating to 25.03 BETA.
These are new, checked several days behind and only found these after the update.

login-to-view

Found this topic that may relate to this issue: https://forum.netgate.com/topic/195347/seeing-kea-dhcp-issues-after-upgrade-to-24-11/24

echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq
echo '{"command":"lease4-get-all"}' | nc -U /var/run/kea4-ctrl-socket | jq

first_command.txt second_command.txt

Cleared DHCP leases but the issue still persists.

Kindly let me know if you need more details, thanks.

[Gertjan]

@mcury said in New pfSense Plus 25.03-BETA is here!:

first_command.txt

Use this command :

echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq | grep 'pool'

Yours showed :

login-to-view

Are you sure ? /32 means : 1 lease avaible !?

I have :

[25.03-BETA][root@pfSense.bhf.tld]/root: echo '{"command":"config-get"}' | nc -U /var/run/kea4-ctrl-socket | jq | grep 'pool'
          "name": "pool_lan_0",
          "name": "pool_opt2_0",
          "name": "pool_opt1_0",
        "thread-pool-size": 0
      "reservations-out-of-pool": false,
          "pools": [
              "client-class": "pool_lan_0",
              "pool": "192.168.1.70-192.168.1.200"
          "pools": [
              "client-class": "pool_opt2_0",
              "pool": "192.168.2.15-192.168.2.254"
          "pools": [
              "client-class": "pool_opt1_0",
              "pool": "192.168.100.50-192.168.100.100"

My pool go from, on 3 interfaces :
LAN : 192.168.1.70 to 192.168.1.200 = 130 Lease avaible.
OPT1: 192.168.2.15 to 192.168.2.254 = 240 leases avaible.
OPT2 : 92.168.100.50-192.168.100.100 = 50 leases avaible.

[Gertjan]

@Gertjan

edit : Your other pool "pool_opt4_0" looks fine : 192.168.20.2->192.168.20.253

[mcury]

Hello Gertjan, thanks for the input.

edit : Your other pool "pool_opt4_0" looks fine : 192.168.20.2->192.168.20.253

It is correct, just one lease in that VLAN, all devices are known.
For OPT4, it is a GUEST vlan.

[Gertjan]

@mcury said in New pfSense Plus 25.03-BETA is here!:

It is correct, just one lease

Can't you give it some more space to breath ?
Just to little 192.168.10.15 to 192.168.10.16 ? ( /31)

ALLOC_FAIL_NO_POOL
+
ALLOC_FAIL_SUBNET
= fail as you entered a subnet thing (the /32) where an pool (barrier) was expected ?

How did you enter this pool ?
Like this :

login-to-view

?

[mcury]

@Gertjan said in New pfSense Plus 25.03-BETA is here!:

How did you enter this pool ?
Like this :

Yeap, exactly like that.

[Gertjan]

@mcury

What happens when you give it more space ?

[mcury]

@Gertjan said in New pfSense Plus 25.03-BETA is here!:

What happens when you give it more space ?

I'll try it, good observation.
As soon as I go back home I'll change it from 192.168.10.15-192.168.10.15 to 192.168.10.15-192.168.10.16 and I'll come here to update this thread with my findings.

[chudak]

@Gertjan said in New pfSense Plus 25.03-BETA is here!:

@chudak said in New pfSense Plus 25.03-BETA is here!:

No upgrade path 24.03 => 25.03?

I saw the same question somewhere already, the answer was : go to 24.11 first. You don't need to stay long there, you can then access the second Beta : 25.03.b.20250306.0140.

Btw : 25.03.b.20250306.0140 rock solid for me.
( not using pppoe )

I had issues with 24.11 and therefore decided to wait for 25.03. Hope it will be available in the final RC

[UweV]

Hello, where in this forum can I report feedback for this beta version? (2.8 beta)
Topic: Fixed: Old IPv6 addresses may continue to be used after DHCP or RA changes #12947
(included also in 25.03 beta)

Thank you.

[bmeeks]

@UweV said in New pfSense Plus 25.03-BETA is here!:

Hello, where in this forum can I report feedback for this beta version? (2.8 beta)
Topic: Fixed: Old IPv6 addresses may continue to be used after DHCP or RA changes #12947
(included also in 25.03 beta)

Thank you.

Here is the forum link: https://forum.netgate.com/category/102/plus-25-03-develoment-snapshots.

If you have a verified bug report along with information about how to reliably reproduce the issue, you can submit a Redmine bug report here: https://redmine.pfsense.org/projects/pfsense.

[mak73]

I am testing now also 2.8 Beta, PERFECT! THX

[jwt]

@mr_nets it's in this beta