Update: SRW224P gigabit interfaces also work well with AOC-UG-i4

Has anyone successfully run pfSense 1.2.3 on an Intel D510MO board in embedded mode? I tried using a 512MB and a 1GB USB stick but I cannot get pfSense to finishing booting up. It hangs at "Trying to mount root from ufs:/dev/ufs/pfsense0". Thanks for your help. /boot.config: -h Consoles: serial port BIOS drive C: is disk0 BIOS 572kB/2078452kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org, Mon Dec  7 21:59:24 EST 2 009) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x739788 data=0x13cf6c+0x51c80 / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]… Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994         The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE-p5 #0: Mon Dec  7 22:22:52 EST 2009     sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pf Sensesrc/src/sys/pfSense_wrap.7.i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Atom(TM) CPU D510  @ 1.66GHz (1666.70-MHz 686-class CPU)   Origin = "GenuineIntel"  Id = 0x106ca  Stepping = 10   Features=0xbfebfbff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>   Features2=0x40e31d<sse3,dtes64,mon,ds_cpl,tm2,ssse3,cx16,xtpr,pdcm,<b22>>   AMD Features=0x20000000 <lm>AMD Features2=0x1 <lahf>Cores per package: 2   Logical CPUs per core: 2 real memory  = 2130644992 (2031 MB) avail memory = 2075066368 (1978 MB) ACPI APIC Table: <intel  mopnv10j="">ioapic0: Changing APIC ID to 8 ioapic0 <version 2.0="">irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger wlan: mac acl policy registered cryptosoft0: <software crypto="">on motherboard padlock0: No ACE support. acpi0: <intel mopnv10j="">on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: <sleep button="">on acpi0 pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0 pci0: <acpi pci="" bus="">on pcib0 vgapci0: <vga-compatible display="">port 0x20c0-0x20c7 mem 0xe0200000-0xe027ffff,0 xd0000000-0xdfffffff,0xe0100000-0xe01fffff irq 16 at device 2.0 on pci0 pcib1: <acpi pci-pci="" bridge="">at device 28.0 on pci0 pci1: <acpi pci="" bus="">on pcib1 re0: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethe<br="">rnet> port 0x1000-0x10ff mem 0xe0004000-0xe0004fff,0xe0000000-0xe0003fff irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x28000000 re0: MAC rev. 0x00000000 miibus0: <mii bus="">on re0 rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus0 rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F DX, auto re0: Ethernet address: 70:71:bc:8f:31:08 re0: [FILTER] pcib2: <acpi pci-pci="" bridge="">at device 28.1 on pci0 pci2: <acpi pci="" bus="">on pcib2 pcib3: <acpi pci-pci="" bridge="">at device 28.2 on pci0 pci3: <acpi pci="" bus="">on pcib3 pcib4: <acpi pci-pci="" bridge="">at device 28.3 on pci0 pci4: <acpi pci="" bus="">on pcib4 uhci0: <uhci (generic)="" usb="" controller="">port 0x2080-0x209f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: <uhci (generic)="" usb="" controller="">on uhci0 usb0: USB revision 1.0 uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: <uhci (generic)="" usb="" controller="">port 0x2060-0x207f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: <uhci (generic)="" usb="" controller="">on uhci1 usb1: USB revision 1.0 uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: <uhci (generic)="" usb="" controller="">port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: <uhci (generic)="" usb="" controller="">on uhci2 usb2: USB revision 1.0 uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: <uhci (generic)="" usb="" controller="">port 0x2020-0x203f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: <uhci (generic)="" usb="" controller="">on uhci3 usb3: USB revision 1.0 uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xe0280400-0xe02807ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">on ehci0 usb4: USB revision 2.0 uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb4 uhub4: 8 ports with 8 removable, self powered umass0: <ibm 0="" 2="" usb="" 2.0="" memory="" key,="" class="" 0,="" rev="" 2.00="" 2.00,="" addr="">on uhub4 pcib5: <acpi pci-pci="" bridge="">at device 30.0 on pci0 pci5: <acpi pci="" bus="">on pcib5 isab0: <pci-isa bridge="">at device 31.0 on pci0 isa0: <isa bus="">on isab0 atapci0: <intel ich7="" sata300="" controller="">port 0x20b8-0x20bf,0x20cc-0x20cf,0x20b0 -0x20b7,0x20c8-0x20cb,0x20a0-0x20af mem 0xe0280000-0xe02803ff irq 19 at device 3 1.2 on pci0 atapci0: [ITHREAD] ata2: <ata 0="" channel="">on atapci0 ata2: [ITHREAD] ata3: <ata 1="" channel="">on atapci0 ata3: [ITHREAD] pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached) speaker0: <pc speaker="">port 0x61 on acpi0 sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A sio1: [FILTER] cpu0: <acpi cpu="">on acpi0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: [ITHREAD] ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1: [ITHREAD] ppc0: parallel port not found. Timecounter "TSC" frequency 1666703450 Hz quality 800 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: <ibm memory="" key="" 5.02="">Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 501MB (1026303 512 byte sectors: 64H 32S/T 501C) GEOM: da0: partition 2 does not start on a track boundary. GEOM: da0: partition 2 does not end on a track boundary. GEOM: da0: partition 1 does not start on a track boundary. GEOM: da0: partition 1 does not end on a track boundary. WARNING: Expected rawoffset 0, found 63 WARNING: Expected rawoffset 0, found 448623 Trying to mount root from ufs:/dev/ufs/pfsense0</ibm></acpi></pc></serial></ata></ata></intel></isa></pci-isa></acpi></acpi></ibm></intel></intel></intel></intel></uhci></uhci></intel></uhci></uhci></intel></uhci></uhci></intel></uhci></uhci></acpi></acpi></acpi></acpi></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></vga-compatible></acpi></acpi></sleep></high></intel></software></version></intel ></lahf></lm></sse3,dtes64,mon,ds_cpl,tm2,ssse3,cx16,xtpr,pdcm,<b22></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c<br>

