on the FIRST interface (and only that one) called "LAN", there is an invisible "PASS-all" rule The rule is not invisible - it is an ordinary rule that is put on LAN in the default config. Netadmins can delete it if they like.

If it's a recent change, like the last thing you did, then using the configuration history to step back to before that change is the simplest way to get back to a working setup.

Which FreeRADIUS package are you using, the 2.x package or the 3.x package? If you are using the 2.x package, remove it and then install the 3.x package. Also, you appear to be running a MySQL server on the firewall itself ("Attempting to connect to radius@localhost:3306/radius") which is not possible unless you made unsupported manual changes to the firewall packages or installed a package from an outside source, which may have compromised/broken your installation in some way, leading to the error you see.

If you are using a "CABLE" provider you need the MAC address on the CABLE MODEMS WAN interface [ usually on a sticker on the box itself ].  You need to usually go into the PFSENSE and put this MAC address into the SPOOF MAC section on your PFSENSE WAN - OR you can call your ISP and ask them to put your modem in BRIDGE MODE.

You will need to show us what interfaces and rules you have set up so far. And let us know an example of what does not work (e.g. cannot ping from clientX on LANx to clientY to LANy). Some things will not work (easily, immediately) between LANs (like file share browsing) when they are not "routable" things.

Thanks for the info, I'm submitted other messages on the forum about the issues I'm having.  No luck on those being resolved yet, and I've been unable to get my P2P, Games, and other traffic to be properly classified and prioritized as they should be. Mark

For me, I would do the fresh install and restore the old config. Remember, the config is PF settings in xml format and really nothing to do with the OS, other than interface names and a few other things which in your case are the same because it's the same hardware, right?

I am not sure if I have done the correct thing however I noticed that the vEthernet (LAN) had a default gateway of PFSense so I removed it and change to DHCP, I also removed IP6 from all the Nics. Seems to be ok so far but only been up for 10 mins or so! Update: Up for over 2 hours and all seems ok

For the next person who finds this thread but it doesn't work, here is what I did: Verify you still have pkg-1.9.4_1 in your cache.  If not, then find a copy and download it manually. ls -l /var/cache/pkg/pkg-1.9.4_1 -rw-r--r--  1 root  wheel  2549424 Feb 10 21:20 pkg-1.9.4_1-de95a0ff9b.txz lrwxr-xr-x  1 root  wheel      26 Mar 27 21:26 pkg-1.9.4_1.txz -> pkg-1.9.4_1-de95a0ff9b.txz Then run``` pkg add -f /var/cache/pkg-1.9.4_1.txz It will complain about the DB version so continue the steps from Bismark's comment above about changing the DB version manually.

thanks!

Plus your SG-2220 into a LAN port on your FIOS router.  From your FIOS router's web interface, assign a static IP to your SG2220.  Finally, go to DMZ, set the static IP you just assigned, and click enable.  That's pretty much it.  All traffic will now flow through your FIOS router like it isn't there.

@PiBa: @theaudioguy: and it now works. Why do people keep replying to something already fixed ?? I'm not sure why hardware offloading would fix it so I replied with the expectation that if it stopped working he would have something to go on.  It could also help if someone came along with the same issue they would have other options to try.  If it's fixed, great.  If not we'll hear back and the conversation can continue.  It's no big deal.

@ricle: There is no abnormaly killed but after reboot it's still the old version! I don't have anything open, only the terminal is used. If you connect to the console and manually tell it to boot from the other slice, does it show the new version? If so, does it keep booting the new version after a reboot? @ricle: There must be a way to make upgrades saver because it becomes unuseable if every upgrade brings new troubles. As u can see in the posts there are many people with different troubles when running upgrades! That is one of the reasons we are removing NanoBSD. It was intended to help with issues such as this but it never quite did. Even back when it was first added there were issues and confusion at times which led to it not being reliable, and it never did quite get to where it promised to be. And because it gets run primarily on CF/SD media, some of the failures are bad disks, but some people have a hard time believing that since when the disk is rewritten it sometimes works (because the disk remapped bad spots when fully rewritten), and so on.

Thanks. You are correct, I was confusing the legend for messages.

Have the same problem. Your solution didn't help to me. Any ideas? UPD: Solved using this post

The "garbage" in your case was SoftRAID metadata from an earlier installation. The default kernel in pfSense probes for that metadata and if it detects a broken RAID array on the disk it's going to cause problems. There's a pfSense wiki article describing a workaround that can be used with the install disk/image as well to prevent the graid driver from trying to use the broken RAID metadata: https://doc.pfsense.org/index.php/Boot_Troubleshooting#.22Fake.22_RAID_cards_with_a_GRAID_error

VirtualBox is saying the VDI is inaccessible?  Maybe someone here can help pitch in but that's a VirtualBox issue, not pfSense.  You could try to regenerate the UUID for the VDI file or create a new VM and attach it if the VM config is messed up but you'll need more than "inaccessible" as an error.  It may say something like "Parent UUID does not match" or a result code of E_FAIL (0x8004005) which will give you something to go on.  Again, though, those are VirtualBox error codes and would need to be brought up in their forums I would think.