Installation on Intel D2500CC (atom with dual NIC board)

MMacD

Reading up just now on the hardware requirements for fNAS, I'd say the more important issue is address space and bandwidth. I've read, tho never seen verified (have you?), that a D2500CCx does have more than 32-bit address space implemented on the board, and I know there are some 8GB parts available, but fNAS's requirement of 1GB per TB to get anything like good performance would make me want to experiment before deciding to host both Snort and fNAS on the same board.

stephenw10

You can use nas4free instead. I believe that has a lower hardware requirement. There are other similar projects.

Steve

moxyspirit

Thanks for the replies. I am currently running nas4free, booting from a thumb drive, at home. I think I am going to focus on building my pfsense boxes and setting up VPN.

o1121708

Hi kids, bugs got fixed in latest 2.1-snapshot.
Installed 64bit version on d2500cc flawlessly.

cibomato

Good news! I'm new to FreeBSD/pfsense and ran into this problem right at the start… Since I don't want to wait for 2.1 release nor using a unstable snaphot version, I'll go with the 'install 32bit first and write down the inputs' method first.
Hope it'll install smoothly on my Samsung 830 SSD (64GB) and it'll detect and work with my miniPCIe WLAN Card (Compex WLE200NX).
BTW, I'm using this case: http://mini-case.com/pi37/pd332.html, totally fanless and hopefully ok when running pfsense 24/7….

Cheers,
cibomato

tesna

I'm has similar board JW Minix Mini HD PC http://www.jwele.com/motherboard_detail.php?1140 with 128GB SSD and 2GB ram. Since I need to set up several VLAN interfaces in the console so I had trouble using writing down the inputs method. Therefore I use the i386 version instead. Is there any downside using i386 version apart cannot using more than 4GB RAM?

stephenw10

No not really.
There may be some marginal performance increase using 64bit but its small enough you'd have to setup a test to see it. I've seen people argue both ways on this.

Steve

neztik

I just picked up a new board. It was listed on ebay as the Intel2500CCE. When I received the board it shows Intel D2500CC. Is there an actual difference between the two?

From what I could find :

The 'E' suffix in the model name (e.g., D2500CCE vs D2500CC) signifies that this product is an Intel Extended Life Product (ELP). ELP products will be available for extended production times (3 years) and are perfect for project use.

So do you think I have the same thing? I dont see anywhere on the board the "E" just D2500CC.

Not sure if I should send it back and find one that has "e" listed.

Any help would be greatly appreciated.

-Neztik

matguy

@neztik:

I just picked up a new board. It was listed on ebay as the Intel2500CCE. When I received the board it shows Intel D2500CC. Is there an actual difference between the two?

From what I could find :

The 'E' suffix in the model name (e.g., D2500CCE vs D2500CC) signifies that this product is an Intel Extended Life Product (ELP). ELP products will be available for extended production times (3 years) and are perfect for project use.

So do you think I have the same thing? I dont see anywhere on the board the "E" just D2500CC.

Not sure if I should send it back and find one that has "e" listed.

Any help would be greatly appreciated.

-Neztik

I would think that would only matter if you were expecting to order an (or many) exact replacement as new stock through a standard distributor sometime in the next couple years. Those designations often are important for system integrators or manufacturers that need to be able to plan their supply chain for a particular product over the next few years.

Think of it this way, if you were building these as appliances and you needed to make sure each and every one was exactly the same for the planned release of your product, then I'd worry about it.

For a one off, no, probably not assuming it's otherwise identical, hardware wise.

neztik

Great! Thanks matguy. I can start building my new router this weekend without having to wait. I am currently running an older i386 system. The plan is to install 2.1 AMD64 and use the 2 onboard nics to VLAN tag.

matguy

Since that board only supports 4GB of RAM anyway, I would probably stick with x86 (32 bit) pfSense. The main reason for going with x64 support is to be able to address more than 4GB of RAM, otherwise x86 may be more supportable for you.

t3h0th3r

@matguy:

Since that board only supports 4GB of RAM anyway.

actually, the board supports at least 8GB ram, despite the claims of Intel:

