@Jason: @nuro: I forgot to mention, the link graph on the cisco shows 1000's of packet errors after 2 or 3 minutes after the port is re-activated. Are both pfSense systems plugged into the same Cisco switch?  If so, are they in the same physical block?  Most switches use multiple controllers inside and I've had a couple flake out and either not establish links or experience high packet loss but only in a certain 8- or 16-port block (out of 48 ports). EDIT:  Also, try fixing both the switch and your pfSense boxes to 100 FD if either is set to auto-negotiate.  I recently had an issue with a new carrier and not being able to get more than 2Mbit/s upstream.  As soon as I changed the ports it spiked up to 20Mbit/s (what I'm paying for). The two servers are on separate switches, but the nics for each machine are on the same block. I'm going to try your suggestion and shuffle things around a bit, and set the port to 100 FD. Thanks.

There is one more thing I can add. I have got a bunch of settings that were recommended to me and/or others suffering from stuck beacon issue back in the 1.2.3. sysctl dev.ath.0.txantenna=1 sysctl dev.ath.0.rxantenna=1 sysctl dev.ath.0.diversity=0 sysctl dev.ath.0.tpc=1 sysctl dev.ath.0.tpscale=1 ifconfig ath0 txpower '12' ifconfig ath0 mtu 1500 ifconfig ath0 bmiss 7 ifconfig ath0 bgscan ifconfig ath0 bintval 500 You are welcome to try those settings (they did help me somewhat during the 1.2.3 days) ,but I haven't tried them yet in the 2.0 as I only got one stuck beacon so far after 3 days of uptime and wifi seems to be stable so far. I had them in a shellscript that I ran manually everytime the firewall rebooted.

Please ignore. Didn't know I was supposed to add it in advanced/misc properties. Strange that it didn't stick after upgrade though.

Hi wallabybob, thx for the help. I try an other Stick with fat16. With commad mount_msdos /dev/da0s1 /mnt all going well. bye gucky66

SOLUTION: In SIM-card, set PIN (/-request) to OFF, using an ordinary mobile phone… thats it. This took 15 hours......... Working like a charm now.

I only found 3 from SuperMicro that will fit the bill: RSC-RR1UE-AXL (PCIex8 -> 1x PCI-X) ($60-90) CSE-RR2UE-AX (PCIex8 -> 3x PCI-X) ($99-140) RSC-R1UEP-A2X (PCIex16 -> 2x PCI-X) ($90-110) I've been told that some of the SuperMicro stuff is proprietary to their boards as well. I also got an e-mail back from PLX and they don't sell direct to end-users and wouldn't give me a list of resellers (odd).  I don't really want to spend a lot of money either.  If anyone is interested, I'm willing to trade both of my cards for one Intel Quad-Port PCIe card, two Intel Dual-Port PCIe cards, or even a mITX/mATX board with dual intel NICs.  pfSense compatible of course.  PM me if you are interested.

I use a pfSense 2.0 box at home with Apple Extreme and Express units as APs.  You just won't use the WAN port on your Extreme and will need to disable DHCP.

I'd suspect the controller or cabling (and if that really is SCSI, termination).

EDIT : Error, I create a new topic for my problem ( http://forum.pfsense.org/index.php/topic,41937.0.html ).

The Hifn cards are only moderately-useful with a slow CPU.  There's actually a decent shot that using it with that CPU will slow you down.

any info about this?

Looking at the other posts i might go for a sandy bridge setup.  At 500mhz for 87 1000meg network equils roughly 5750 mhz.  Assuming the network card drivers can at least have a thread per processor per card thats a 2.87 ghz duel core or above. I know we wont have gig too soon but my mate in sweeden is already on a 1 gig connection just as i got my 100 lol.   (he only see's 300 currently no dobt because of his network gear) Might as well build it to last. I was thinking about a a Pentium G850 (duel core) which is rated at 2.90GHz.  Is this thinking sound? How does pfsense or rather BSD make use of the cores with network cards?  Would a quad give more headroom for the firewall if it was only running the two interfaces (with an intel or other nice onboard network).

I have had good results from the TP-Link TL-WN321G and Tenda W311U, both USB devices, both use Ralink chipsets and both support AP mode. The Tenda is supported by the run driver in pfSense 2.0 (but not in earlier versions). The TP-Link devices I used had an older version of the Ralink chipset and were recognised by the rum driver in pfSense 1.2.3. It appears newer versions of this device need the run driver. I have had good results from the TP-Link TL-WN651G PCI card with Atheros chipset. It appears this card has been superseded by the TL-WN350GD. I have no experience with mini-PCI cards on pfSense though Atheros cards seem well regarded. PC Engines (http://pcengines.ch) sell a range a mini-PCI cards with Atheros chipsets. However, if I recall correctly, they don't sell direct to EU customers. The web site has links to web pages of distributors in a number of other countries.

Does your WAN link use PPPoE or DHCP? Can your provide some lines (say 10 to 20) from the system log BEFORE and after the apinger line you quoted?

Problem solved. The traffic shaper was the bottle neck.