@erack:

Since this probably won't be fixed in a timely manner, anyone have a recommendation for another 4-6 port Intel-chipset NIC that is compatible with the SuperMicro Atom boards?

And if anyone has one they want to sell, I'll trade the PEG6I for it.

The post from Gluon99 reminded me that I have seen hints of Intel chips packing 4 NICs into the one chip. Investigations a few years ago suggested some of the Intel 2 port and 4 port boards might have all the NICs in a single chip. I suspect the absence of a bridge will enable such boards to work with the Super Micro motherboards.

@Lee:

I have never seen a "card" that makes a better AP than a good AP.  So right now I have an EnGenius EAP300N plugged into an Ethernet port.  Less headaches…

Ditto.  I use Apple AirPorts though.

Just booted mine up with a Celeron G530 and 2gigs of ram. Latest 2.1 x86 snapshot. I get kernel panic's with 2.0.1. Waiting for my Travla C292 case. Might have to change the cpu cooler due to the pci-e riser.

@gregober:

But I am absolutely unable to have the output sent to COM1 port with the standard i386-2.0.1-NanoBSD (no VGA) install.

I presume you mean you don't see anything on the COM port. What are you using to read the COM port?

@gregober:

I have tried all possible combination on the BIOS setting… nothing works.

Does this mean you can see BIOS output on the COM port?

@gregober:

I was able to run It smoothly using a i386-2.0.1-NanoBSD-VGA install

You saw output on the COM port when running the VGA version of pfSense?

I would check
1. The cable connecting to the COM port is correctly wired - do you ever see any output from the COM port?
2. FreeBSD runs the COM port at the same speed the BIOS runs the COM port. From memory, by default FreeBSD runs the console port at 9600bps.

@rfischer1984:

oh ok, thanks. I was just concerned freebsd may have issues with a newer processor or something. Thanks

There are sometimes issues with driver support for "new" chipsets. To try to reduce such problems I would get a motherboard for FreeBSD only if the chipset had been widely available for at least six months before the release of version of FreeBSD I was planning to run. Or, I would select a motherboard/CPU with virtualisation hardware so I would have the option of running pfSense in a VM to try and hide the new (and possibly troublesome) hardware.

thank you for the response,and I just solved the problem.  ;D

they are builtin NICs.

to fix the problem you have to reset the NIC to its defualt config. everything I found online pointed to a utility called IBAUTIL.

"IBAUTIL WILL NOT WORK" that is the old version and it only shows one out of two NICs….

it has been replaced with BOOTUTIL which can be found here http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=19186 .

copy the bootutil.exe from the dos folder to your dos bootdisk

the command I ran was "bootutil -nic=1 -defcfg"

if you try to do all or nic2 it will give you an error....

@bucky31:

I have a Dell R610 server that has a PERC H200 raid card. I am running into issues with the install where it isn't detecting a drive. I've read some older posts that mention PFSense does not have support for this particular RAID card. Can someone confirm if this is true or not?

The H200 is based on the LSI 2008.  The 2008 isn't supported until FreeBSD 8.3.  Since pfSense 2.0 is built on 8.1, it won't work.  The 2.1 development snapshots are built on 8.3 though so I think it might work with those.

http://snapshots.pfsense.org/

Server doesen't boot with 1.2.3 version of pfsense from boot cd i get invalid boot drive :( what version should i try on this arhitecture ? server model ibm xseries 220

Cool , working pfsense 2 on ip380.. ;D ;D ;D ;D ;D ;D ;D.

I installed xp on the laptop ( had to after i made the mistake of booting pfsense cd and choosing quick install, it wiped my laptop drive ..but anyway)

Then i added oracle viruabox and warftp on laptop.

Plugged the nokia hard drive into a usb adapter and mounted the raw disk to a virtuabox disk.
Booted virtual machine with pfsense 2.0 live cd and completed the quick install , chose console & no vga with keyboard. Selected exit and stopped the reboot.
Mounted the hard drive ….
give ip address to virtuabox ethernet with /sbin/ifconfig
start warftp and share new kernel dir on xp...
ftp to laptop & transfer new kernel files into /boot/kernel on viruabox
reboot,
install disk in nokia ip380 & connect console.
Working like a charm !!!!!

Should be the parallel port and the driver is named "Watchguard Firebox with SDEC". If that does not show up, you don't have lcdproc-dev.

I have had success with Atheros AR5008. In mode hostap too. But have trouble with low signal.
Do you have had success and found a card?

Thanks Steve,

I did all the upgrades on my existing X750e, 2 GB of Memory and $4.00 CPU and it works great, I was looking for another Firebox and you confirmed my suspicions.

Mike

NID_NOT_FOUND is fine. http://doc.pfsense.org/index.php/DMA_and_LBA_Errors

runtime went backwards is generally indicative of a BIOS bug breaking timekeeping. Disabling ACPI or changing kern.timecounter may work around that if it's a persistent issue.

I have used a Trendnet TU2-ET100 USB to Ethernet adapter and it worked great. It uses the Asix chipset I believe.

If you guys want in on this there's 2 ways :
1. - Wait for 2.2
2. - Pony up and throw down some cash for someone to code in the OFED package into the existing releases.

I posted up a Bounty a while back and no one else chimed in offering to chip in.

My offer still stands and even re-posted the bounty for V2.1
The main question is how fast (bad) do you want this feature ??

@TrickyWidget:

I'm considering buying an appliance with pfSense pre-loaded, but I'm concerned about the hardware capacity.  I have a 30mbit connection and I'll want to run pfBlocker (I don't anticipate using any other optional modules).  The box has a VIA 800mhz CPU and 512MB RAM.  Does anyone know how well that would work?

Thanks!  :)

I'm running a Neoware CA10 Via C3/800MHZ with pfblocker on NanoBSD

My connection is 50mbit connection with no issues at all.

You should be fine  ;)

Thanks Steve that worked.

Hmm, OK.
The command you are using to call modeswitch is not using your conf file so that is not being used at all.
Instead the command is looking for a device with a different product ID, though it does match your own, and sending a generic Huawei code.

The device shown in your output, VID 12D1: PID 1506, appears to be either a device already in target (modem) mode or something as yet undocumented.

Do you not have any serial devices shown in /dev/?

Steve