I fixed the backup and restore by downloading the file from the master on Redmine. I'm still getting the javascript line appended to the config.xml before applying the patch. The patch worked, backups look good again.

Thanks!

If you are coming from 2.4.2 or 2.4.3, I would uninstall all packages first, then upgrade, then manually add them back once you are on 2.4.4.

If you follow all of the recommended steps at https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html you should be fine.

Through a packet capture on interface facing the radius server, I found that the ip address was malformed and radius server was dropping the access-request packet. This was a great discovery, as I found the line 218 in radius.php file is not the problem. I have been asking for NAS-IP-ADDRESS support in the Radius client for what seems like years. They finally added it to the Radius process as a valid attribute, but from what I can tell, it defaults to the WAN interface, which for me also happened to be dhcp. With the services starting and dhcp not yet available, the line 218 failed to find the dhcp address and in return failed on line 218.

Fix: Assign the interface facing the Radius server as the NAS-IP-ADDRESS, which is most likely your LAN interface and should be "static". This change should be done under System>User Manager > Authentication Servers > (edit) Radius Server> Choose NAS-IP-ADDRESS interface from drop down menu.

Note** Traffic from FW Radius Client sources from the egressing interface of firewall. This ip address does not have to match the NAS-IP-ADDRESS, but should be same for ease of configuration on Radius Server.

I have the same issue, last week i upgraded to 2.4.4-p2 from 2.4.4 on both my nodes but master now warns
"A communications error occurred while attempting to call XMLRPC method restore_config_section"

I tried to uninstall/test/reinstall pfblocker and snort without success.
Removing both services reports same XMLRPC error.
Changing pf rules on master replicate as usual on backup
Changing pfblocker rules on master does not replicate on backup

At the back i have several years of working HA since pfsense 1.2.3 and no conf changes has been made since then.
I think is a 2.4.4-p2 specific issue because i also had for weeks a well synced 2.4.4 with a 2.4.4-p1.

Any idea?

Looks like it didn't fully or properly upgrade from <= 2.4.3 to 2.4.4 or later. It has some parts of PHP 7.2 and some of 5.6.

From the shell, run pfSense-upgrade -d and see if it finds anything more to do.

Another thread on this topic I'm aware of:

https://www.dslreports.com/forum/r30908033-Bypass-Google-Fiber-Box-How-To-pfSense

Hope this helps.

@rico

Yes, lesson learned.

@nick13 - I figured it out. It appears after the switch from the USG to pfSense, my Windows 10 VM changed my network firewall settings within Windows from Private to Public. Once I switched it back to Private everything worked.

@KOM @Grimson @stephenw10 Thanks for your replies.

I didn't press Accept button because I wasn't sure if the boot had gone well.

Now, I want to know what are the benefits and the difference between an UEFI and a BIOS installation.

If possible, I'll upgrade the bios on motherboard to enable UEFI boot and fix some bugs.

Thanks

I was expecting 192.168.1.10 but it turns out .100 is the start of the DHCP range so that is actually expected.

I could have sworn it started at .10 but the default config files don't lie so it must just be what I set. Or I was somehow in a parallel universe! 😉

The actual cause of the problem was the subnet conflict between WAN and LAN.

Anyway I'm glad we were able to get you up and running despite my confusion.

Steve

You could but if the same switch port works with no change other than plugging the DSL modem in instead of the WISP connection then it probably won't help.

When you connect the WISP can you ping the gateway IP from pfSense?

Were you unable to ping anything even by IP, like 8.8.8.8?

Steve

Where in NAT? Outbound?

Yes, it is perfectly normal to apply outbound NAT to localhost addresses and whether or not it is a VM has nothing to do with anything.

RTFM: https://docs.netgate.com/pfsense/en/latest/book/routing/gateway-settings.html#monitor-ip

Thanks for the help. I upgraded to Windows Pro to use Hyper-V. Same setup and everything is working fine.

I was very hopeful this would fix me, but it did not. Same issue trying to go from 2.3.4 to current. Doing this actually made the issue slightly worse in that before I could at least check for updates and now I cannot. Sounds like I might be stuck with a config backup/fresh install/config restore situation now unless someone has a better suggestion.

your pfblocker and other packages have to be OLD as shit as well... Since packages for 2.2 died a long time ago..

Sorry but no I don't get its working ;) Not when it comes to your security devices.. They need to be kept up to date if you expect to be secure.

See it all the time with users, Antivirus is from 3 years ago - but it was working! <rolleyes> Sure it was ;)

@gwaitsi said in 2.4.4_p2 unable to retrieve packages:

so smarty, why is it unable to retrieve packages

PEBCAK, very obviously.

We are aware, IPv6 access for those hosts should be back up in the near future.

Completely reboot
No crash report, I have to connect serial port and check the output.
thanks

Yes, once it has recovered the config it returns to the install menu so you can install using that.

If you have a backup of the config file anyway just go ahead and install there. You can always restore the config after install if you have to.

Steve