# uname -rsp;dmesg|grep CPU;dmesg|grep memory
FreeBSD 9.1-RELEASE amd64
CPU: Intel(R) Atom(TM) CPU D2500   @ 1.86GHz (1866.78-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0: <acpi cpu="">on acpi0
cpu1: <acpi cpu="">on acpi0
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
SMP: AP CPU #1 Launched!
real memory  = 8589934592 (8192 MB)
avail memory = 8217665536 (7836 MB)</cpu></cpu></acpi></acpi>

they are probably trying to make it look less attractive than it is…

car2010

@t3h0th3r:

actually, the board supports at least 8GB ram, despite the claims of Intel:

# uname -rsp;dmesg|grep CPU;dmesg|grep memory
FreeBSD 9.1-RELEASE amd64
CPU: Intel(R) Atom(TM) CPU D2500   @ 1.86GHz (1866.78-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0: <acpi cpu="">on acpi0
cpu1: <acpi cpu="">on acpi0
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
SMP: AP CPU #1 Launched!
real memory  = 8589934592 (8192 MB)
avail memory = 8217665536 (7836 MB)</cpu></cpu></acpi></acpi>

Hello t3h0th3r, I am going to use the same board for a new
pfsense installation.

As I am going to include Snort, Squid + havp and OpenVPN,
I was looking for a board with more than 4GB Ram, but the
2 Intel Nics convinced me :)

Are you running the Intel D2500 or the newer D2500CCE revision?

What Ram do you have installed?
If possible could you provide the serial number for the memory.

Thank you very much!

dquant

Today I installed the D2500CCE. I selected the Jetway JC110-B case which allows for adding two PCI cards, and has two internal fans. It is not very noisy at this moment. The case comes with a wall mount which is very useful as well. The Intel board fits without moving the fans's (which I read somewhere else). The BIOS has a setting for "always on" on power failure which is useful in my case because the firewall will be installed quite remote. I burned "pfSense-memstick-2.0.2-RELEASE-i386-20121207-1630.img" on a memory stick and installed pfsense from the stick on a harddrive. The display output was a little corrupted but good enough for a "simple" installation (I could read most of the words). The monitor isn't needed after the install, so it is good enough to me.

To answer the question above:

board: Intel D2500CCE
Memory: Transcend SO-DIMM DDR3 1333 2Gb

Later on I installed Squid proxy. The firewall will be used by a maximum of 75 users and a bandwidth of 60Mbit.

Dirk.

stephenw10

Solid information. Nice first post! ;)

Steve

stuck

besides the first gentleman who posted his idle consumption @ ~20watts
has anyone else checked their power consumption at idle?
I thought I read somewhere that these atom 2500's were supposed to idle at <10 watts?

Paul47

My D2500CC idles at 15W using a "Kill-a-watt". I have it running the 64-bit 2.1Beta snapshot. I think the 32-bit beta also worked. Anything else was a problem for me, IIRC. I am using a Picopsu-120 with a 10A (large) power brick, which might account for some of that. A PicoPSU-80 would probably make more sense. I'm using a flash drive, not a hard drive.

tpf

I'm using pfS 2.1 x64 Snapshots full-install@hdd with two Intel D2500CCE board since eight months without any problems, except the serial-console-bug. Services are HAVP, Squid / Dansguardian and OpenVPN on a 50/2,5 cable. VLAN on the Intel NICs works, too.

Without cooling the Atom heats to 60 degree celsius. Power consumption with HDD and none -80+ PSU ~30W.

pfs_dashboard.png_thumb

pvoigt

@tpf:

I'm using pfS 2.1 x64 Snapshots full-install@hdd with two Intel D2500CCE board since eight months without any problems, except the serial-console-bug. Services are HAVP, Squid / Dansguardian and OpenVPN on a 50/2,5 cable. VLAN on the Intel NICs works, too.

Without cooling the Atom heats to 60 degree celsius. Power consumption with HDD and none -80+ PSU ~30W.

Nice to hear, that this nice board is handling VLANs correctly - despite some reported problems elsewhere. The Intel is using the same NIC as my board, namely the Intel 82574L and I can confirm not having any VLAN issues.

Your measured power consumption seems very realistic according to my experiences with an Atom D525 on a Jetway NF99FL-525. I've measured the power consumption with a power meter during several hours and found ~33 W with one CF, WiFi, one case fan and a standard ATX PSU.

Hoping, for a solution of the serial console bug in the near future as it is the same with my board (pfSense 2.0.1 NanoBSD VGA AMD64) :)

n1ko

I got one of these recently too. Running vlans and no troubles (2.1).

The traffic output seems to be quite low though, running iperf with single nic and vlans only gets me around ~380Mbps because the cpu gets capped by the interrupts.