Thanks Again hoba,
  But still no go :(

My Loader.conf looks like this :-
autoboot_delay="10"
hint.acpi.0.disabled=0

But when boot the Box using option 1,  It crashes with a general protection fault when load the network card drivers.  If I use option 2 it boots fine.  I'm just concerned that if the power goes down,  the box will not start unless there is someone here to select option 2 :)

Thanks for your help

Knotty

Sounds like a DNS Issue maybe? If you can reach the modem you can pass through pfsense.

@guybrush:

i know this how-to…
but he is physdiskwriting the .gz-archive onto the flash, can this be true??

Yes, physdiskwrite is smart enough to handle .gz's directly  ;)

Thanks for the info.  Currently got the HD hanging out the side of the case and that is working (connected via ide) but clearly this is less than ideal.  Oh well seems like that will have to do for now.

It's unsupported but should work. Use an IDE-CF-Adaptor to move a full install over to the cf-card. When it asks for swap partition delete it from the autogenerated partitionlist. After you finished the install change the  file like sai told you and reboot.

This kind of config is not supported by the frontend currently. There are some anonymisation services that work similiar to this setup. Maybe a bounty would raise some devs interest in implementing this cleanly in the frontend.

I had nearly the same experience just a few minutes ago, only it wasn't a power issue.

I was testing failover (CARP) and the backup unit wouldn't pick up the IPSEC tunnels.  I brought the main unit back up, rebooted the secondary unit and it started asking for the password.

The secondary unit is definitely FUBAR.  Maybe it's just old and tired and wants a dirtnap?

Memtest on the memory and fsck on the disk. If the checksum checked out on the ISO, and it was verified.

Can I just say that this thread has single handedly fixed my setup problems with pfsense. lol, I was typing in x10 over and over, and I couldn't understand why it wouldn't work… xl0... doh!!!

@Superman:

Check here: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/

Ty  ;D

Thanks, I acctually saw that in loader.help right after i posted that. FreeBSD  is starting to come back to me :)

I don't know for your upnp problem but maybe this can help you for making working your XBOX live! ;)

With the specified settings in my post you should be able to clean the MTU problem. What's the link between ports and MTU ?
Well, with my tests, I noticed that the XBOX try to check your MTU by joining a M$ server on the ports 3024 TCP/UDP or 88 UDP.
But, first of all, the request seems to query a DNS server, and then the MTU-Check server through ports 3024 or 88. Don't know.
So, if your DNS test pass, your MTU-Check depend on your NAT settings.
And sometimes your will run 2 times the test and see : NAT STRICT, and now NAT OPEN.  :o
I all case, your NAT is OPEN :)
I think its just a bug of NAT detection from your XBOX because its use a remote server ;)

To conclude MTU problem => NAT problem :P

@wyckedone:

Since you installed pfSense on the hard drive, the floppy would only be needed for config backups.  You don't need it since you download the backup through the webConfigurator to your remote system.

That's what I thought… thanks.  I'll forget the floppy stuff then.

i pulled a 256meg cf out of my zaurus and threw the image on it. seems to be working fine.

so heres my temporary solution. either (a) the wrap doesn't support a 1gig card or (b) i pulled out the CF card from the reader before i told the software (little gray card with green arrow lower right on win box) to release it and perhaps some files were not completely written to it. i had a similar problem with my zuarus.

ill post again when i find out for sure.

http://wiki.pfsense.com/wikka.php?wakka=BootTroubleShooting
http://wiki.pfsense.com/wikka.php?wakka=BootOptions

@hoba:

m0n0wall has proxyarp too and something called "server nat".  It's different from m0n0 and pfSense has more types of VIPs.

Quick update… I got it running this weekend.  Thanks everyone!  PFsense rocks.  Now I just hope the bounty for content filtering is fulfilled as that is the only thing lacking that I can think of!

LOL.  You might want to take the time to fix the channels, drive types (master and slave) and simply reinstall.  This is quite messy!

BUT!  If you must, change /etc/fstab ad2s1 to ad2s0

Cool, it looks like Bao is still doing USB key bootable images.

http://shopping.hacom.net/catalog/pub/pfsense/