It's time to move on from that device. :-)

Even if you manage to get it to boot, you're going to have a bad time. 128MB may have been good on 1.2.x and passable on 2.0.x, it's not really sufficient for 2.1.

The WRAP has been EOL for many years for good reason.

I think I have this figured out. When I first installed I gave it an IP on another subnet, thinking I would use that IP as the management IP, since it will be a transparent bridge. The machine seemed to cache that IP number and attempted to set the wrong default gateway, which I found had failed in the logs. I removed the second IP from the configs, and the gateway, and it seems to be working now.

Hmm, not too sure what to suggest here. Normally the boot loader should timeout and automatically select F1. Quite why it isn't I don't know. Have you changed anything in the box since you installed, like perhaps added or enabled something that provided the PXE boot option?

You could try this:
https://doc.pfsense.org/index.php/Remove_F1_Boot_Prompt

That carries some risk though. Make sure you know which disk you're using!

Steve

Ok so thats pretty embarrassing even by my standards  :-[ Thanks Steve

@dreamslacker:

Go to system->Routing.

Ensure that your WAN gateway (198.0.212.70) is set properly (add it if you haven't got it).

Now go to Firewall->NAT->Outbound and check that you have rules to NAT to 198.0.212.68.
If not, set manual outbound NAT, then add a rule to NAT your LAN subnet to 198.0.212.68 on WAN interface, uncheck 'static'.

Go to Firewall->Rules->LAN.  Check that you have a default rule to allow access from LAN subnet to any protocol, any destination.  If you don't have this, set it up.

That should work for most part.

This was completely the issue, figured it out about an hour ago after searching for 'basic internet connectivity pfsense' on google. Thank you guys very much!

@robina80:

I know vmware isnt supported any more …

If you're referring to the fact that pfSense VMware appliances have been discontinued, I think you might have misunderstood.

Insstalling on VMware is still "supported" in the sense that it does run quite happily on products like ESXi, Player and Workstation.  It's just that the pre-built VMware appliances aren't being created by the pfSense developers now.

It really isn't hard to install pfSense under any of those VMware virtualization products (or the open source equivalents).

have a look under the Virtualization category here https://doc.pfsense.org.

You can do it with a USB thumbdrive (I'm assuming there is a hardware switch on the USB drive to write-protect it).

First, you need to install the Cron package (easier to do this with GUI).

Next use the Crontab to set a job at midnight?, daily, to run a shutdown with restart command for the reboot.
Command will be:  shutdown -r now

Go to diagnostics -> NanoBSD.  Disable all Backup jobs (if any) so pfSense doesn't try to write to disk.

After you are done with all that, re-enable the Write protect.

To be honest, this is probably not required at all.  What you should focus on is to secure your hosted services, enforce good passwords policies, and keep your clients/ servers actively protected with anti-malware software suites.
Further, don't expose the WebGUI/ Telnet/ SSH for the pfSense box to the internet.
In all likelihood, it will be your hosted services (servers and such) that get compromised rather than the pfSense box itself.  You can setup SNORT to further protect such hosts.

Are you using vlans in the switch?
By other devices do you mean wireless clients?

Steve

@stephenw10:

It's not caught by your rule because it is set for ipv4 tcp only. Traceroute uses igmp. Set the protocol to ipv4 any and it should work.

Steve

Steve you save me. Thank you very much.

2.1 has better support for sata interfaces which is obviously a good thing. However in some systems this has resulted in the drive bring recognised by a different driver and not booting.
Try changing the sata mode in the BIOS.

https://doc.pfsense.org/index.php/Boot_Troubleshooting#BIOS.2FDisk_Errors

Steve

Thanks for your guidance stephenw10
and thanks for your links ptt.

or wait another day or two and update from the netgate repo

I stand corrected.  2.0.3 gets much further before throwing errors and dying.

I'm guessing the model of USB stick isn't supported.

What modem/ router are you given?
Also, what kind of connection do you have?  DSL?

If it is a DSL connection, find out what your VPI/ VCI is (get it from your provider).

When setting the modem to bridged mode, disable the DHCP and set the VPI/ VCI as required (for DSL) by your ISP.

Connect the modem 'LAN' to your pfSense 'WAN' port.  Login to pfSense and setup the WAN connection as PPPoE (for dynamic ip DSL).  Key in your username and password for the PPPoE login.

If you cannot do it in GUI then you can download Ca.crt und CA.key from GUI and import on your other pfsense.

Or you can probably edit your config.xml file and copy and past the CA data.

Are your downstream clients using dhcp? Are they receiving the correct details?
How are you configuring wan and LAN? Please hive more details.

Steve

Thanks - couple of questions:

Wizard - Is this traffic shaper wizard?
If so, I am trying to figure out which wizard to run.  I have one connection to the internet - through my verizon modem and one lan behind the pfsense firewall.  That to mean sounds like a single wan, single lan yet I only see single lan, multi wan or multi lan, single wan?

Thanks

Have got the same problem.
Is there a fix? I couldn't see anything in the bug reports.

Regards,
Sebastian