Now Seagate will hate you… they wanted to save the planet!!!  ;D ::)

Uhm… that is a legend. https://redmine.pfsense.org/issues/7203

"How do I set things up so all ports are working?" Pretty sure like 99.999% until you setup stuff that switch will act just like any dumb switch.. All ports in vlan 1.. What Kpa already stated ;) What specific model do you have - there are a lot of them.. Yeah says so right on their page - if you want to use it as dumb switch you just plug it in.. https://www.netgear.com/images/datasheet/common/202-11700-01-WebManagedSwitches-UM.pdf Configure the Switch ProSAFE Web Managed (Plus) Switches are Plug-and-Play, so they can be used without any configuration. Just connect power, connect to your network and to your other devices, and you’re done. You can also configure and manage additional advanced features of the switch either by using your computer’s web browser or by installing the ProSAFE Plus Utility on your Windows-based computer.

@jimp: Look in your boot log, just above the mountroot output. It shows the disk was detected as "ada0", and it's trying to mount ada4. Try mounting "ufs:/dev/ada0s1a" and it should work. You will need to fix references in /etc/fstab and then perhaps once you get that fixed and you confirm a reboot works, run /usr/local/sbin/ufslabels.sh to convert your fstab file over to ufs labels rather than using device names. Or reinstall 2.4 with ZFS and leave UFS behind. Great catch - something I overlooked when looking at the screenshot. I'll give it a shot. Thanks!

yes actually, on my first install i've left the default settings of the console, i didn't know that will cause such problem, So i've reinstall it and choose the right console settings. thank you  :D stephenw10 your analysis was correct.

There was some squirrelliness in the pkg format in early 2.3. Did it not work?

Hi ablct, Are you able to get this issue resolved? We run into the same issue. Thanks.

@jimp: You can't reliably* downgrade in that way. You are now on a later release. If you want to move backward you have to reinstall. You might be able to switch back to the stable release, run "pkg update -f" and "pkg upgrade -fa" but be prepared for trouble. "-fa" is not a valid option for me on 2.3.4-DEVELOPMENT: I somehow updated to 2.3.4 and would like to rollback to 2.3.3rc … so I found this thread. EDIT: never mind, I chose a reinstallation

Thank you, Phil Davis, for your reply. At least now I know I haven't done anything wrong and that the bug has already been solved in the next version of pfSense. As I said it is not a huge problem to begin with. I swear I did look at the "issues" page but it was a bit overwhelming and I was not able to find the one you mentioned.

Yeh, the default settings have DHCP on LAN with a pass all rule for traffic originating from LAN side. I guess you did something odd when creating the VLANs the first time and re-assigning interfaces to the VLANs.

A vpn connection on pfsense is just amounts to a different gateway you can policy route whatever you want through that gateway.  As to inbound from that connection - yes you can limit what it can talk to..

@chpalmer: no one here has figured out the crystal ball we stole from the weird looking lady at the carnival.. I think I know the problem. My gramma mentioned someone stole her personalised lawn bowling ball. Funny that. p.s. beware she is really pissed. >:(

Did you register your device? https://www.netgate.com/register/ Once you register your device (which is free) using its serial number, you get a login to the portal which has a link to the firmware. The "CCCC" repeating string is the BIOS waiting for a serial upload of a working boot environment. You should be able to write the firmware to an SD card and boot/reinstall from there as the FAQ suggests.