@bazz: Well … don't I feel stupid ... Seems that one the two switches inbetween was the problempart. That'll teach me not to start from the beginning and trust on network drawings. Even though, for those contemplating buying a Jetway with intel controllers and getting scared of all the talk. It's working great here, just remeber to check your switches when you are having problems. Happens to everyone.  I had a switch that refused to work with class 'A' IP range of addresses.  It took quite a while before I could convince the company to either buy a new managed switch or change to class 'C' IP range.  As is typical of most accountant types, the owner went for changing IP range instead.  lol.. Your Jetway belongs to the Industrial line though, I'm not too confident that it is a reflection of their regular line which uses Realtek NICs.  Even my Intel D945GCLF2 had it's realtek NIC semi-die (flapping connection) on me in a year.

Hi, you were both right, sorry for bothering you with that topic. I followed the tuning instructions in the post of stherr and now everything is working fine. It seems to be the kern.ipc.nmbclusters problem which wallabybob mentioned in his post. My apologies for not finding the forum articles you mentioned (I was looking for "problems with multiple NICs"). Many thanks for your quick help !!!

I assume you mean 50Mbps? If so then you should be OK. According to Netgate: Maximum throughput with filtering enabled: NAT - 85 Mbps Routing - 85 Mbps Bridge - 85 Mbps 50MB might imply 400Mbps which the ALIX can't cope with.  :P Steve

They work on my Jetway NC9C-550 and pfSense 2.0 Release.  I've seen another post where someone was having problems getting his 8111E recognized but it wasnt a Jetway board if I recall correctly.  There might be variants of the 8111E chipset.

The Atom will help lower your power consumption, but so will a new Sandy Bridge CPU. Even the lowest end Sandy Bridge, Pentium G620, will FAR outperform an Atom, yet with similar power savings. I just built a system that uses 36 watts when idle. The CPU is a Pentium G620 and the Motherboard is an Intel S1200KP mini-itx board with dual Intel gigabit NICs. At 36W, powered on 24/7, PG&E (my power company in California) estimates this box will cost me $42 a year to run.

I`ve found this on other website ;x someone has the same problem,,, but yes,,, kldstat show this module loaded,,, but i think it doesnt replace re driver because my interface doesnt show ;x but hmm,, there is info that module loaded but at the end there is info error 22 ;x Do you know  when exactly the new build will show ? cause i need it to be set up now ;x so either i run it with USB adapter or i`ll try diifferent DISTRO that recognise my interface ;x

50W seems completely reasonable to me for a 200Mbps connection. Do you need to use new hardware? My own Pentium-M based system draws less than 50W and is good for 400Mbps+. Steve

Ok, It now works like a charm. Had to go in the BIOS setting to disable the UART port of 81216D. And change the setting of the fourth serial port to be 3E8 and IRQ 5. FYI. Thx everyone (and most particularly Steve) :-)

The most important factor in sizing your hardware is throughput. What sort of WAN connection do you have? Also that server came in a variety of configurations. What cpu(s) do you have? Steve

Hi, you should think about more than 2GB of RAM. Squid is using RAM caching, for indexing HDD cache and so on. Chose lower HDD (60GB is enough) and use 4GB or more of RAM. Just for your information: I have got 4GB system memory I am using 30GB od Hard Disk Cache for squid I am using 1GB of memory cache for squid. I am using squidguard And my overall RAM usage is always more than 75% I am using this CPU: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz I have got 2x 16MBit/s down and 2x 1MBit/s up. CPU usage is in general lower than 5%. Sometimes it growths up to 10% or 15%.

@stephenw10: The first thing to do is hook up a serial cable to the box and login to the console directly. That way you will know for sure if it has really crashed. If it is really crashing the first thing I would check is the power supply. This. If it is actually crashing, i.e. it's not responsive at the serial console, then it's most likely the power supply has flaked out. I don't hear much of the boards actually dying, probably less than 10% of failures like that, but hear about power supplies dying on occasion. That comprises probably 90% of the ALIX hardware failures I've heard about.

In a similar vein, a lot of Juniper equipment used to be x86 hardware, connected to a board board with custom ASICs and the ports via a regular Cat5 cable.  The board would handle all of the simple routing, but would pass anything else back to the x86 hardware for more complicated processing. I don't know if anyone ever ran any FrankenJuniper equipment, and they've advanced pretty far beyond that so I don't know what the CPUs are now, but it's a pretty interesting thought nonetheless.

That's been reported by others as well, there's something about that card that doesn't play nicely with stock OSes.

Until some intrepid coder comes long and completely rewrites the menu system to be fully user-configurable… Then we could have a "classic" menu layout that never changes, something else that may be completely different but in some regards more logical, and a third or n+1 option in which users could rearrange things however they want. Sounds fun, but something that would have to gain some funding or have someone step up and just do it.

Dear Steve, thanks for your idea, but in this case I don't have any switch supporting VLANs. But in the Italian pfSense forum I found: www.firewallhardware.it and in paticular: http://www.firewallhardware.it/appliance_utm_evoluto.html Do anybody know this appliance? by Alex

@jpmtg: I will work on testing via live cd next time I am on site. That would be a good plan and without wrecking your existing install, get the most basic config possible to get online and see how that's diff.

Great :) the 10G network switch out of the c7000 has 4 XFP's. Modem                          |                 –------    -Firewall-     |         |   |          |   DAS     -Server - Switch1 - Switch2-             |                                     |             ----------------------------- This way everything is on a 10GB backbone. Firewall - HP DL360 G4 ( Dual Xeon 3.6Ghz 8GB RAM 2x72GB U320 Drives Running RAID 1 ) Server - HP c7000 Blade Enclosure - Currently 2 x BL480c G6's - 2x Intel X5460 - QC 3.16GHz, 24GB DDR2 667MHz Fuly Buffered ECC SDRAM, 4x 72GB 10K SAS Drives DAS - HP MDS600 Switch 1 - HP ProCurve 3500al-24G-POE Switch 2 - HP Procurve 2910al-24G-POE Basicly I'm doing  some home reno's and ran a 60' 12 strand 9/125 Single mode fiber drop from attic to basement utility panel into a 24 port Wall mount fiber enclosure, from where there is a second 50' 12 strand 9/125 Single mode fiber drop from the utility panel to my office where the server is. The reason why this was done is for future expansion as FTTP ( Fiber To The Premisses ) is due to arrive in the next coming months in my neighborhood for gigabit internet connections. At this time i only have Switch 2, and might be buying a second one instead of the 3500

I have given up to install pfSense 2.0 on a system with the Intel board DH61WW. It looks as if the problem is the newer 82579V NIC, but it might also be s.th. else. Nevertheless, Fedora 16 installs almost without problems. The system freezes if the onboard NIC is active when starting the Fedora Live CD. After disabling it, installing the OS, and updating the system, the NIC can be activated again and then the system and the NIC work smoothly. There were too many patches to see which drivers and chipset related packages were updated. There is a short article on phoronix.com about FreeBSD on Sandy Burst systems, which seems to suggest not use Sandy Burst boards at the moment, although none of the problems described there seem to be relevant for my setup.

Old laptop or Nokia box from eBay doesn't fulfil the requirements: @torontob: No moving parts MUST be able to run pfSense and I do intend to run pfsense Not be an end of life product or hard to find as I might want to get few hundred of time over time. Not that I can think of anything else!  ::) Steve