Reading the guides we have posted is the best bet. Verify your hardware will work with 2.4.4-p2, we no longer offer support for 32bit OS, nor Nano images. When that is done, I would suggest doing an install and restore: The fastest path to getting onto current with less issues will be to take a backup right now (Diagnostics -> backup and restore, download XML). Downloading the latest/greatest, install, and recover. Depending on hardware this will be under 15 minutes. If you go the upgrade route you might be waiting over 30 minutes depending on what's going on.

Thanks for the reply sorry I wasn’t clear the other config was for a PF sense box that I have that is already up and running I was hoping I could put the config on the system that I couldn’t get to access the Internet and try it that way even with the config from the working PF sense box it still was not able to connect to the Internet at this point I’m at a loss I reset the config several times the only thing that I haven’t tried yet is downloading a fresh copy Any other ideas? What would a good firewall entry look like

@gertjan said in Users on the LAN network do not surf the internet: Hoho : No bad mood at all on this side. All reflexions are here to help you. Remember : we all have been there - and most of us seen it all already. We're all expert in doing this fast, good and stable (so you can pass on to other things fast !) Thank you so much for your encouragement. I also thought about abandoning Virtualization, because that's the problem in my opinion. Thanks again

Okay, I'm reading everything documentation, but squid is not working. my version is 2.4.4-release-p2. I thought I had to upgrade squid

pfSense is not configured to support multiple disks other than hardware raid or geom mirrors (or ZFS pools). There is no provision to mount additional disks in the GUI. It has been done before but some custom scripting is required to make sure services relying on additional disks are handled gracefully should the disk not be mounted for example. For logging you can install the syslog-ng package and specify the storage location on another disk. Then export the pfSense logs to it. Again though you can edit the fstab to mount that but it may be overwritten. Hosting a syslog server externally is the recommended way to go. Steve

Which SSD type is it? mSATA or 2.5" SATA? If it's mSATA be sure the slot you are using in the other machine is actually mSATA and not mPCIe. Steve

@jimp , much appreciated! your old post made here Re: Packages disappear overnight after system restore led me to the solution straight-away. It was driving me nuts. For me the browser auto-filled in the "System-Advanced-Miscellaneous" proxy info. Thanks again!

Hi, Yes I had tested it multiple time, but you can guess what, it works now :( I dont know what else to say Thanks

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