Saw this and thought I would reply...

I have recently just tried this, as I have tethering available on my iPhone.   Seems the iphone requires ADHOC connection to connect the native IOS Wifi Hotspot.   In Pfsense 2.0.1, if I configure my wireless interface as ADHOC, the machine reboots and I get a kernel panic over and over again upon reboot until I physically remove the card.  I've tried this multiple times, not sure if it's my on WRAP having issues, or maybe my Artheros card.

Anyone gotten an ADHOC connection working in Pfsense 2.0.1?  This is probably not something that is used/configured all that much.

I have in-bound load balancing working perfectly between two HTTP servers.  I want to add a third HTTP server to the pool, would that cause the SLBD daemon to stop/restart resulting in an brief outage?  Or can I add servers to the pool on the fly and not have the existing connections be affected?

Well,  I need to eat what I posted earlier.  I ran fine the entire day yesterday across multiple reboots in Vista.  Today I booted in the AM and the same problem rears its ugly head again.  I can ping the Pfsense box, but I cannot get through the Pfsense box to the internet?

Anyone have any ideas?

I am having terrible problems with Vista and using Wireless with Pfsense 1.2RC3   Vista works fine with an old WRT54G WAP, no problems.  Same machine, booted with Ubuntu works fine as well connecting to the Pfsense box via wireless.

I have found that running vista and associated with the PfSense wireless, that I can get an IP address.  I can also ping the interface of the Pfsense wireless card, as well as the LAN interface.  When I try to ping through the Pfsense box to the internet, I get about 75% packet loss.   Immeadiately boot Unbuntu on the same hardware/setup and thing are fine.

This has been going on for about two weeks, and had me frustrated, until I found:

http://forum.pfsense.org/index.php/topic,2098.0.html

I know it's a locked topic on the forum, but as soon as I ran the command "netsh interface tcp show global" as administrator everything works fine? 

I just loaded 1.2-BETA-2 to see if there is any difference....  I am importing my config from 1.01 to the Beta for 1.2.  Maybe I should start clean and not import my config and see if that helps...

I am assuming that since 1.2 is based on FreeBSD 6.2 that will will continue to have problems with wireless...

Wireless in FreeBSD 6.2 seems to have some issues that cause the interface to drop. No known solution at this time. Do you see anything in the logs at the time of failure?

I was able to check out the logs tonight right after the wireless took it's dump.  Here is what I saw:

Jun 30 20:28:41    last message repeated 3 times
Jun 30 20:36:11    kernel: sis0: discard frame w/o packet header
Jun 30 20:36:47    last message repeated 4 times
Jun 30 20:36:54    kernel: sis0: discard frame w/o packet header
Jun 30 20:36:56    kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jun 30 20:36:56    kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jun 30 20:37:19    kernel: ath0: device timeout
Jun 30 20:37:20    kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jun 30 20:37:20    kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jun 30 20:37:37    kernel: ath0: device timeout

I am having to reboot the WRAP box about twice a day because the wireless problem...

Make sure your bios is the latest version.  This can happen with prior bios versions.

I've been running 1.11 for some time...  anything else to check?

I've been running 1.01 for months on a WRAP Board with a CM9 wireless card without any problems.  I just upgraded the WRAP to 1.2-Beta-1, and after every few days I get the following errors in the Logs, and the Wireless stops working:

Jun 27 20:36:33    kernel: ath0: device timeout
Jun 27 20:36:34    kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jun 27 20:36:34    kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jun 27 20:36:43    kernel: ath0: device timeout

Anyone know why this is happening?  The only way to reset is to reboot the machine.  If I go back to 1.01 everything is fine?!?!?

I have just installed snort on a 1.2gig P3 machine with 2gig of Memory.  I cant get Snort to run in any other performance mode but "lowmem".  What gives? Do you really need 2gig+ of memory to run Snort?

Guess it should be able to handle that load as you "only" have 8 mbit/s. I tested a wrap here at a 16 mbit/s adsl2+ and gave it a hard time (p2p, multiple ftp downloads, etc) and it didn't break though it was not able to deliver the full speed and the cpu was heavily loaded. Just give it a try and monitor cpu load at status>system. If you get the latest snapshot there are some rrd cpu graphs now too 

I have a WRAP running 1.01 release here at work running on a 45meg link.  I can only get throughput of about  16mbit/s on it which is right in line with what Hoba is experiencing.  I have tried all the tweaks in the config (polling, etc etc) and 16meg/s is about the most I can get out of the WRAP box.  Polling made response time jump about 10x (~1ms to ~10ms) but I didnt really see any bandwidth improvement...

I have an IBM xSeries 330 with dual PIII 1.13GHz procs, 1Gig RAM, 3Ware IDE RAID controller and 2 WD 20Gig Hard drives.  The server has 2 built-in 10/100 MB/s interfaces.  When I put the 0.90 LiveCD in the system and boot it hangs after recognizing the second CPU

SMB:AP CPU #1 Launched!

No errors nothing any idea?

Thanks

Did you find any resolution to the origional problem?  I have a IBM x330 with the exact same problem booting 1.01 from CD.  Even installing to HD make no difference.   I've tried all the comments people made above, but it still gets stuck here booting for 4-6 minutes, and then continues???

I've seen some pretty nice Network Diagrams in the posts in the forums.  What are people using to do network diagrams?  I know there is Visio, but it sucks IMHO...  Any opensource diagramming apps for networking?

I have been beating my head aginst a wall for the last couple of hours.  We just got/installed new Cisco 3560 gigE switches.  Seems that the interfaces and Pfsense WRAP boards do not play well together.

Forced the ports on the switch to 100meg/Full and Pfense didnt see interface as full deuplex and was causing errors due to duplex mismatch.  I tweaked the Config.xml file via the tips in the FAQ, and forced the sis0 and sis1 to full... still got CRC errors and collisions.

Only way I could make things work was to leave the XML options in place to make sis0 and sis1 to full in Pfsense, and then set the Cisco interfaces to auto speed and auto duplex. 

Just a FYI in case someone else runs into this...

Destinations are passthru MAC's so I am not sure what could be up... Let me know if I can post any info.