Version  : 1.0.1-SNAPSHOT-03-15-2007 built on Tue Mar 20 00:29:24 EDT 2007 But no luck. Is there a way to add these drivers to pfsense manually?

Thx all for the replies. Have orderd one now, it seems to be perfect for me.

http://snapshots.pfsense.org/FreeBSD6/RELENG_1/

It feels like i've put the thread in the wrong forum, and if someone with the ability to move it feels that it belongs in the hardware section, please feel free to do so.

I'll lock this thread. Please continue posting to http://forum.pfsense.org/index.php/topic,3954.0.html as this one covers the same topic and is in the correct board. Thanks.

Thanks a lot. Now everythinks work fine! GV

128 mb is enough to run the base featureset on it. Packages are not supported for embedded platforms and depending on the package you really need more ram then (snort for example eats a lot of ram).

Reset the asigned ressources in the bios or try to manually assign them. Also swapping pci slots might help.

@sai: Could the FreeBSD gurus tell me which FreeBSD mailing list to post this problem on? I have tried freebsd-questions@freebsd.org some weeks ago but no progress there. Start at questions, then make your way to freebsd-net@ and if that finally doesn't work try freebsd-current@

Don't know. Hard to say what a faulty bios can do here but as it seems to be fixed I wouldn't care anymore about it.

OPT1 not work, tested with last snapshot 1.0.1-SNAPSHOT-02-27-2007 built on Tue Mar 6 16:54:14 EST 2007, error in log is the same

hmmm… i tried this tutorial but when i did i must have been smoking a wrong pipe. i see now where i went wrong. i'll try it again tomorrow.

Solved… To answer the last post, the box in which we're having problems is the same box that wrote the configuration to floppy. The problems was ACPI.  This is an older PII and ACPI needs to be disabled in order for the FreeBSD to: 1. See the floppy 2. Do anything with the NICs, 3. Not get "stalled" messages for USB mass-storage. Once we disabled ACPI, all was well Thanks for suggestions and help.

Have a look at our recommended vendors list ( http://www.pfsense.com/index.php?id=40 ). If you want  to use packages you need a unit that can carry a hdd and which is upgradeable with RAM. Wraps or Soekris are far too underpowered for what you want to do. Depending on wether you need a fanlass desktop solution or a 19" appliance with fans you will find several options at our recommended vendors. However I would not use something lower than 1 GHz and at least 1 GB RAM if you want to run Squid and Snort. These boxes should be able to push some bandwidth too (for LAN to LAN traffic).

@hoba: We use caching for the config.xml to speed up processing it. Directly editing the config.xml on a running system won't work unless you empty the cache and reboot. Glad you got it going  :) It wasn't a live system.  I was editing it after mounting the drive in a FreeSBIE booted system. Also, would it be possible to allow entry of an IP address during the first boot after putting the drive back in the Nokia?  This would be after the interfaces are set. or An option to enable the Serial Console Below is a snippet of what we currently see and possibly where the new options are set.. –---------------------------- The interfaces will be assigned as follows: LAN  -> fxp0 WAN  -> fxp2 <new option=""><------Request IP address for LAN (this is needed so we can get to the web interface and enable serial console... or <new option=""><------Request serial console enable...  ie:  Enable Serial Console Do you want to proceed [y|n]?y Updating configuration…done. ------------------------------</new></new>

Unsupported but give it a try: http://wiki.pfsense.com/wikka.php?wakka=UsingProjectEvilOnpfSense

Don't think it will work (and with no management inteface I really doubt it). This looks more like a "seperator" where you have an uplink at port1 (to this port all other ports have access) but no traffic is granted between the other ports (like client at port 2 doesn't see other clients at other ports and vice versa). This maybe makes sense for hotelsetups where you want to let out all guests to the internet but want to prevent that guest a tries to access guest b's notebook. To be used with pfSense it's useless as it doesn't support vlan tagging.

Have a look at http://<pfsense-ip>/status.php (it's a hidden page). At the bottom you'll find the dmesg output. Have a look through it to see which devices all use IRQ5.</pfsense-ip>