@heper: wikipedia: PCI Express 2.0[edit] A PCI Express 2.0 expansion card that provides USB 3.0 connectivity PCI-SIG announced the availability of the PCI Express Base 2.0 specification on 15 January 2007.[26] The PCIe 2.0 standard doubles the transfer rate compared with PCIe 1.0 to 5 GT/s and the per-lane throughput rises from 250 MB/s to 500 MB/s. This means a 32-lane PCIe connector (×32) can support throughput up to 16 GB/s aggregate. PCIe 2.0 motherboard slots are fully backward compatible with PCIe v1.x cards. PCIe 2.0 cards are also generally backward compatible with PCIe 1.x motherboards, using the available bandwidth of PCI Express 1.1. Overall, graphic cards or motherboards designed for v2.0 will work with the other being v1.1 or v1.0a. The PCI-SIG also said that PCIe 2.0 features improvements to the point-to-point data transfer protocol and its software architecture.[27] Intel's first PCIe 2.0 capable chipset was the X38 and boards began to ship from various vendors (Abit, Asus, Gigabyte) as of October 21, 2007.[28] AMD started supporting PCIe 2.0 with its AMD 700 chipset series and nVidia started with the MCP72.[29] All of Intel's prior chipsets, including the Intel P35 chipset, supported PCIe 1.1 or 1.0a.[30] Like 1.x, PCIe 2.0 uses an 8b/10b encoding scheme, therefore delivering, per-lane, an effective 4 Gbit/s max transfer rate from its 5 GT/s raw data rate. –------------------------------------------------------------------------------------------------------------------------------------ PCI Express 2.1[edit] PCI Express 2.1 (with its specification dated March 4, 2009) supports a large proportion of the management, support, and troubleshooting systems planned for full implementation in PCI Express 3.0. However, the speed is the same as PCI Express 2.0. Unfortunately, the increase in power from the slot breaks backward compatibility between PCI Express 2.1 cards and some older motherboards with 1.0/1.0a, but most motherboards with PCI Express 1.1 connectors are provided with a BIOS update by their manufacturers through utilities to support backward compatibility of cards with PCIe 2.1. my bad, thanks for educating :)

The SG-8860 1U variant is available now: http://store.pfsense.org/SG-8860-1U/ There will be a 1U 4860 coming soon.

It also depends on your definition of "small".  Refurb SFF (small form factor) PCs like the Lenovo Core2Duo units are 12.5" W x 14" D x 4" H.  That size comes with (1) low-profile PCI and (1) low-profile PCIe slot (probably x8 or x16). There is also the "ultra-small" variant which is 10.8" W X 9.4" D X 3.1" H - but that only has a single PCI slot (which is okay up to about 200Mbps?). The Lenovo M58 series units come with a single Intel NIC, which is a big positive for them. You can easily add a 2nd low-profile Intel single/dual port NIC for not too much.  Mine draws about 38-40W idle and 50-65W under heavy load.

That's what it seems like from the Google results I was looking through. On similar if not identical HP servers you can find Linux boot log output that says something along the lines of x2APIC broken, disabling. Trying the most recent FreeBSD 11-CURRENT snapshot might be telling, in at least determining whether or not it's still a hardware issue, or if it's one that's been worked around in software. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/ not that it'll help you at this instant, but it's at least another data point. Booting a Linux distro and looking for logs along those lines might also be telling.

That's an old enough one to be x86. If they haven't done anything to restrict what can run on it, it'll probably work. I'm guessing it's probably restricted in some way that makes other OSes not work. That's a really slow piece of hardware, IMO it's not worth the effort to try.

My SFF refurbished Core2Duo system (Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz) only draws 38-40W idle and 55-65W under load.  Best part is that the box only cost about $85.  I paid more for the dual-port Intel NIC and the SSD. I reached the same conclusion as others after pricing out the 10-25W systems.  The cost savings per year (at $0.12/kWh) weren't enough to pay for the higher cost of the compact systems. The other factor is that with the SFF PC only being $85, I'm not as worried if it fails because I can get another.  Or even keep a spare on the shelf.

Thanks! So it should work with any atheros card? I'll give it a try.

Hi, Your last post was in March and I am not sure you are watching this thread but in case you are: can you share the specs of you pfSense hardware in where you plan to install these 40G cards? Martin

As one with no commercial interest in what hardware you buy, I will put in a plug for the SG-2440. I have a couple of them now. They work and I know they are hardware that will be in the standard test suite for some time to come. If you are buying a "million" units, or are somewhere where it is not viable to buy from the pfSense store (or whatever other "pfSense store" international sellers come) then sure, evaluate the possible hardware alternatives, ask the pfSense store guys for some sort of bulk rate… But if the hardware on the pfSense store suits your number of ethernet ports, hardware form factor and performance needs then just buy from the pfSense store and support the project. If non-hobbyists factor in the cost of the time spent researching hardware alternatives, messing about procuring them from some el-cheapo online site and... then the pfSense store price looks fine.

