@tibere86
Create a file called "loader.conf.local" in the /boot folder. That will stay between reboots.
I use WinSCP to attach to the FW and create/edit because it's easiest for me.

@deanfourie

Start here : Upgrade Guide. This page will lead directly to other pages with solution.

@1eo
How should you get the WAN IP? DHCP or PPPoE?

What shows pfSense in Status > Interfaces for WAN?
What shows pfSense in Status > Gateways?

What tells the system log?

Mmm, but if you are putting the LAN and OPT ports in the same subnet (like a 2 port switch as you said) then the OPT interface is no longer required.

@jollycloudycheergoose as mentioned, keep everything simple to start with just to make sure things work as intended. Then you can start to tweak things until they are set up as you want them. Importantly, pay close attention to what you change so that you can revert if things don’t work right.

We’re more than happy to help and I don’t think any of us means to beat you down. There IS however something to be said for posting a problem you are having and asking for help, rather than declaring that pfsense is broken. 95% of the issues I see posted on the forum end up being user config errors or misunderstandings in how things works, though many users like to blame pfsense right out of the gates.

Best of luck on your technical journey. Hit us up as you go!

@jollycloudycheergoose said in pfSense ruined my non-pfSense router:

why it isn't working when alternating

If your cable modem - and you change the "rouer" or pc connected to it - you almost always have to power cycle the cable modem.. Because the mac address has changed.. Unless you clone the mac of the devices so they are the same..

Cable modems don't like it when the devices mac connected to them change.

@TheRAt , @johnpoz
Enabled 2FA and configured the app password. Entered the app password into the Notification E-Mail auth password field. It now works. Thanks for the direction. I appreciate it.

You have to set the Level of Detail higher to see MACs displayed. Note that doesn't change what is actually captured, only what the pfSense GUI shows you.

Steve

Could be stale states somehow. Try clearing the states if you haven't already.

When you bypass pfSense and that allows it to connect what exactly are you doing? You have a wifi network that bypasses it?

Do you have IPv6 on your network?

Steve

What config are you importing? What version? From the same hardware?

When you import the config via the gui the config upgrade scripts are run against it.

If you need to import a config I'd recommend using the external config locator via USB (if you're local to it). https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-ecl

Steve

@stephenw10 I managed to fix the problem, but it seemed haphazardly. I tried installing pfSense 2.6 by DVD only to realize that the previous memstick method did install the firewall OS despite no OS found rebooting the computer. Then, booting from the DVD would start and hung on synchronizing user. So, I made sure that the bios were set to legacy mode and CAS was disabled then booted the computer. This time it hung on CSM; so, I powered off the computer and reboot again and select single user mode and created the file as you had instructed:
echo 'kern.geom.part.mbr.enforce_chs=1' >> /boot/loader.conf.local

It then completed the boot up, and I could restore backup configuration. We'll upgrade to version 22..5 when my friend return from vacation. Thank you Steve.

Well, late yesterday up till 19 minutes and 44 sec pass midnight, we were getting lots of sent to error 65 and some latency alarm; so, this morning spoke with ISP and it was their fault doing some update. We have fiber and no modem. It appears all is good.

Hmm. Weird that it's not showing queries in unbound though. Seems like however it's failing could be because it's not going via Unbound...

Hmm, the BOGONs option by itself should not have blocked it unless the subnet you were using is outside the usual RFC1918 private subnets. The 'block private subnets' option would have of course.

Indeed it was my wireguard script messing with this. Once i removed it, things are back to normal.

@stephenw10 yeah i forgot proxmox supports 'vmxnet', I assume its not as optimised as it is in esxi, but I do wonder if a multi queue 'vmxnet' on proxmox is more capable than a single queue 'vtnet'. It will be interesting to find out.

Undecided at this time. You could always roll back or switch to 2.7 if you need to though.

That's a side effect of how schedules are handled these days. The methods of fetching rule labels are not quite right there, but it's fixed on snapshots:

https://redmine.pfsense.org/issues/13155 -- that alone wouldn't apply to 2.6.0 since there are a lot of other changes around after 2.6.0 there. Though schedules are not mentioned it's the same root problem since schedules are handled through an additional rule labels on 2.6.x.

Not personally. I'm sure there are many others here doing similar things though.

Steve