Fixed, I did a reinstall this morning and edited where I needed.

Thanks! I appreciate the quick response. I got the .iso.gz snapshot from 17-Jun-2011 15:58. On to the fun!

Probably ARP cache on your modem since you were switching between machines but using the same IP, and waiting a while cleared it (the reboot most likely a coincidence).

Sounds like NAT reflection isn't playing nice there. Run your GUI on another port besides 80 or 443, and disable the GUI redirect.

The snapshots are really RC2 even though the files say RC1. We never officially released RC2. Be on the lookout for RC3 coming soon with an official announcement and signed images. :-)

Thanks, now working properly. To answer your question on the router, no because it supports a fiber network and without it the fiber is not configured. Thank you for the help. cjb

Not pre-built, you'll have to build one

Hmmm, I'm not actually using squid at the moment, because I'm running embedded. Is it not under: Status -> System Logs ? You could use the lightsquid package to get nice reports of what your users are doing. Steve

Most likely cause is your upstream router's ARP cache, you'll have to get your provider to clear that.

@stephenw10: Ah, well have you checked the 'Allow intra-BSS communication' box in the wifi interface settings? Steve Nope, ticking that option fixed it. Thanks so much.  There are so many options in pfsense as a new user it is hard to figure everything out.  I apologize, if that was an obvious solution, didn't mean to waste people's time. Thank-you to everybody in this thread who tried to help me out.

Enabled the bootblocks and all is still well, many thank. On a side note, I have an extremely old PCI WAN card (10 years old) for a cable network and it doesn't come up as a interface.  I have drivers for it but I do not know the location on where to put the driver.  I will start another thread for this.

BSDPerimeter, including the founders of pfSense, offer this as a service. https://portal.pfsense.org/index.php/reseller-subscription. You could also tackle this yourself but if you plan on re-selling pfSense it will be much quicker to have them do it. http://devwiki.pfsense.org/ReBrandingSupport Steve

Tnx so much!! i think everything works fine!! tnx again!!

Sure, with embedded it's easy. Just use dd/physdiskwrite/something else to write the embedded image to the CF. I thought Netgate even had 2.0 images for the Hamakua with the right bits set on them to boot correctly. Check their website or e-mail their support, they're a good bunch of guys they can point you in the right direction. (Especially if you let them know you're looking to order more. :-)

http://redmine.pfsense.com What you're probably interested in is: http://redmine.pfsense.com/projects/pfsense/activity

@Perry: Yes @http://forum.pfsense.org/index.php/topic: Usually this is happening when you have nano bsd installed and you are trying to follow the boot sequence through the VGA port. In that case, you will have to attach the null modem cable and connect through the serial port. Nano bsd does not load VGA drivers. To support different sizes of CF cards as you now can upgrade and install some packages on nanobsd. doc.pfsense.org and forum search is your friend If your new to networking and pfSense the book will really help you out thanks

I don't think I have sticky connections.  Correct me if I'm wrong but I would not have that unless I have a multi-wan setup (which I do not). Thanks for the link.  I've changed my DNS to openDNS for now. As for the 6 possible causes in the article 1. How would I ensure this?  2. The LAN subnet mask is 255.255.250.0 (Status -> interfaces) in pfsense and the same on the asus router.  It is 255.255.240 on the WAN if that matters. 3. Where do I set the MTU?  Pinging with 1500 bytes was successful 4. Traceroute does not stop upstream - not applicable 5. Not applicable 6. Did this I'll post back if I continue to have problems.