192.168.x.y range are non routable. Having that on your WAN interface is bad.

Dated comp is not a problem, I installed and ran on a 15 years old single core Pentium3. My feeling is, pFsense works good with generic, non-custom PC, and you did not volunteer what brand, if any, this dated PC is, and Mr. Obvious would want to now, if this PC a WORKING PULLED, meaning it was working perfectly right before you decided to install pFsense or it, or you just found something at the garage sale with unknown history?

Just noticed the badly photoshopped antenna removal from that image.  ::) Steve

@Gertjan: I'd would like an explanation of this one : route add default y.y.y.y Although the OP mentioned this in terms of DNS resolution, it's more basic.  It adds (temporarily) a default IP route (aka default gateway).  Without routes you won't reach anything, let alone an upstream DNS server[1].  Drilling down further, you'd also want to verify that your WAN interface has a valid IP address, netmask and is UP.  Useful checks: ping y.y.y.y ifconfig -a [1]<pedantic>unless they're on local subnets</pedantic>

The supported solution there is to backup your config, re-install to the SSD and restore the config. Then you can increase the log file sizes significantly. Running two disks (other than as a mirror) is not a supported configuration but it can be done. You need to mount the other drive at boot. fstab may be overwritten. If you use the syslog-ng package you can specify the log location and then export the logs to it from the logging settings. I'd choose option 1 though.  ;) Steve

i fixed by running "pfSense-upgrade" command. It saw kernel needed updating still and pushed it through.

I sent a support request to Netgate and I very quickly received an RMA to return it to them - I'm impressed, I wasn't expecting such a rapid response.  I'm going to Fed-Ex it back to them. The speed at which the RMA came though suggests to me that they think it's a hardware issue, not a software issue.  I'm happy to say that it's out of my hands now and I can get back to my day job - LOL.

One of the best things I ever did was REPLACE Cisco/Linksys RV042s with pfSense.

I would boot from a 2.3.5 USB drive. Don't reinstall. You should be able to mount the disk using the emergency shell, edit the file, then boot from the disk. Might be easier to just install 2.3.5, edit the file, upgrade to 2.4.2, and restore a config backup if you are not familiar with how to do all of that.

The pfSense box replaces your existing router and also can take care of DHCP and DNS. In your case, the ethernet from the ONT will plug into the NIC that you identify as the WAN interface. This is my exact setup as well. Just be sure to release the DHCP lease prior to disconnecting the edgerouter. Not sure what you are trying to do with the VPN, but pf can also serve as a VPN server for you… The Ubiquiti AP can still serve as your wifi AP--I do the exact same in my setup.

I just got off the phone with the Cable company here in Delta BC, and their statistics for my modem for the past month, show packet loss to the extent that front line support was extremely apologetic. My fault again for not pressuring Cable support, previously, as they have me flagged as "has own router" (pfSense) - therefore customer is not eligible for support.

Hey, thanks for ur suggestion. By chance I try again and I boot from EFI mode and thats do the trick. Now its perfect with my new hardware !  :) :)

That's just an APU1, right? I'd recommend putting an msata in it, and doing a full install.

OK, I will leave it well alone.

Here is the fix…. Go to System > Update, Update Settings change it to 2.3 stable, let it do it's thing, then change it back to 2.4 stable.

I finally got the backup to work after editing it and some trial and error. At first, I thought removing the problem parts of the RRD data referring to opt2 would be enough, but the error would just move to a different line. I then noticed that the second rrddata node had two nodes for opt2 while the first only had one. I deleted the entire first rrddata section and was able to restore the config. However, after reboot, the web UI and console got messed up again for a different reason: During restore, pfsense reinstalls the packages, but it doesn't seem to install the right ones. At first I thought it was partially due to pfsense not being up to date. At the time, the current version was 2.4.2-1, but the version downloaded from the site was 2.4.2. Updating to the latest version first didn't make a difference, however. I had to reinstall the packages manually, but that wasn't a big deal because their configuration was restored. Thanks again to everyone for the help.

Thank you! Accidentally had Stable (2.4) set as the target while upgrading from an older 2.3.X release. Had to run the pkg-static clean / install commands to get things back on track from a partial 2.3.2 -> 2.4.X upgrade attempt in console. I rebooted after switching the update branch to "Security/Errata" to get to latest 2.3.X, and ran the update in the console and was able to get to the latest 2.3.5.  Then switched back to Stable update branch, before finally upgrading to the latest 2.4. A reboot between setting the update branch each time seemed to help, but maybe wasn't needed.

@Nhiel23: After configuration my computer connected to pfsense can access to Internet but the problem is I can't ping yahoo or even my LAN-gateway. The first four words indicate a potential problem factor. Every PC on planet earth has a DHCP client activated by default. The 99 % other devices also. So it will obtain an IP/DNS/Gateway as soon as plug in the Ethernet cable. Why did you have to configure your computer ? What is your LAN-Gateway ? 192.168.3.1 ? If not, detail your config - show us an image - do not hide details. Show also the result of a ipconfig /all from your PC. pfSense : Interfaces => WAN, Block private networks and loopback addresses must not be checked (192.168.1.0/24 is a reserved for private network)