@stephenw10 Thank you Stephen you saved me . I was like banging my head here and there, Thanks a lot ..

@masteradde Hi Guys, ok Are you ready for this! I was having the same exact issue and I was able to fix it! I don't know how I fixed it because what I did was a complete mix up of steps that are not in any beta that I have found. So What I did when I got this picture as seen above. Go into Machine setting and click on reset. Re-install pfSense ISO image. pfSense-CE-2.4.5-RELEASE-amd64.iso.gz Go to this link and follow these steps [https://technicalustad.com/how-to-install-pfsense-in-virtualbox/](link url) Once the install is complete from bios boot up hit reboot (do not force unmount yet) Once it reboots go through the process again. When is ask if you want to reboot, then "Force Unmount" Then click reboot, then you will get error messages. (no worries) Either turn the VM off then or simply click on the Machine settings and click reset. This finished the Bootup process for me and took me to "pfSense dashboard" where you can then configure interfaces and ip addresses etc... I'm not sure why this worked because it has nothing do with installing the software, it seems like their is a glitch in the boot up process and doing things in this "exact way" fixes it. At least it did for me. I don't understand why its acting this way, because I installed two pfSense VMs on my laptop and did not have this problem. It always get weird if you "Force Unmount" at the wrong time. Maybe that is the answer. I remember seeing YouTube Video explaining when to "Force Unmount" I hope this helps, let me know if you have any questions and maybe I can help!

@dlehenky said in Does the SG-5100 run v2.5 well?: And you're a politician No need to start calling people names ;) hehehehe ROFL...

@teicee This worked great!

@gertjan nothing comes up, and card does work in Linux...

@gertjan Thanks. I could not have my whole house without internet because the Netgate router bricked itself trying to update, so I went out and bought another I hope is more robust (a Ubiquiti). Perhpas some time, if I have time and interest, I will reinstall everything to get that one back up and running. But with all that is going on right now, my internet access is too critical to be playing games trying to figure out why the piece that connects the house to the outside world quit working.

@gertjan Well, that was it, a bit emberassing. It switched to the old revision for some reason. I never touch the branch field, I ususally don't even use that page as I run a script to notify me of updates. That's how I missed it. Wonder how that happened... Anyways, works again, thanks! Tobias

@ecottd The initial setup consisted of what ? Your 3100 is connected to what type of upstream device ? A modem ? Another router ? Can you show the console menu, like : Passphrase for key "rsa-key-20150201": pfSense - Netgate Device ID: b87955xxxxxx42af9fa0 *** Welcome to pfSense 2.4.5-RELEASE-p1 (amd64) on pfsense *** WAN (wan) -> em0 -> v4/DHCP4: 192.168.10.3/24 LAN (lan) -> em1 -> v4: 192.168.1.1/24 v6: 2001:470:1f13:5c0:2::1/64 PORTAL (opt1) -> em2 -> v4: 192.168.2.1/24 HENETV6 (opt2) -> gif0 -> v6: 2001:470:1f12:xxx::2/128 OPT3 (opt3) -> em3 -> OPT4 (opt4) -> bge0 -> OPENVPN (opt5) -> ovpns1 -> v4: 192.168.3.1/24 v6: 2001:470:ccea:1::1/64 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: The GUI works ?

@stephenw10 Anyway the hardware failure happened because I was installing pfsense. When the installer offered me making the last acceptance which was “ok” then I activated and the black screen is appeared. I went to an repair store. They are guessing 99% the motherboard is dead.

Some pics might make it clearer hopefully. Again, I have no control over anything in the Internet or green 'Prod' areas on the diagrams. Base enironment [image: 1606801554010-test-base.jpg] Current setup (1:1 Nat) - AD slow and DNS not working, high maintenance). [image: 1606801638391-test-nat.jpg] Preferred setup (Bridge / flat network). [image: 1606801721623-test-bridge.jpg] Getting the bridge to pass traffice between the 'Lan' ports and the 'Wan' port seems to be problematic (it is not working). Test PFSense setup [image: 1606802635974-test-pfsense-setup.jpg] A couple of questions after drawing all this out.... What interface should the bridge be assigned to ?. Should the IP stay ont he Wan (VMX0) or the bridge if I am filtering on the interfaces rather than the bridge. Hope this is a bit clearer. Thanks

@viragomann yes I have an ubuntu image that works just fine but when I added pfsense, i couldn't access any web pages except the gui of my router

/23 not uncommon for a public IP from isp.. What did you think you should have? /22 or even /21 not all that uncommon..

@stephenw10 Thank you, this is an important answer, too.

@Df1988_2005 said in New install - Default creds accepted but stays on login screen: v6 routing for internal preferably with OSFPv3 pfSense also to run upon relatively low-performance "iron", but don’t think that, we can to strangle into a VM environment which is only (1CPU / 1GB) OSFPv3, hmmm, if you want fast routing you have to increase the performance (definitely)

@linedan said in Problemes upgrading from 2.3.4 and install of packages: somehow could install the openvpn-client-export-package! Example : check out pfSense 2.4.5-RELEASE-p1 Now Available [image: 1606466395082-9ac4317f-0f54-4f38-b56a-865c3a719c0d-image.png] As the Netgate blog already states with any pfSense upgrade : IF there is a pfSense upgrade available, install that first. Never ever upgrade packages after a pfSense upgrade came out. As you can see in your image above, your pfSense is based on FreeBSD 10.3. Or the repository mentions it's based on FreeBSD 11.3. This means FreeBSD packages (for pfSense) and packages for pfSense that are pulled in are based on 11.3. They will have dependencies that won't work out. For example, a PHP library that is compiled against FreeBSD 11.3 will not work on a FreeBSD 10.3 system. This means : the GUI will go down. So, no "openvpn-client-export-package" for you : the risk is to big. I advise you to have the box send over to you. Or find some one on the other side that can do a bit more as n clicking "Like" on a screen, and you guide this person. Go for a re install, as cleaning out a system with a 'mixed identity' is possible, but very time consuming. It also needs a great deal of knowledge of the OS. I understand that, because of the distance, you won't upgrade every time when a new pfSense versions comes out. It's ok to wait a couple of weeks or even months. But hanging around with a 2.3.4 creates new problems. Knowledge about that version has faded out (on the forum )... I strongly advise you to look around on the forum. Others popped up with upgrade problems from 2.3.4. Some found solutions.

You should look at: https://redmine.pfsense.org/issues/8355 Specifically the last post I just made about NanoBSD being deprecated which leads you down this goatrope path.