After hours…. I found solution: https://forum.pfsense.org/index.php?topic=51618.msg276125#msg276125

anyone?

Firstly, have a backup of your config, then: If the base FreeBSD and pfSense script PHP… files are fine, but you just made some config change that messed something up, restore the known-good config from backup. If files in the base FreeBSD or pfSense scripts... are gone wrong (deleted, corrupted, disk hardware problem...), then do a full install, then restore your config. (If the base system has been corrupted in some way, there is not much to be gained messing about trying to get back the files you know are deleted/corrupted... You will never be quite sure if everything is right. Much easier to just reinstall and restore the config.

ddwrt, open wrt, or tomato wrt on those ideal for wifi APs. pfsense needs a pc @ x86-64

@zeroepoch: Just in case anyone else had the same issue I had with NAT reflection not working after checking the 2 boxes and selecting pure NAT check your aliases.  I was using a hostname for the alias for my NAT rules and my guess based on the pure NAT comments is that it didn't know the IP at the time it was creating the reflection rules?  Less convenient to have to maintain the alias and the DHCP reservation but it worked.  Something to look at if you're having problems I guess. This was my issue as well. Put an IP address in the alias instead of a host name, and problems disappeared. Does anyone know if this is a bug or expected behavior?

Ah sorry I misread the model in the title here. The X-Core boxes are pretty ancient though. Nothing special should be required to boot that other than using the correct image and possible a smaller card. Running as a VM will almost certainly be far more powerful than the X700. Steve

And on another note - after you've fixed the conflicting subnets, you'll soon notice that the whole network design is completely broken with the virtualization you put in place. For the complete picture, my router is set to recognise a series of fixed IP addresses from their Mac addresses in the fixed range of 192.168.1.2 to .200 plus .250 to 254 with DHCP having reserved addresses (for visitors) in the range 192.168.1.201 to .249. pfSense is supposed to be your router. And it will not do any useful job when all your LAN machines are on pfSense's WAN side. Also, double/multi-NAT sucks.

the config (probably) doesn't actually reset. I think its more then likely, somthing as the following is happening: old nic naming: -em0 (mac-address = 00:00:00:00:00:0x) -em1 (mac-address = 00:00:00:00:00:0y) new nic naming (after adding) -em0 (mac-address = 00:00:00:00:00:0z) -em1 (mac-address = 00:00:00:00:00:0y) -em2 (mac-address = 00:00:00:00:00:0x) yes i'm aware mac-address' can't have an X/Y or Z ;) In any case, when such a re-ordering occurs, pfSense detects this and needs to run the assignment wizard to make sure WAN & LAN are mapped to their correct physical interfaces.

Just to update this post … I recently installed 2.3.2-p1 on an old PC Engines ALIX 3D2 board. Much to my surprise the GUI works amazingly fast and I will update my other ALIX installs in the field. Write speed of the CF cards makes each update quite painfull though.

Well, about an hour after posting this, and after I'd already gone to sleep, it finished and sent me an email. Not sure why that update status page never progressed further (its gone now, back to the login screen after the auto-reboot). But the Status page does report its on "2.3.2-RELEASE-p1 " Cheers.

Yep, it turns out the problem was caused by all the DNS server entries config going away for some reason.  It's odd, because some resolution was still working…some IPs on the states table were converted to host names. All other connectivity seemed to be working fine.  Along with at least some host names in the state table (not everything will reverse), I didn't suspect DNS until I tried a few manual "curl" and "fetch" commands.

Yes, the "ADI" install files are the correct ones. The other installation media would not present a usable console so it's fairly obvious it's the wrong one. If it boots/installs/runs it's OK.

That. ^ You need to use the 32bit image on an ALIX board. Steve

I am having the same issue today, trying to restore the factory CentOS to a RCC-DFF 2220.  Tried multiple times using both USB from here as well as iPXE from http://install.netgate.com/rescue/CentOS7/centos7-rescue.ipxe Anyone have any ideas??  edit: here's a screenshot of the console output [image: 0tjDZZN.png] edit2: I tried another method that I had notes on from somewhere… this resulted in a slightly different but equally catastrophic failure (screenshot below) # initrd http://firmware.netgate.com/netinst/CentOS7/images/pxeboot/initrd.img # chain http://firmware.netgate.com/netinst/CentOS7/images/pxeboot/vmlinuz console=ttyS1,115200n8 ip=eth0:dhcp ks=http://firmware.netgate.com/netinst/ks.cfg inst.cmdline inst.text inst.headless net.ifnames=0 [image: CXSlUDO.png] I have that "/run/initramfs/rdsosreport.txt" file attached here as well. rdsosreport.txt

@KOM: Usual steps to make a generic wifi router an AP: 1.  Unplug/disable WAN 2.  Disable DHCP server 3.  Set LAN Static IP outside DHCP range 4.  Plug wifi LAN port into LAN switch Now it's acting as a wifi bridge to LAN. Added one step. Makes it easier to get back in if you need to.