https://redmine.pfsense.org/issues/9541

@albgen said in Upgraded to 2.4.4_3 - system now unstable: Arrived today and i had a dead box. 'Dead box' is not a helpful term for debugging. Was it powered off with no LEDs? Was it totally unresponsive via console? Was it showing any errors? Did you reboot it? etc etc What happened? well i don't know, it seem this version(2.4.4_3) is braking something. And what have you seen that makes you believe this? I've been here for many years, and if I had a dollar for every user who complained about pfSense - only for the real fault to be bad hardware - then I could retire already. Never happened since using monowall and pfsense. First time! Like I said earlier, everything works until it breaks. As JeGr said, if you have a problem then post a new thread.

That's a question for a FreeBSD forum. They must have made some change in FreeBSD that helps it work on that hardware. Probably newer drivers in one area or another. You'd have to ask them to know for certain.

I upgraded the Bios on my APU2 bios to v4.9.0.5 and later to v4.0.25. On both these Bios versions the 2.4.4 installation progressed passed the xterm terminal selection point to where Auto(UFS) is selectable. Beyond this point a “Device Busy” error is reported and progress is halted. While on the v4.0.25 Bios I persevered with repetitive attempts at Auto(UFS) selection and eventually it burst through the Device Busy error and progressed to a full install. At this stage I have not tried to repeat this experience. PfSense has been operational for a day now with no adverse indications. My plan now is to battle test the current 2.4.4 installation for some days and when satisfied it is solid I will go to my second mSata drive with my penultimate 2.3.4 system still intact and then replace it with a fresh 2.4.4 install, trying to replicate the “Device Busy” error and explore just what is happening there.

Yeah "any" wifi router can be just used as AP/Switch by turning off its dhcp server and connecting to your network via one of its lan ports.. Some allow for bridging the wan port into the switch/ap bridge in AP mode... Others do not.. Be yeah any soho wifi router can be just AP and switch ports. Good idea to give it an IP for its lan that your going to be connecting it to so easier to manage your wifi settings.. Keep in mind that many native firmware for these devices don't even allow for setting a gateway on the lan interface - so you have to manage them from the network they are connected to. Unless you can put 3rd party firmware on them which allows gateway - like say dd-wrt.

Hi again, after trying several times, differen USB sticks and so on I had to chose another terminal than the default. Welcome to pfSense! Please choose the appropriate terminal type for your system. Common console types are: ansi Standard ANSI terminal vt100 VT100 or compatible terminal xterm xterm terminal emulator (or compatible) cons25w cons25w terminal Console type [vt100]: cons25w No I could run through the installer process

@Derelict Yep, that is what I'm going to have to do. Especially since the I can't reach the HTTP or SSH interfaces anymore. Just waiting for a USB to female serial cable to arrive.

@KOM said in Cannot log into 192.168.1.1: Good catch. I never would have figured that one out in a million years. Thanks again for your help.

@Jonathan-Elias said in Do not carry packets!: The DNS has already put the private and the public... Restore the original, default DNS settings : let the Resolver do the work. "Availabe Packages" will populate.

Thank you that worked.... got past this error anyways, and i dont expect any more problems as this exact machine has ran pfsense before, but not in my ownership. case closed.

What do you want to know dude, if your isp is locked down to prevent inbound traffic, there is nothing pfsense can do to fix that.. Run a vpn that supports inbound traffic if that is what your after.

If it's a moderate size disk then RAM isn't a huge concern. I don't have any specific disk size vs RAM consumption recommendations, but I've gotten away with ZFS even on some really low-RAM VMs when testing.

@kevin9033 said in Migrate Sophos XG/UTM to PFSense: Sophos UTM/XG I was also thinking to install pfSense on some old Watchdog hardware installation may be possible on some of them with a little hack but thought those hardware are too old to run the latest pfSense OS so decided to go with netgate certified / approved devices. I found a link regarding Sophos https://forum.netgate.com/topic/133355/installing-pfsense-on-sophos-xg-105-rev-2

@Derelict okay? The bug is restarting interface assignment after doing so

Actually I've learnt a lot form the guidance given here. But it has to be infuriating to deal with the problems of numpties who don't really understand how stuff works but non the less want to set up something which is beyond them. Cables are bought and changed about to check for errors tho not got a connection checker here. What I meant to be saying in my final note on the problem was that a good deal of time was wasted because I hadn't realised Id got a problem with dhcp on the client and restarting linux didnt flush the network if that’s even the correct phrase. sudo ip route flush table main – after which it got better -or maybe I just imagined it ;) Anyways, its doing what it should now - Thanks