Nope, a bunch of development stuff came up to occupy my time and my support staff is occupied with day-to-day troubleshooting, new hires, etc., and having them replace perfectly good hardware isn't high on the list when I've got a rack where every switch needs replacement (some defective, some full, some ancient).

Hi Guys Thank you very much for your feedback. Sounds great i think i will process with this setup. If i have it up and running i will write a full review about it  :) cheers Mario

Should be supported by the igb(4) driver: http://www.freebsd.org/cgi/man.cgi?query=igb&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&arch=default&format=html Steve

Myricom 10G-PCIE2-8C2-2S+E is the solution(https://www.myricom.com/products/network-adapters/10g-pcie2-8c2-2s.html). It has driver called mxge that is having altq option compatible with freebsd 8.1 . the page on pfsense portal does not mention mxge (http://doc.pfsense.org/index.php/ALTQ_drivers) but freebsd 8.1 official page does (http://www.freebsd.org/cgi/man.cgi?query=altq&apropos=0&sektion=4&manpath=FreeBSD+8.1-RELEASE+and+Ports&arch=default&format=html).

I believe he found another means of sale.  I was first to reply and never got a response after March 20th.

You're running it out of RAM and filling up the RAM disk also. Squid on NanoBSD cannot do logging. There isn't enough room to log to the RAM disk (/var or /tmp) and the CF is read only most of the time and thus not suitable for logging. If you need to have a full-featured squid platform, you'll need to be running a full install on a hard drive or SSD.

Pretty sure even the first 10base2 NIC I had could do better than 3sec ping!  ;) (though I don't think it was running an IP stack so probably couldn't ping at all) Steve

Since having the WAN connected it boots quicker and the webGUI itself is much more responsive which per another thread i knew would happen, but its still a nice change

Yes the speedtest.net client uses 2 or 4 connections depending on the speed. It works great as you can see.  :) There are other interesting things you can do such as failover and policy based routing. Steve

@rjcrowder: Not sure on the Buffalo dd-wrt version, but the standard dd-wrt definitely lets you map WAN to LAN. fingers crossed!

Yes, here it is: http://www.osnet.eu/en/content/firewall-fwa-3030#content But I just noticed that I made a mistake. The box doesn't have 7 ports but 6. I mixed that up with the ibm servers I used for a customer, they all had 7. I've edited my first post. However there are also pci-e expansion slots available so one could upgrade it with a different case then. Or add any other cards.

My android phone works just fine

I am also unable to find a seller for this board.

ill stream and download a few things at once and check what the device is up to and post

I know that the X520 works in 2.1, not sure about 2.0.2. Anyway, I'd probably go with a single E5-2643 in each box.  That will give you the best chance of hitting 8Gbit/s, though I'm not sure it will actually do it.

Thanks everyone for your help.  Although 2.1-BETA did fix a couple issues I was having, it did not fix the issue with the serial ports.  The pfsense menus seem to require you have a NMEA GPS (refclock 20) so if you want to use a different refclock you'll have to hack on /etc/inc/system.inc to generate the right stanzas in /var/etc/ntpd.conf.  I stopped the ntpd service in the menus then jumped to the shell and ran ntpd by hand /usr/local/etc/ntpd -D3 -c /etc/ntpd.conf still no joy with the serial port.  I have symlinked cuau0 to both /dev/oncore.serial.0 and /dev/oncore.pps.0 and also have my /etc/ntp.oncore.0 config in place which enables TRAIM and mode 1 (zero position mode).  No Joy. /var/log/ntp/clockstats shows driver timeout on @@Cj (get config) command sent to the device same as before. 56382 82497.628 127.127.30.0 ONCORE[0]: ONCORE DRIVER – CONFIGURING 56382 82497.639 127.127.30.0 ONCORE[0]: state = ONCORE_NO_IDEA 56382 82497.641 127.127.30.0 ONCORE[0]: Input mode = 1 56382 82497.643 127.127.30.0 ONCORE[0]: Initializing timing to Assert. 56382 82497.645 127.127.30.0 ONCORE[0]: ONCORE: Can't open SHMEM file 56382 82497.647 127.127.30.0 ONCORE[0]: ONCORE: Can't open shmem 56382 82497.649 127.127.30.0 ONCORE[0]: state = ONCORE_CHECK_ID 56382 82498.514 127.127.30.0 ONCORE[0]: Oncore: Resend @@Cj 56382 82514.514 127.127.30.0 ONCORE[0]: Oncore: Resend @@Cj 56382 82530.514 127.127.30.0 ONCORE[0]: Oncore: Resend @@Cj 56382 82546.514 127.127.30.0 ONCORE[0]: Oncore: No response from @@Cj, shutting down driver It looks like this is an issue with the motherboard/BIOS settings or somesuch at any rate I'm happy with 2.1-BETA and an busy building a new refclock based on a Raspberry Pi with the Adafruit 66 channel gps which will replace my old Motorola as my primary NTP server.  I've got the Raspberry Pi ready to go with linux kernel pps and latest ntpd build just waiting on the Adafruit gps board.