Have you fired up Sierra Watcher in Windows and made sure the SIM card is OK and everything is working properly? Reason i say that is there are no distinct error messages in pfSense if SIM is not valid. You can fire off some AT commands to verify from PPP. Note on the PPP.conf stuff. It has been changed since that post. Now using mpd5. Settings for that are in different spot. Goes by interface name. I think the modem script gets generated on interface setup and sometimes it goes wrong so it don't hurt to wipe and try again. That said i don't see a single pfSense success story with that device. Its old enough and seems to use the exact same firmware as my Sierra MC7700 but that don't mean much… My general feeling is that internal modules have much less problems than USB fobs.

did you ever get this to work?

I have never tried it personally, I've just read account of others having a hard time.  ;) There are quite a few Squid help docs to look at for examples. http://wiki.squid-cache.org/ConfigExamples/DynamicContent or http://wiki.squid-cache.org/ConfigExamples/DynamicContent/Coordinator Steve

I think that's the IPv6 issue that LCDproc had. Is there some reason why you're running 2.1? Hard to know quite what issues there might be with such an old version now. Steve

These controllers are crap. We couldn't get them to work with anything (Linux, FreeBSD) and gave up rather quickly. Just buy a regular SmartArray P420 - anything else is not worth the time.

I have a Verizon Jetpack MiFi 6620L but I can't it working in tether mode in pfsense 2.2.2-RELEASE. I believe this is because I need the if_cdce driver, which is not available on this build. I'm interested in what device the network interface device name is, which drivers are loaded in the kernel and what version of pfsense you're using. Can you provide the output of these commands: ifconfig -a kldstat uname -a Also, the usb info for the 4620L might help. Can you show the output of 'usbconfig dump_device_desc' as well?

ok, before i try the upgrade, i have the firmware      netgate-memstick-ADI-2.2.2-RELEASE-amd64-20150424-1057.img. i also downloaded the firmware    pfSense-memstick-ADI-2.2.2-RELEASE-amd64.img. my device is from negate so i assume i should use the netgate one. when i use the console setup to my pc with the command prompt it is very temperamental. after the initial connection is made, if my pc goes to sleep or the cable is removed, i am unable to reconnect. all i get is "#" after hitting enter. is that normal, and when the netgate reboots with the memstick will i lose the connection and be unable to go through the install process? and if everything goes for a #$%! can i simply remove the msata drive and have the netgate operate as it is now? thanks.

Serial console speed on 2.2+ defaults to 115200. Looks like a serial speed mismatch.

@bennyc: Seen those new black boxes recently at varia-store.com, prices in €, german distributor, who has +- normal prices compared with others. For that 2240 model, their webshop lists:  "Price: from 643,79 EUR excl. Shipping costs" rate today: USD/EUR 0,89 So you payed €488 (device+shipping) + €97 (20% tax) + €22 (bank fee), that equals about €608 incl. Shipping costs. (under the assumption you only payed once a bank fee, otherwise we need to add €25 (=$28, but not sure what you mean with your comments) Even with that 2nd fee added, you bought it cheaper than when through European retail store, but you had to cope with bank fee(s), extra tax, and of course the risk (unknown factor). Interesting. Device listing price: $353. What I payed in total: €492 Looks expensive, but don't forget that usually no tax is included in the listed prices in us shops. You only have to pay the tax for your country (where the package is imported to). The $28 were basically a buffer in case bank fees on their side occur. Not really a legitimate practice, but I did get $18 back later on. The €22 fee was the charge of my local bank for the bank check and currency change (many us companies do not provide international bank account numbers). PS: I did not find any EU reseller at time of ordering. But you are right: http://varia-store.com/Ready-Systems/pfSense/pfSense-SG-2440-Security-Gateway-Appliance::27988.html that's the same device. If the alrdy installed pfSense and the included support is important to you - that's maybe the better choice. PPS: It's possible to order the board only, thats about $100 cheaper, but the case is actually quite nice.

Hi guys, I have a "39Y6138" quad port pci card on an asus "p8h67-m pro" (latest BIOS installed) and the newest pfsense "2.2.2" only recognized two ports. I have tried many options at "/boot/loader.conf" (and "/boot/loader.conf.local" too) like: hint.agp.0.disabled=1 hw.pci.realloc_bars=1 Do you have another recommendation? Have you detected similar issue? Have you wokerd around? As I could check, there is information about FreeBSD/Debian has updated em(4) driver and it's used in the latests versions of pfsense. Thank you in advance. Best, @rofc