@the_greenest_noob: thanks everyone for your insight, i'll try to test the laptop, given that the atom way looks underpowered for what i aim to do. any hints on a known working pmcia card would be very appreciated. CardBus or ExpressCard? Used an Intel Pro/100 CardBus in DELL Inspiron 5100 until recently switched WAN to VLAN on the integrated Broadcom 440x.  LAN is native physical.

I got the same problem with a dell Switch.  Everything will works if you disable the POE from the port. Thanks, your post help me find it out! Benoit

Arrived today. Thanks again for your generosity.

@tirsojrp: The problem with these boards is always the same, PRICE$. … don't forget lots of headers and ports for accessories that are never made and the fact that no one ever makes a case it will fit into.

I confirm that the driver is correctly loaded in 2.1BETA. We do intend to switch to 2.1BETA very soon. Thanks for all your help.

It's almost certainly easier to format the disk from pfSense directly. I don't think there is any convenient way of writing UFS from Windows. This might help: http://doc.pfsense.org/index.php/Local_Disk_Storage_on_Embedded_%28soekris%29 Steve

I just read the manual for the device.  You need to go to page 12 of the manual where it talks about connecting it to another router.  You'll also have three LAN ports you can use on it, so it can be a hub also so you wouldn't necessarily need the extra NIC. Set up the d-link dir-655 wireless WPA security and password and there's no additional configuration required in pfSense.  All of the configuration is on the d-link dir-655 side.

one thing that comes to mind: did you by any chance set WEP encryption for that interface? br, Benny

However flowcontrol does appear to operational: [2.0.3-RELEASE][root@pfsense.fire.box]/root(5): sysctl dev.em dev.em.0.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.4 dev.em.0.%driver: em dev.em.0.%location: slot=1 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x1075 subvendor=0x8086 subdevice=0x1075 class=0x020000 dev.em.0.%parent: pci2 dev.em.0.nvm: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 dev.em.0.flow_control: 3 dev.em.0.mbuf_alloc_fail: 0 dev.em.0.cluster_alloc_fail: 0 dev.em.0.dropped: 0 dev.em.0.tx_dma_fail: 0 dev.em.0.tx_desc_fail1: 0 dev.em.0.tx_desc_fail2: 0 dev.em.0.rx_overruns: 0 dev.em.0.watchdog_timeouts: 0 dev.em.0.device_control: 1077674561 dev.em.0.rx_control: 32770 dev.em.0.fc_high_water: 28672 dev.em.0.fc_low_water: 27172 dev.em.0.fifo_workaround: 0 dev.em.0.fifo_reset: 0 dev.em.0.txd_head: 131 dev.em.0.txd_tail: 131 dev.em.0.rxd_head: 194 dev.em.0.rxd_tail: 193 dev.em.0.mac_stats.excess_coll: 0 dev.em.0.mac_stats.single_coll: 0 dev.em.0.mac_stats.multiple_coll: 0 dev.em.0.mac_stats.late_coll: 0 dev.em.0.mac_stats.collision_count: 0 dev.em.0.mac_stats.symbol_errors: 0 dev.em.0.mac_stats.sequence_errors: 0 dev.em.0.mac_stats.defer_count: 0 dev.em.0.mac_stats.missed_packets: 0 dev.em.0.mac_stats.recv_no_buff: 0 dev.em.0.mac_stats.recv_undersize: 0 dev.em.0.mac_stats.recv_fragmented: 0 dev.em.0.mac_stats.recv_oversize: 0 dev.em.0.mac_stats.recv_jabber: 0 dev.em.0.mac_stats.recv_errs: 0 dev.em.0.mac_stats.crc_errs: 0 dev.em.0.mac_stats.alignment_errs: 0 dev.em.0.mac_stats.coll_ext_errs: 0 dev.em.0.mac_stats.xon_recvd: 0 dev.em.0.mac_stats.xon_txd: 0 dev.em.0.mac_stats.xoff_recvd: 0 dev.em.0.mac_stats.xoff_txd: 0 dev.em.0.mac_stats.total_pkts_recvd: 850882 dev.em.0.mac_stats.good_pkts_recvd: 850882 dev.em.0.mac_stats.bcast_pkts_recvd: 699 dev.em.0.mac_stats.mcast_pkts_recvd: 0 dev.em.0.mac_stats.rx_frames_64: 715 dev.em.0.mac_stats.rx_frames_65_127: 847331 dev.em.0.mac_stats.rx_frames_128_255: 985 dev.em.0.mac_stats.rx_frames_256_511: 555 dev.em.0.mac_stats.rx_frames_512_1023: 90 dev.em.0.mac_stats.rx_frames_1024_1522: 1206 dev.em.0.mac_stats.good_octets_recvd: 71709190 dev.em.0.mac_stats.good_octets_txd: 72480859 dev.em.0.mac_stats.total_pkts_txd: 849527 dev.em.0.mac_stats.good_pkts_txd: 849527 dev.em.0.mac_stats.bcast_pkts_txd: 22 dev.em.0.mac_stats.mcast_pkts_txd: 5 dev.em.0.mac_stats.tx_frames_64: 726 dev.em.0.mac_stats.tx_frames_65_127: 846203 dev.em.0.mac_stats.tx_frames_128_255: 152 dev.em.0.mac_stats.tx_frames_256_511: 361 dev.em.0.mac_stats.tx_frames_512_1023: 424 dev.em.0.mac_stats.tx_frames_1024_1522: 1661 dev.em.0.mac_stats.tso_txd: 0 dev.em.0.mac_stats.tso_ctx_fail: 0 How do those numbers compare with your failing NIC? Steve