A forum search would be enlightening there, there are four pages of hits for 'cm9' with what appears to be several people using it.

Thank you for the feedback! The strange thing in my case ,is that in my country online stores i can find an adapter and a cf card at almost the same price as a IDE Flash Module :) less capacity for the IDE Flash module ,but enough for the pfSense. Thanks for the help ,now i have the full picture. Nice forum ! On the monowall forum nobody said a word for few days already :)   LE:I have to correct the last statement to be politically correct  ,i finally got some feedback over there too regarding some other issue.Better later than never.

ok – i will check that and report back thanks, hardocp

You should start with the hardware sizing guidance page, which includes sizing guidance for VPNs: VPN - Heavy use of any of the VPN services included in pfSense will increase CPU requirements. Encrypting and decrypting traffic is CPU intensive. The number of connections is much less of a concern than the throughput required. A 266 MHz CPU will max out at around 4 Mbps of IPsec throughput, a 500 MHz CPU can push 10-15 Mbps of IPsec, and relatively new server hardware (Xeon 800 FSB and newer) deployments are pushing over 100 Mbps with plenty of capacity to spare. Supported encryption cards, such as several from Hifn, are capable of significantly reducing CPU requirements.

The Cisco 1231 can be found used on ebay for fairly cheap as well.  If you have any support contracts with Cisco, you'll be able to update to the latest firmware.  They've been around a long time and don't support 802.11n or standard 802.3af (POE), but are the most reliable access points I have ever worked with.  In the US, the model number to search for is AIR-AP1231G-A-K9.  You can usually find quantity auctions on ebay if you need more than one unit.

Something like this help you out? http://www.rad.com/10/Fast-Ethernet-over-T1-NTU/2541/

I use Alix in MonoBSD imaged, u disk images in Sizes (512MB, 1GB, 2GB, 4GB) But I have a 8GB CF, how do I use the maximum disk?

thanks I change old NIC realtek (WAN) with other realtek NIC i will try and tell you. thanks

@jimp: It would show in the GUI. The most common reason would be that you turned on SSH and it's alerting you that the keys are done. Or it could be anything else (filter rules didn't load, config error, etc) Thanks jimp! Phew, when you said alert, I started to thing hardware failure! It was simply that the SSH keys had been created :)

rum is the FreeBSD driver for an older generation 802.11g USB chipset.

That was the problem for me as well. I removed the MAC cloning, ran ifconfig re0 -promisc Promisc mode is off and everything works. Good to know. This is what jimp said about using the physical + logical (parent + vlan) in http://forum.pfsense.org/index.php/topic,22921.0.html: using the parent interface along with VLANs has always been discouraged. It's not good from a security standpoint, and it also breaks other functionality such as Captive Portal. That said, while it is discouraged, it should probably continue to work [in 2.0?] if possible, since it does on 1.2.x. It would be a POLA violation to break it unnecessarily, and it could lead to machines upgraded in this state being broken/unreachable post-upgrade. In most (all?) situations, it's better to tag all VLANs on a trunk port and use corresponding VLAN interfaces on pfSense. I did a search for "vlan" and "spoof". there are lots of interesting results with many people trying to clone a mac on a vlan interface with no traffic.  can anyone familiar with vlans on pfsense tell me why spoofed macs are so problematic with vlans?

Thank you all for your answers and time. I couldn't find any other same sort of problem from FreeBSD PR database (I didn't spend hours to search). This card was only nice to try/have. So it's not so big problem to me as it's not working correctly or at all. Like I said thank you for your time. P.S. If there is someone from Finland and want to have this card for experimental use, please send a PM. -Miika

@jimp: Works great. Has for months. Problem solved!  ;D

Hi there, I'm having the same issue on a Dell R300 server with a quad Intel. Used to work fine on a 1.2.2 version but since the upgrade we got a degraded performance on a net to net transfer, no such probleme when transferring over internet. Have you managed that issue now? r@

I seem to recall that Intel reorganised their FreeBSD LAN drivers so that support for  some of their newer devices moved from em driver to igb driver. If you were upgrading from 1.2.3 to 2,0 and your system was affected by this and you didn't look hard enough at what was reported on startup it would appear that your NICs weren't recognised. Fix: just reconfigure the interfaces at the startup dialog. If your WAN used to be em0 say its igb0 etc