@x: Hi, OK, I think I know what happened :) /31 is the answer I was looking for. pfSense do not support /31 networks ;(( Best regards, – Peter Not that it solves anything for you right now, but it's on the TODO-list for pfSense 2.2: https://redmine.pfsense.org/issues/1972

I understand. Nothing obvious that would stop that laptop booting. I don't think I've ever seen an 'OK>' prompt. Steve

@orthopteroid: The strange thing is I don't see the file snort-2.9.6.2-amd64.pbi.sha256 listed on https://files.pfsense.org/packages/amd64/8/All/ Packaging error? The very old pfSense version, 2.1.1, wasn't using FreeBSD 8.3, but a lower version. So, probably the download path, used to load basic FreeBSD packages to complete pfSense packages isn't probably valid anymore. Easy and best solution:  get the latest version 2.1.4 and your problems are solved.

Well 2.2 installs but after rebooting the server it's failing to see that PFSense is installed on the machine and it's just caught in an endless reboot cycle. Any ideas here? I've checked in BIOS and everything looks alright to me. Not getting any errors either it's like it's thinking there's nothing to boot from on the HDD.

I've had this working in the past, and I remember using the Target Category to handle the redirect.  I don't remember if I had any problems when using the Common ACL redirect.  Try creating a Target Category for your blocked sites, add the sites you want blocked and then change the redirect message.  Then set Common ACL to Deny that Target Category.

Maybe a nice TXT or PDF report with a section for each service. For example, the DHCP section would list the config settings and any reservations. The Firewall section, would list all the rules.  So on and so forth.

^Exactly. X86 only currently I'm afraid. There is a possibility of MIPS support sometime in the future (after 2.2 is released) but ARM is not even on the map! Steve

Thanks Steve, I would agree the image should be bit for bit and the file format shouldn't make a difference. Its weird, I had this issue whether I used dd or Win Disk Imager. I'm using a transcend 4GB Industrial Grade CF card. I guess that I never actually did anything to the bios at all then, from what you say. For RAM choice it was pretty simple: I took the advice of the pfSense docs: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox and used the KVR100X64C2/512 module - all in all £10 from fleabay. Its been a learning curve but good fun! I'm now going to convert an XTM 505 as my main box. Thanks, Adam.

Any reason you're using 2.0-release? That's old! There are a large nuber of threads about how to get past 'stuck at 38%' if you find that an issue. Some people found it eventually went past it others recommend disabling and CPU virtualisation features and any multicore features in the bios during the install. They can be re-enabled for normal running. Steve

To anyone that has read this and might have ran into the same issue… The auto detected IPV6 network IP addresses that were assigned to the interface didn't have a gateway that was reachable and so apinger was going bananas trying to constantly reload the configuration. When I disabled iPV6, utilization went back to normal and re-enabled and properly configured the IPV6 addresses on the WAN it fixed the issue... Hope this is at least helpful to someone else as the logs are not very clear as to what's happening.

So it is now online - this connection is setup by the pfsense vm. I preset all the forwarding rules while the router was not connected to the internet but was connected on the LAN side to an open IP address. To put it online I removed the LAN and WAN connections from the old router. Plugged in the WAN line into the unused but configured interface and turned on DHCP and moved the LAN gateway from the open IP address I used to do the configuration to the same IP as the old routers Gateway.

here is an update. I can now ping out. - however, the ip is 70.177.0.29 the static ip for the wan. when i try Virtual ip, i get nothing. - I cant use the lan, as i have voip phones on there, that requrie an ipsec connection to a remote switch, and they need a public ip address. - So i thought i try a dmz, or use the opt2 as the cidr block. thanks,

http://snapshots.pfsense.org/

I'd read that for the LEDs and Thermal Sensors, but not for the reset button.  Oh well.

@Stewart: I was actually able to fix the problem, I think.  Instead of resizing partitions, we are able to increase the size of the RAM drives.  While this may result in the loss of virus definitions and such on a reboot, it only takes about 4 minutes to be fully operational. Ok, that would work too.

Seems you have to use /sbin/reboot as mentioned below to reboot FYI - it should /sbin/tunefs -t enable /, not /sbin/tunefs -t / as mentioned below. @spid: @dstephens80: Charlie, I will give v2.2 a try and let you know how it goes.  As far as dmesg, I can provide nothing as the system will not boot with AHCI enabled.  it will not detect any GEOM devices, but it will boot fine if I remove the ahci_load="YES" from /boot/loader.conf.local. Did you convert fstab to ufslabel before adding ahci_load="YES" ? Run the following script to do it: /usr/local/sbin/ufslabels.sh then if it boots correctly go in single user mode and enable TRIM with: /sbin/tunefs -t / reboot with: /sbin/reboot and after a reboot check if it's enabled with: tunefs -p /