ok tanks  ;D

Under status - Traffic viewer.

Thanks all… =)

Awesome,  Works like a charm. Thanks again.

The driver is from FreeBSD, iirc. Not sure if Dell/Broadcom actually contribute much at all. The tricks I put on that wiki page have stabilized the cards for most people I've worked with that have bce.

Further update: Perhaps it is already off topic but since it is the same machines I am referring to so I put them here. Finally I have replicated the crash under a test condition and found that it is the NIC that have been causing the problem, all the problematic servers are using the same NIC with the driver: dev.dc.0.%desc: Macronix 98715AEC-C 10/100BaseTX The crash occur after "TX underrun - using store and forward" message appeared during a network stress test(downloading large files). Hence I start looking at the NIC, replaced with another brand and everything works like a bliss, not even TX underrun message popping up. Both RealTek and DLink NIC works happily. Poor thing I have been spending weeks torturing it with CPU and HDD stress test scripts and it end up the real culprit is the NIC :/

@josueharos: How did you properly enable bridging. I want to setup a pfsense box as a filtering bridge using only 2 NIC (WAN – LAN) to filter traffic passing through a wireless link we have, without messing with NAT. Can you post some info about it, Thank you You should consider third interface for management

Hi jigpe, I'm using pfesense 2.0 but I think it's radius because using have to login captive portal after successful authenticated. They can get this access. If we use squid we can  only apply on web traffic. Please kindly advise.

To reset the web interface you use the console and then assign the IP to the LAN interface again. Then the webGUI will revert to http. This will give you back access to you box - but will not help you with your cert prob.

Is this what you're using? I have read through your document, I congratulate you on actually writing stuff down!  :) However I have a number of questions about your setup. 1. Why are you using Manual Outbound Nat? Auto should take care of everything, you don't have a particularly complex setup. 2. Are you running DHCP servers in the switch? Usually you would run dhcp in pfSense and have it's interfaces set as gateway for your clients. 3. Why do you have IP addresses on each VLAN in the switch? This seems unnecessarily complex to me. Admittedly I've not used a pro-curve switch so I'm unfamiliar with the details. 4. What is your WAN firewall rule for? It allows packets originating from the WAN IP address to enter the WAN interface. It does nothing except possibly open a hole in your firewall. Generally speaking though I agree with what Nachtfalke wrote above. Add an extra interface (or VLAN interface) and put lightspeed at the end of it. Route traffic to in and out of it. Steve

This board supports 2gigs of memory max. Not a big deal, probably just going to end up using it as a router only.  I did see a package in the package section that allows for hosing a website on the server though if I decide to do that.  If I do that though it will be a light traffic website that won't put the processor to much more use. If I need to upgrade the server later to something that supports more memory I will at that time, not to big of a deal.  This is just something to get started with.

You got it