@wallabybob:

Its probably worthwhile lodging a FreeBSD problem report (goto http://www.freebsd.org/support/bugreports.html) to initiate a conversation with the FreeBSD developers about this. At best someone will need to add an entry to the "supported devices" table in the re driver. But there might need to be more work done, depending on the peculiarities of this particular device.

Thanks, done that, this is their response to problem report :

Old Synopsis: Realtek 8110SC with device ID 0x814910ec is not detected by FreeBSD 7.1. Most of New Mini-ITX boards are based on this chip.
New Synopsis: rl(4) Realtek 8110SC with device ID 0x814910ec not detected

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Thu Apr 30 20:06:18 UTC 2009
State-Changed-Why:
To submitter: can you please try the patch at
http://people.freebsd.org/~gavin/PRs/134105.diff
and see if that makes a difference?  If you still do not
get the extra interfaces, you should at least get extra lines
in the dmesg, please supply them.  Thanks!

Responsible-Changed-From-To: freebsd-i386->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Thu Apr 30 20:06:18 UTC 2009
Responsible-Changed-Why:
Track

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

I am not familiar with applying patches. Is there any guides?

Did you get it to work???

The DP83815 and DP83816 are identical (816 only adds WoL,) and are more than capable of wirespeed under FreeBSD, when using POLLING and doing raw, rather than pf. DP8381(5,6)'s backed with sufficient CPU certainly can do what you're looking for, but a 5501 does not fall into the sufficient CPU category. The DP83816's beautiful for pfSense in that you can do not only in-chip zero-CPU MAC filtering, but deep frame pattern matching. Sadly, nobody bothered to implement either in sis(4), or the PHY's self/remote/cable test capabilities. Hell, the Sun X4445A Quad Gigabit is actually based around the gigabit version of the DP83816, which did add TCP checksum offload. The problem is that only Sun picked up on the design, and nobody else used them. The MacPHYter family is still far and away, one of the most advanced designs ever created - even Intel does not equal them in many regards.

But I digress; as I said, you need to back an 83816 with significant CPU. Realistically, you'll only find RealTrash, Intel, and Marvell (D-Link DGE-530T) out there. As far as I know, D-Link hasn't changed the hardware on the 530T. So either that or an Intel card will do the job.

Take note of the reviews; this is the typical experience with this board. It is a very, very low quality board like most Tyans. You will not get a much usable life out of this board. I had two at work, both repeatedly failed. The vendor who sold them to us was forced to eat both systems and replace them with Supermicro.

That said, everything on the board will be supported by pfSense without issue.

on install what type of kernel did you use ? the atom only has one prossecor and no extra kernels is it the uniprossecor i should use ?

@forum:

yes that was exactly what i mean. are you sure it won,t work ? because it would be very nice to have two extra nic. and i mean that i use a risercard with two pci slots on it.

Why not get a multi-port NIC?

Does the Alpha still use the atheros driver?

I found this:
http://leaf.dragonflybsd.org/cgi/web-man/?command=ath§ion=4

Revision v3 of the Netgear WG311 is based on a Marvell Libertas 88W8335
     and is not supported by this driver.

EDIT:
Looks like we might need the Malo driver which is in Freebsd 8.0
http://www.freebsd.org/cgi/man.cgi?query=malo&sektion=4&manpath=FreeBSD+7.1-stable

I´ve been running both WRAP and ALIX boards with full installs of both IPCop and PfSense using 4GB microdrives. One of these units has been running now for over 2 years without an issue.

When I first started using microdrives they were silly expensive. Now, however, they can be purchased on eBay for under 10.00€. These drives produce no noticeable heat and make little difference to power consumption.

Based on price and performance I can´t see any reason to go with a standard CF card with ALIX boards when for the same price you can have a full install with access to all the add on packages as well.

MiniPCIe interface contains 1 lane of PCI express, so performance should be equivalent to a fullsized PCIe 1x slot. I don't see any reason why this wouldn't work.

This problem may be resolved, but we need testers. The patch was for a Realtek 8139C+ chip specifically (which are also present on Firebox X series devices).

Please see http://forum.pfsense.org/index.php/topic,15669.0.html

Hi
I have found that IDE connector on Nokia ip130 motherboard is in fact a 50 pin connector, and that could be the reason of issue : following some info found at http://pinouts.ru/HD/Ata50Internal_pinout.shtml , "The first four pins of the connector plug located on the device are not to be connected to the host, as they are reserved for manufacturer"s use"
So I have the idea that Nokia uses this pins to detect if the IDE 2.5 disk  is jumpered as device0, device1, or cable select
And so I think that the CF adapter must emulate this, by providing 4 pins more (than the usual 44 pins) in positions 1-2-3-4 to provide this info

So solution could be to find a CF adapter with 50 connector with cable selection in the 4 first pins, and not like usual 44 standart pins and cable selection somewhere else on adpater

Do someone agree on this and found/used such 50 pin adapter

Thanks
GyB

The Alix box will be just fine on a 20/1 ASDL line with only 8 users.

gigabit nics have more throughput even on non gigabit connections vs 10/100 nics

you use the installer, install the base system
log on
go to shell (8 from console)

use fdisk to partition the other disks (google fdisk)
create the filesystem (google how to do this, i forgot the EXACT command)

you're probably better off just putting the entire "var" directory under a single disk…it's going to be easier in the long run
to do this just make a new directory
mount your new disk (again, google mount if you need to but it's basicly mount DEVICENAME DIRECTORY NAME so if your device is /dev/ad9s1 and your new directory is /mnt/newvar the command would be mount /dev/ad9s1 /mnt/newvar

copy everything from var to the new drive using the cp -r command
use the mv command to mv the old var to /var-old (you do this incase something goes wrong and you can easily restore it)
use the cp command to cp /etc/fstab to /etc/fstab-backup
create a NEW /var directory with mkdir
edit fstab to mount your new /var disk

that's the method on a system ALREADY installed...i might have left some stuff out.....it's been awhile since i've done this in free bsd

on a new install you can probably use the installer to partition and mount disks...

A forum search for "fitpc" turned up this note: http://forum.pfsense.org/index.php/topic,15132.0.html suggesting at least one user has successfully installed pfSense on a fit PC.  The same search turned up another user who apparently gave up trying to install pfSense on a Fit PC.

I have no experience with Fit PCs. However I have been running pfSense 24x7 on a mini-ITX system with a 1GB solid state disk module for almost a year. The module is a Transcend TS1GDOM40V-S. It plugs directly into the IDE connector on the motherboard. There are 44 pin variants to replace notebook drives. I bought it from http://www.memoryc.com, current cost 14 euros and they ship internationally. This won't be suitable if your pfSense needs lots of disk capacity (e.g acts as web cache) or is a heavy disk writer. Compact Flash cards are another low power alternative and from reading the forums it appears there are a number of pfsense users who have chosen that option.