Sorry about not point out an error. For starters. Heres my error for just running pkg update [2.4.4-RELEASE][root@firewall.example.com]/root: pkg update Updating pfSense-core repository catalogue... pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: Network is unreachable repository pfSense-core has no meta file, using default settings pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: Network is unreachable Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/meta.txz: Network is unreachable repository pfSense has no meta file, using default settings pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/packagesite.txz: Network is unreachable Unable to update repository pfSense Error updating repositories!

@KOM I'm inclined to accept, that he is talking about a cluster setup maybe and the device does not have direct internet but only via its cluster member/master or some other router so that it doesn't has active internet when not on duty?

Static IPs are very rare for PPPoE. Even more rare are links with no gateway specified. If you need to use a custom mpd config though a conf file in /conf will be used in preference the generated one in /var/etc as you found. Steve

as i said i don't use haproxy so you need to test this out create backend : Address: you put the webseerverip you have [image: 1562494203016-backend1.jpg] create one for every webserver you have [image: 1562494223973-backend2.jpg] : then you go to frontend and create acl and action: [image: 1562494806968-frontend1.jpg] pls do not pm me i'm not helping for money donate it to netgate forum / buy a service or an appliance when you can afford it, from them / buy a new car for johnpoz / donate it to some charity have a nice day

@bmeeks Made contact and opened a ticket. Thanks to the forum. In the end went nuclear and re-imaged device. Looked like the file system was off some how during reboot. All done. Will watch for hardware issue. But think this may be an isolated case. Cheers.

Thank you

@CompProbSolv said in Can't change WAN Config Type (invalid IP.. PPPoE Password...): As it sits, it's still on DHCP and "admin" appears in the "reject leases from" field. I've looked at the config.xml file and find the line: <dhcprejectfrom></dhcprejectfrom> I expected to find "admin" in the middle of that. We had sth. quite like that on another topic. Problem was the users browser and saved credentials that somehow always got auto-inserted when he visited the WAN interface. Seems like a Chrome (not Chromium/Firefox/Opera/etc.) specific problem with its password manager running haywire on fields that have nothing to do with passwords.

That did it. Up and running with ZFS. That installer is really confusing. Many thanks.

Now that a few months have passed I'm wondering how ZFS is working out on low powered hardware like the type listed above (Celeron(R) CPU J1900 @ 1.99GHz/4GB Ram/Single mSATA SSD)? TLDR; Current system resource usage is very light My current memory utilization is about 25%, Disk utilization is about 8%. I don't know how to measure maximum CPU Usage, but I suspect it is pretty light as well since the network just a small home network (most I've ever been able to observe is something in 25-30% range). Any issues with excessive resource usage? What about with a single SSD with no redundancy? Anything else to watch out for? I'm using ZFS on FreeNAS, and even on Linux, but that is with much more powerful machines with 32GB of RAM and redundant storage. ZFS has been great-especially snapshots with the ability to "rollback"-that ability would make upgrades much less stressful if an upgrade could be reverted with a single rollback command. Any comments much appreciated.

@johnpoz @stephenw10 got it to work! i updated the main threat... basically yeah i had port 1 on port 8 anmd port 8 on port 1

Thanks for your feedback ! I have to put the routeur in production next week so I'll be short on time to try new pci cards. I'll set up a 4x1gb LAGG for the LAN. It should be more than enough :D

@dragoangel @viragomann The problem is be squared away and thanks for all the pointers!

Thank you, Sir! It is now connected

it can be don with a single nic and a vilan cabable switch. It's more to leran but its än alternative if you cant get a card

@benman No offense taken - just curious :)

@netblues said in Upgrade from 2.4.4-p3 to 2.5: @NollipfSense And it was good they did. They benefit from much better vpn encryption performance. The fact that dropping support for non aes-ni capable hardware could make the community smaller jeopardizing the longlivity and future of pf, is a far bigger problem. In this case, have two versions for a win win. The new folks who just spend money upgrading could quickly jump ship limiting pfSense growth potential.

I would reboot the pfSense and when it completed, then reboot/repowered your CenturyLink modem. You'll then obtain an IP address for WAN.