Hi, I would suggest the HP ProCurve Switch V1810-8G v2. I have 3 of them for my home setup, they work very well. The average price in Swiss is CHF 80.- Regards

http://doc.pfsense.org/index.php/DMA_and_LBA_Errors

@apfusertoo: I am really hoping for a non-anecdotal, authoritative "THIS is the card we all know is THE ONE" but if I cannot get that, I will try this one. There are some reasons why this is not possble now and probably won't be possible for some years: 1. Some suppliers change the chipsets used in their cards without changing the model number. In such a case one particular revision of the card might use a supported chipset while another revision might use an unsupported chipset. 2. Some chipset suppliers don't provide open access to programming data for their chipsets making it very difficult to write open source device drivers. 3. The FreeBSD kernel developer community seems considerably smaller than the linux kernel developer community so there are fewer people to write new device drivers or port device drivers from other open source operating systems.

yup.. just wanted to give Atom a chance but haven't seen many real life feedbacks on its performance. I guess I have to stick with i3 for now. My main reason for Atom was because its fanless and silent. I could add a fanless heatsink to the i3 but it may overheat on heavy network activity.

@ecube: Looks like it has this thing: Cavium CN5010 whatever that is.  Could be RISC, which would be bad. Seems to be a MIPS-processor. Bad luck there. I was the one who tried to get Pfsense onto a Netgear Prosecure STM150 with bad results. I have not given up yet, but Netgear clearly dont have that flexible hardware as other manufacturers.

There are no good options for hosting files on the pfSense box. If you search the forum you'll see this is a common question that usually receives the same answers: It is possible to do it but it's very much not recommended. It reduces security and it probably wouldn't survive a firmware update. It you want a single box solution for firewall and media servers by far the best way is to run both pfSense and nas4free, or whatever, virtualised. Steve

the daughtercard uses "standard" 82574L's, I'd be curious about the jetway bus they're connected to and if it's actually capable of 4Gbps.

See this… http://forum.pfsense.org/index.php/topic,61782.msg333562.html#msg333562

@Jason: @tirsojrp: Check page 5 of this doc: http://cache-www.intel.com/cd/00/00/46/78/467819_467819.pdf Even Intel don't have an straight answer about non-ecc or i5/i7 CPU. edit: Asus CPU support list Looks pretty clear to me. They say that the i5/i7 doesn't support ECC. My mistake, I should have said: …an straight answer about non-ecc or i5/i7 CPU support on C204. As stated in page 5 ”Not Supported” configurations may still boot