OK - thanks!

@bplein:

So, clarification: Did all the standard cron jobs go away between Beta1 and Beta3?

No, none of the cron config entries have changed in a long time. Almost all of those are static. The filter_configure_sync one gets dynamically added or removed as needed depending on whether you're running time based rules (if you are, and that cron entry isn't there, it's added. if you aren't, and that cron entry is there, it's removed. otherwise it's left alone). The logic there looks fine after glancing over it, it's possible there are problems I'm not noticing looking through it though.

@trijames:

Checking BSDInstaller health… dfuife_curses missing [ERROR!]

####################################
Something went wrong, check errors!
####################################

Does anybody have any tips?

Build the bsdinstaller ports on your builder and re-run.

Thanks for the reply, I'll keep an eye on that ticket then.

@clarknova:

WAN:Out graph might still be reporting double traffic, but there is a ticket open for that. I will update it as necessary.

My mistake. The ticket was for the problem as stated in my original post in this thread, however I updated it to state that the WAN:out graph is incorrect, as the new issue still appeared to fit under the same bug description.

It's one of the primary boxes in my test lab, been running 2.0 on it all year. It maxes out at around 250 Mbps, 100 Mb between VLANs won't phase it, but if you're using multiple gig links with fast boxes on them that can push serious traffic, you can peg it.

Solid box, and since Netgate is offering it and they take care of us, you can be sure it'll always work with our releases or there will be documented solutions if something is a bit unusual. such as:
http://doc.pfsense.org/index.php/Full_install_on_Netgate_Hamakua

Thnx for the info :)

I'm wondering why not many people see this problem? I already started from a fresh config file with 6/22.

I've had issues with the gateway load balancing, but I haven't had time to track it down yet, so it wasn't sure if it was my configuration or a bug in the system.

I've seen in redmine that there is an issue with the link hotplug event that hasn't been resolved yet, and I thought maybe that was causing my problem.

http://redmine.pfsense.org/issues/656

All good news there. Hopefully that's the end of it :-)
/knocks on wood

Thanks!!

Yeah, I managed to get through the wizard with a newer build. It helps get the queues set up, which was the hardest thing for me in my stumblings. I've since managed to classify some traffic through a lot of trial and error. I'd like to do some documenting, as I find the built-in clues quite confusing, but I don't know that anything I write would be too useful, as I don't even know why I have to use the options I use. Anything I write at this point would be a step-by-step without any background concept.

Let's close this thread.

UPNP bypasses the filter. Doh!

I beefed this up a bit and imported it into the Doc Wiki:

http://doc.pfsense.org/index.php/Creating_Your_Own_Package_Repository

Did that and still no help.

Attached is my config file.

config-lanner_pfsense.home-20100621075403.txt

Don't feel too bad, that's a fairly common mistake. :)

I'm working on getting the auto-update system working on NanoBSD, hopefully it will be working later today, which should improve the situation for many.

Per IP, if you allow multiple simultaneous logins it will limit each, if they're coming from different IPs.

Just confirmed, still broken with my system. I wonder what is it that makes it work on some and not others…

does somebody know where i can monitor the changes regarding this problem?