Packet mode (from man boot0cfg):

packet  Use the disk packet (BIOS INT 0x13 extensions) interface,
                    as opposed to the legacy (CHS) interface, when doing disk
                    I/O.  This allows booting above cylinder 1023, but
                    requires specific BIOS support.  The default is `packet'.

If you want to simplify your setup drop the router and use a pure bridged modem. It's less things that can go wrong and less settings to configure. However ot should work the way you have ot now too. You have to manually assign DNS-Servers at system>general if your WAN is not DHCP or PPPoE and gets them assigned automatically.

Really?  You'd rather spend $140 on a Hitachi microdrive instead of $29 on the Seagate?  This is not a poor-quality issue with respect to the Seagate.  It USED to work, now it doesn't.  Something changed in Free BSD to bork it.  By the way, I couldn't turn up any Fujitsu microdrives at all on Google or on Fujitsu's site, so I DK what happened to their product line.  Hitachi bought out IBMs product line, of course.  I think it's just them and Seagate now.

I just wish that bug report had been marked with something other than "non critical" on the Free BSD site.

P.S.  I'm not using a WRAP either.

The embedded version of pfsense displays kernel output via the console port.  You'll need to hyperterminal into the serial port on your device on order to see the rest of the boot sequence from that point on.  So basically pfsense continues to load but without video or keyboard support.  Get a null modem cable if you dont have one already and console in.

Thanks!

You need to download the full update file. Then just upload it at system>firmware. System will reboot after the upgradeprocess. Note that firmwareupdates are not supported for embedded platforms but only full hdd installs.

LOL, thanks!

I installed Webmin (lite) to do this. Works great an I only have to install the modules I need.

Greetings, Marcel

Try the latest snapshot from http://snapshots.pfsense.org/FreeBSD6/RELENG_1/ . Haven't seen the problems you are describing with 1.0.1 anywhere but upgrading to the latest snap won't hurt.

@yawarra_paul:

Hi Scott,

I'm going to give creating a "read-only during bootup" version a try since the versions we ship don't have a lot of need (or space) for installable packages.  As I understand it, when a new version comes out the whole CF usually gets reflashed.

If it seems to work I will post the image on our website at: http://www.yawarra.com.au/sw-osimages.php for others to play with.

Thanks for all your help, it is much appreciated.

Best regards,

Paul McGowan

No problem, please let me know how it works out and thanks again for the xmas present!

I updated to the next release and that particular little nasty went away all on its own.  Maybe a file was corrupted and was overwritten during updates?  Maybe someone (throwing nasty look over the cubicle wall) was "looking" and slipped?  The world may never know.

Thanks for your reply!!
Scott

Do something like this:

vi /cf/conf/config.xml
rm /tmp/config.cache
/etc/rc.filter_configure_sync

I seem to have found a possible solution.  It seems that by having two hard drives connected and using teh on board RAID controller was causing the issue.  I simply removed the second hard drive and the command ran fine.  Thanks.

This is not supported. If you want to do something like that you will have to find your own way (livecd with packages). There have been discussion earlier why this is not a good idea (search forum and mailinglist).

OK, so j0emv beat me to it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/110407

I wish I knew enough about BSD to just fix the darned thing.  I hate waiting.  That little Seagate microdrive is perfect and I can't use it!

Please use the sanpshot from 23.03 with caution, at the time a feature called "schedules" will be implemented!

Use the snapshot from 15.03.

Setup a remote syslog server then tell pfSense to send the logs to the other server.

Currently there are no other methods of saving the logs locally but we will be addressing this soon.