They'll work fine with 1.2.1, actually better as the newer FreeBSD performs better.

My firewall has 1 x vr NIC, 1 x rl, 1 x ath and 1 x udav, I've been running some variant of pfSense 1.2.1 for some months now and can't recall ever seeing similar interrupt percentages to what you see. If you are curious to explore this issue further, perhaps you could  take the interfaces out of polling mode and give the shell command vmstat -i to see interrupt rates on  rl0 and rl2. Are these interfaces in promiscuous mode (possibly bridged with another interface)? Are they connected to a hub rather than a switch? Do you have something "new" happening causing more network traffic?

@Cino: dont use channel 6. I had the same problem with a netgear card. Some reason the wifi card doesn't like channel 6. Back on topic: The problems on WiFi channel 6 might be related to a special mode like "Super G" or "SpeedBooster". Atheros and Broadcom as mfr's invented different incompatible standards to double the max. throughput by bonding channels. I seem to remember having read about it some time ago.

Parallels Desktop only allows you to enable or disable USB emulation, which likely is the equivalent of enabling or disabling the emulation of the USB host controller. After that, you can only decide which attached USB devices should belong to the Mac OS and which to the virtual machine. Actually, one can't even assign real USB devices to a virtual machine before one enables USB support in the virtual machine emulation. So from that point of view it's fool proof. Of course, that doesn't guarantee it's bug free…

Hi, Try searching deviso…may be on wiki. cheers,

There is more information on the Alix boards at http://www.pcengines.ch/alix.htm There are variants with 2 or 3 NICs on board and 1 or more mini PCI slots and wireless mini-PCI adapters. If you have a VLAN capable switch you could get by with 1 NIC running multiple VLANs. In the last few months there have been a few posts on VLANs with suggestions for economical VLAN capable switches.

Typically FreeBSD is very good at auto-negotiation.  I know I thought I had a mis-configuration before and it turned out to be the T-1 router from our Telco.  You can give this a go, but know that it's risky. http://forum.pfsense.org/index.php/topic,9434.0.html

dude, That custom 2u case is sweet!!!  You should do a write up so others can copy the idea. -V

Is your power supply capable of supplying the current needed by the dual NIC PCI card? Maybe the box was built to a price (or size) and consequently the power supply doesn't have much margin.

Send an email with the output you pasted here and the output of a pciconf -lv and send it to freebsd-net@freebsd.org plus freebsd-stable@freebsd.org so the driver author can give you a propper answer. Usually it is an id issue which is a simple adding the id to the driver and recompile but better confirm with the driver author.

@atamido: Do you plan on converting the existing power supply to fanless, or are you going to purchase a new fanless power supply? I may have to replace the power supply with a fanless model.  The entire PC doesn't need alot of power to run so I can probably get away with a small factor 100 watt PS unit once I change the hard drive to a CF or laptop hard drive and no fans.  I'd very happy if the entire thing runs under 20 watts but not likely due to the PIII.  Lucky it's not a P4, power hungry little beast. Darkk

Thanks for the information! The article re SonicWall is crazy. I love open source :-)

Having received no feedback, I went on and bought the motherboard anyway. The good news is that the onboard Ethernet is recognized and there seem to be no other problems. I haven't tried to really use it yet, though.

@Cry: Suggestion: Use the search function ;) Recommendations for choice of NIC have been made many times.  Intel Server grade cards are amongst the most recommended ISTR. Sure I have already read some posts about intel. I want just to be sure that intel and dell 830/840 are compatible. Thanks for your interest!

Well, I have found a decent workaround for now. adding: <shellcmd>ifconfig sis1 media 10baseT/UTP mediaopt full-duplex</shellcmd> to the system area of my config.xml seems to have done the trick.