There will be no way to boot CD …. no CD drive .... or usb boot option ... all locked in BIOS. Only way is to get the HDD out ... and then noticeable downtime of the box. But you are right. I will think about grub for some time, but probably leave it in this way.

You're correct, there is no authentication system for authenticating WAN side connections in pfSense.

You are damn right.I can't speak english very well. :'( Thanks

you can still try V2.0 but as we all are stating 2.0 isn't ready for true production environments BUT its can be used but we STRONGLY suggest using 1.2.x, if your ok with taking it into a production environment and testing it and are willing to accept that there may be bugs and potential down time and want to use 2.0 we won't stp you, we just are trying to let you know if you do use 2.0 in a production environment just be ready for things to break and down time to happen with it. now if your looking for an actual firewall appliance perhaps something called endian may fit your needs, but again thats the same basic situation, if you are using a custom machine you run the risk of incompatibilities being there…and the actual appliance will run you from about $150+ depending on what you need...if you need other options there might be other linux based firewalls out there you might be able to try.

you have Snort enabled with blocking?

@dordal: Would folks be interested in a bounty? That is what it'll take. Three people currently make a full time living on the project, plus a handful who make part of their living on it, and those people do the bulk of the development and testing work. We're hoping to pull together enough that we can spend a considerable amount of time on it, after 2.0 is released. For the time being it's not something that can be even considered as we are fully dedicated to finishing 2.0. But when it gets to that point, we'll definitely be seeking contributions to cover the implementation. I'll post to this thread, the blog and mailing lists with info when we get to that point. thanks!

I could if you tell me how :P It's been working for a while though, so you'd probably find a lot of other stuff in there as well.

The message suggests to me that the Alix is trying to boot over a network interface (PXE boot) but that is failing because the interface is not connected to anything useful. I don't know enough about Alix systems to guess whether this can be eliminated by a BIOS configuration change. The DISK BOOT FAILURE INSERT SYSTEM DISK AND PRESS ENTER. message suggests the BIOS is either not seeing the CF or it can't find a bootable partition on it.

@trunglam: Any solution to solved this trouble? I'm locking this thread because it's been getting hijacked for 2 years, and the initial problem was determined to be an ISP issue (which is almost always the cause of such problems). If you have a performance problem, start a new thread and post details (not just "it's slow").

Ongoing incessant NTP updates and gateway pings. Stopping the ntpd service (status|services) prevents the incessant NTP updates but how to fix? Need your help here. Thanks

Try using 1.2.2 -stable version of pfsense? How many users have you in your network?

Can you probe external dns servers in your pfsense box and do save aply to discard problems with  your internal dns server? when you do save aply you loose web navegation like www.google.com but you lose too navegation like 200.200.200.200?

Yup, looks like that was the issue, somehow the subnet mask had been set to /5.

pfSense 2.0 uses ipsec-tools 0.8[1] (which isn't even an official release yet) which includes racoon. What racoon2 are you referring to? [1] Mar 27 09:06:37 racoon: INFO: @(#)ipsec-tools 0.8-alpha20090903 (http://ipsec-tools.sourceforge.net) Mar 27 09:06:37 racoon: INFO: @(#)This product linked OpenSSL 0.9.8k 25 Mar 2009 (http://www.openssl.org/)

What you describe has a few dozen threads on the DynDNS forum.  While you can sign in to the web site with your email address or username, any update client must use the account name, not the associated email address.  Glad you got it sorted.

HGi Jimp, Jup that is what I ended up doing. I just let the modem login with PPPoE and then let pfSense handle the rest. It is just a shame the way AT&T does this. Why they have to be so difficult? Anywaz, thank you all for your inputs. It really helped me.

Sorry like my server is my physical Windows 2003 box which I just use to run Microsoft CRM 3.0.  I have vmware server installed on that, and I run pfsense through vmware versus having separate hardware just for that.  So just confused how my physical windows server 2003 gets a 10.0.0.50 IP when vmware is using both my physical nics?

Unfortunately that's pretty vague in terms of a problem description. I am using PPPoE on a number of 1.2.3-RELEASE routers in the field and they all work fine. Can you check the system log under Status > System Logs and post the contents here? It should have log entries from mpd, which is the program that handles making PPPoE connections.