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

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)

Thanks Gertjan, after applying the patch error seams to be gone.

@yarick123:

Hi,

I had also some troubles during upgrading i386 NanoBSD from 2.3.4_1 to 2.3.5 . One of them was missing "Legacy stable version (Security/Errata only 2.3.x)" branch.

Solution: I switched the Firmware Branch to "Development Snapshot (Experimental 2.3.x)", saved the changes and checked for upgrades. After this procedure I could select "Legacy stable version (Security/Errata only 2.3.x)" branch. After saving the configuration, new updates were recognised.

Regards
yarick123

P.S. Yes, I got 2.3.5 and 2.3.5_1 on my i386 NanoBSD.

@Gertjan:

@Waqar.UK:

I understand, the Asus is in the front line.
Also, why I cannot connect my pfsense box to my wan port instead of lan port?

Where did you hook up this Asus box (the AP) ?
I understood : on the pfSense LAN - as one of the devices on your LAN - like PC's, printers, etc.
It's an AP, thus that is where it belongs.

On the pfSense WAN side you have tour "ISP" box (also a router), that's it.

pfsense LAN port to Asus.

@jarmentrout@kidsrsu.org:

it booted, now on 2.3.6-Development

There is nothing newer then that version - if you use the 32 bit version.

Undoubtedly it's a hardware problem of some sort. It could be having trouble reading the disc, there could be a memory or other problem causing a corrupted read, or corrupted data in memory, or any number of other issues. That hardware is probably far too old to be used effectively.

You don't do anything with the modem apart from disconnecting your home hub and connect the modem in its place.

Then change the pfSense WAN connection to PPPoE, but I think you'll need a BT ID & password.

https://forum.pfsense.org/index.php?topic=136545.msg747008#msg747008 << maybe look at this for the userid & password.

^^that. You might want to exchange the Realtek for an Intel NIC and speed should go up.
At least if your CPU can still cope with it.

Thanks man, this is exactly what I was looking for.

This entire forum is great. Thanks all

But the wrt3200acm is capable of switch and wifi at the same time it can be done but I am new on this Cain of things