Looks like the field name is desc and not descr, so it isn't getting the same protection against that as the other description fields. Shouldn't be too hard to fix. EDIT: I reopened the original ticket for this and added the details of what is going on here: http://redmine.pfsense.org/issues/320

dual wan, both are set dhcp, have tried wan as static still doesn't allow change as static and doesn't all for weight of connection to be changed either tried going back to a snapshot from 9-13 still didn't help .

Hi, Can I setup WAN1, WAN2, WAN3 with all PPPoE  and work well?? Now I only connected one WAN (PPPoE) is OK but enable both not OK that just one connected at the same time build i386 Thanks

Actually, there is no way to assign the _wlan0 version at the moment.  Assigning the parent currently implies assigning the _wlan0 interface for it.

@jimp: That looks good too. If you go to Diagnostics > States and filter on the IP trying to ssh while you do it, what shows up? When i try to connect to the server (noc.it2go.eu port 10022), i get an error "can't connect etc" in putty. But when i connect to 10.0.0.10 port 22, everything goes well Problem doesn't seem to be pfsense…

Rules are crafted from the perspective of the router itself. Imagine yourself sitting inside the router. Traffic coming from the LAN is coming "in" toward you (i.e. LAN users uploading) and traffic going "out" to LAN (i.e. LAN users downloading) is going away from you.

From what I have heard, there is some dark magic involved with disk cache layout; A lot of things affect performance: Too much in the cache, too little in the cache, underlying filesystem layout, file system size, filesystem type, disk hardware, disk placement (front of the disk vs end of the disk), other items on the same disk controller, other general hardware items, etc, etc. I'm not sure any one choice would be better for everybody long-term, but ufs may be the best place to start.

Same probleme with 2.0-BETA4  (i386) built on Wed Sep 22 22:49:23 EDT 2010 FreeBSD 8.1-RELEASE-p1 Not a 64 bit issue only, it's a LAGG type issue. The probleme seem occur with a "fec" LAAG not with a lacp "LAGG" fec: Supports Cisco EtherChannel. This is a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the link. Thank in advance.

Upgrading to the latest nightly fixed it. I think one of the packages broke a shared libary

Thanks :)

Im using Dell Poweredge R300 and they work fine, install from internal DVD drive fine. You can't use 1.2.3 on these due to to the Intel PCIe network card does not have drivers in 1.2.3. The base features in 2.0 seem to work fine. I've had to restart twice due to firewall rules changes stop taking effect. Most of the packages seem to not work right or have issues, so I think as long as the base pfsense w/o extra packages works for you then you will be fine using 2.0 beta. Squid do not work right (transparent proxy broken, at least) and on the other machine its stuck with the packages removed but webui thinks they are still installed.

If I correctly got the underlines, Stigma is a home user like me. If so, I'd ask you to give some updates as to your current experience in combining Pfsense with virtualization, either from the architectural and security standpoints. I'm a newbie home user who is trying to get rid of poor hardware routing apps, but I'm still pretty much afraid that virtualization could present a threat in terms of security. Thanks

No, it's trying to -HUP cron if it's already running, which at that point it isn't. Look later in the boot log, cron is actually started farther down. I'm committing a fix to suppress that error you're seeing.

I just committed a fix. It should be in newer snapshots, or you can either gitsync or apply the patch from the repo manually: https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/7b2fdac49b28d638a38c9f51a7222e25d386bcca

Then maybe you should use an other firewall? (Or open a bounty to get this feature added :D )