Thank you for your advice, I will try that method sortly, hope that it will work fine.

good to hear!

I try to exectute this command:

sysctl -w hw.acpi.handle_reboot=1

but… the pfsense reponse:

sysctl: unknown oid 'hw.acpi.handle_reboot

I take the same problem with Alix Board Mod: alix3d2...and still not get the machine restarted.

Please... help me.... :'(

I create the post wih this problem: http://forum.pfsense.org/index.php/topic,19951.0.html

Could be a hardware problem. You can put the NIC in another machine, or test another NIC in your machine (you can also try other type of NIC's, to test the mainboard on errors). When you've got only one NIC, maybe your reseller or Supermicro/Intel can help you with this problem. Good luck!

I've tried to manually set media type with the same negative result.

Yesterday I've tried with FreeBSD 8.0 RC3, and it works fine…

So, the problem is related to 7 FreeBSD version.

Unfortunately, current pfSense release is also based on 7.2 .. And alpha release is still alpha...

I'm a definite n00b when discussing pfsense, so take this for what it's worth.  From my previous experience with Alix boards, I am not sure that they will have the power to run Snort + HAVP well.  Snort, from what I have heard, would require a bit more power to be truly effective.

Hey James,

You haven't said anything about the throughput and the amount of money you're willing to spend. A standard PC with mATX or M ITX board, Intel E7200 and 80+ power supply uses only about 35W (idle). How much power does you configuration pull on energy? Maybe it differences about 10W? On yearly base 10W would save you around € 15,- on energy costs (in the Netherlands, based on 330 days/24 hours in a year). Throughput, especially with Intel NIC's, is a lot better compared to the VIA board. You can also use Realtek 3911D NIC's. Lower costs, but also (a lot) less throughput and less stability. I don't know anything about running this Jetway mainboard with Pfsense, but reading the forum can tell you that Realtek isn't exacly a favourite…

Not supported.

Yes they are :)

@karlzon:

I do know dual and quad have more cores than one, but they still count as one single CPU. But, do you mean that SMP kernel (option two) is for one (1) dualcore CPU to? I though it only mattered if there where more CPU units in one system. Example; dual (2) XEON CPU's in a server.

SMP is for multiple cores or multiple physical processors. It can also be used on a system with only one processor without any real negative effects from what I understand.

@LedPighp:

@jasonlitka:

I've used that board in the past but I've replaced just about all of them with better kit.

What hardware did you use to replace your Jetway? How long have the replacements been up and running?

I replaced the JetWay boxes with the FW-7872 from Lanner (packing a Celeron M 440 & 4GB of RAM).  The systems have been running since July with no issues.  They've been rebooted a few times each for pfSense updates but otherwise have run solid.

Sounds like there may be some other issues with the package in general then.

LOL 16 gig of ram! damn that'd be funny…but since you know it wont support it now...and it seems you want it for basically like a fast cache setup or something...maybe read up and setup a SSD...they are getting pretty cheap now...and the initial write may be painfully slow (at least on the cheaper SSD's, but if you are willing to spend money..the expensive ones writes are pretty fast.....but the cheap ones reads are pretty damn fast...for caching though...after you get a good chunk of data, you'll be doing a lot of reads.

just a thought of a workaround for ya.

good luck.

@Hugovsky:

@Emab:

How can I check if the problem is in the chipset, and how can I try to resolve this?

Can you check what chipset is on your board? if it's a 915 intel, then you might have a problem. Also, do you have all mem banks ocupied?

It was already said by wallybybob…this wont be able to be fixed.  64-bit systems/software will fix this limitation you will need to ensure your hardware/software both support 64-bit to take advantage of 4 gigs or more of ram.

copied from FAQ's  to answer you next question...pfsense does not work in 64-bit mode yet...so we'll just have to wait...It's fast enough the way it is for me and probably all of us though. :)

Does pfSense support 64 bit systems?
From PFSenseDocs

Yes, but only in 32 bit mode. There are numerous installations running on 64 bit processors from Intel and AMD, but 64 bit mode is not yet supported (and not needed for firewall scenarios).

ok i realize that this is really old but i've been really busy and havent even had time to mess with this =, my apologies on my absence and late response…

ANYWAY, wallabybob, I think your right, it wasnt that it didnt detect it...because it did allow me to run through all the drivers, unfortunately none of them worked.

I may try it when i can get this board again lol i had to use it for a much needed upgrade to a server =P

I did plan on the riser card, so thats not new news to me. It doesnt have the right cutouts, but i cant find a 1u case with such a low depth, so i figured i would dremel out the "static" i/o shield so i can use the one that comes with the motherboard, and thus open me up for future upgrades without having to buy the special board for that case.

Issue was solved by installing the Thinkpad Configuration Utility in Windows -> Drive Bay -> Disable.  Fortunately I have another x40 that runs Windows so I just switched out the hard drives to do this.  Everything working great now.

For people who find this thread through google I will post a few performance details.  The x40 is functioning as a router/firewall/Nat device on my home internet line (40-50mbps line, fiber -> VDSL).  Using bittorrent I loaded up 60 torrents (tv shows) and cranked up the max connections.  While downloading around 45mbps with about 3,000 open states the cpu (pentium M 1ghz) was at 50% and memory usage (768mb physical memory) was around 15%.

he is using now p4 celeron system. he gave ibm as gift 2 someone.

Thanks for you thoughts!  From what I understand that NIC driver has been around a long time … but who knows! Strange that this has worked successfully for almost 2 years. However perhaps we've had more more traffic recently and that's begun to be a problem. I still like my interrupt theory ;)

Yes, I'm looking forward to upgrading once 1.2.3 is done!

In the meantime, we're looking to upgrade the hardware. We'll bite the bullet and go for a real (albiet old) server and Intel gigabit NICs, along with fans to fail and a big UPS because it will use real power. This should give us enough margin for growth and error that we shouldn't lose hours of productivity again...