No worries, I will go back to the 2.4.4-p2 ( that is the netgate image I already have ), then get to 2.4.4-p3. I was testing a few things with 2.5, I have no need to be on it any longer. I had planned on going back to 2.4.4, this just moved it up on the list.

Thanks for the reply.

Thanks Jim, If you need any data from my system, logs, traces etc. then feel free to drop me PM.

I rebooted pfsense and seems to have fixed issue

@jimp Thanks! Much better now :)

@kiokoman - thanks, looks like apart from doing the DHCP request via IP4 it was all preset and ready to go out of the box. :)

Having wiped the machine the problem seems to be sorted.

@jimp I've just updated, tested and yes it's fixed.

Download it and try it?

The list of issues open against 2.5.0 is here:

https://redmine.pfsense.org/projects/pfsense/issues?query_id=104

Once it is released you can switch your branch back to stable and it should pick it up from there.

@jimp
Works now, thanks.

I didn't feel like climbing over my desk and shelves to get to the window where my GPS is when testing to move it or block the signal to reproduce the problem, I just made sure it worked fine before and after the changes I committed to fix it. :-)

Thanks for the reply, issue #9561 has been submitted. I reviewed #7272 before looking for helpful debugging information. Issue seamed to focused on the gateway monitoring. My issue seams to centered on establishing the ipv6 address on the wan_stf interface. Monitoring won't work until the interface is up.

My IPv6 is also PPPoE based. It works on 2.4.x and on 2.5, but if do not disable it before upgrade than I have two scenarios — update stuck on the first stage and never continues or update starts, take hours to complete (extremely slow download!) and just ends with corrupted installation.

UPDATE:
Did 2.4.4-p3 upgrade to 2.5. Success!

@jimp

I had to roll back to 2.4.4 for operational reasons, so I guess the log's gone.

Not sure what the nmbclusters is you refer to. Under 2.4.4 I never had to do anything: installed software, and all interfaces were recognized.
Under 2.5 installed software, and the only thing it sees is em0, em1-em5 are like they aren't there.

I've now switched from using that system to my new MBT-4220 unit. I could try, after that proves stable, to wipe the FW-7535F clean, install pfSense 2.5 on it, and make it available on a public IP address, so you could have a look, if that should be helpful.

So I was able to find another way to keep nat reflection turned on and stop the spam. I changed one of the port forward rules from tcp/udp to separate tcp and udp rules. It fixed the issue. tcp/udp port forward rule might be broken.

I was going nuts with this issue in my lab until the light bulb went off. I had left the block private networks checked.

No. And please post separate issues to new threads.

@tandyuk said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:

Just had a very similar, if not the same problem today, after deciding to test out 2.5.

From 2.4.4-p2, using the gui to upgrade.
System rebooted, but threw all manner of issues on the boot, leaving the system broken.

Root cause was at some point during the initial boot php-fpm crashed, and tried to write its core dump to /var/run/php-fpm.core
/var/run however is a 3.4MB ramdisk, so it failed to write the dump, and subsequently a lot of the upgrade process failed due to lack of disk space.

This sounds like a different issue. I never heard about php-fpm crash during upgrade before