No plans, not likely.

great then It's time to goto sleep cy all later

changes here: http://doc.pfsense.org/index.php/2.0_New_Features_and_Changes For most people's usage there is no difference. If you rely on certain packages that the maintainer hasn't kept up to date for those we don't maintain ourselves, they may not work. Other than that, 2.0 is better than 1.2.3 in every regard at this point, has considerably fewer bugs (though those outstanding in both versions are highly unusual to encounter). The only other thing you can encounter on occasion is hardware-specific regressions between FreeBSD 7.2 and 8.1, though those are rare and we've back ported newer drivers in some instances to resolve.

I believe that only people matching the spammer database in use (either by username, e-mail, or IP) get stuck in the queue for approval. If someone doesn't match at all, I thought they went right through. Looking through the list of people in the queue waiting for approval, they all have at least one field flagged for spamming.

Hi Steve.. So they are only talking about squid itself not transparent config.. I hope your great developers surpass this issue  ;D

thanks steve  ;D

Thank you very much…

Ah, That's got it!  ;D Steve

Because i'm not currently having a working box so i can't check but is havp something what you're missing

Yes 6GB does seem quite high!  :o I guess it depends how much use/speed you want/need. Openwrt will run in 16mb or ram from 4mb flash on a 133MHz CPU. It has a x86 port though so it should fly on your thin client. There are many packages available for it and a nice gui install for them if you are running X-wrt. You can run an SMB server and have shares for each of your users or general shares. Or run NFS or many other options. It's never going to be as fast as a genuine NAS solution which needs to be as fast as possible. It sounds like you are looking for something more akin to a file server. It's not as easy as FreeNAS though see: http://wiki.openwrt.org/doc/howto/nfs.server Why not try FreeNAS 7 and see how it goes? http://wiki.freenas.org/documentation:setup_and_user_guide:hardware_requirements Steve

He actually came and said how sorry he is for his doings.. (BIG TIME VICTORY). And he also asked that could i recreate my firewall. But when the discussion went to money part he didn't mention to pay his mistakes.. So the resolution is at this point, that his workshop and our neighbours doesn't have internet but I do have. And I don't make any firewalls from my wallet.. My game might be dangerous, but it has a hidden lesson. I've already learned, now I'm waiting if father-in-law learns it

Thanks a lot nach =)

Thanks, Chris! Commented and re-locked it. Best, Martín

The wiki article here: http://doc.pfsense.org/index.php/Creating_Your_Own_Package_Repository Was written before when the repo was on rcs.pfsense.org. Over the years people have checked in all kinds of binaries into the repo, and they don't belong there. Only the PHP/xml/scripts belong in there. So when we moved to github a lot of that data that shouldn't have been in the repo was purged (lots of .tgz/.tbz files add up quickly in size!) and moved to where it should be on files.pfsense.org. As a consequence of that purge, the size has reduced quite a lot. It used to be nearly 1GB in size between the data and the history in the .git directory. It's still nearly 200MB. pfSense-packages$ du -k -d 1 88258  ./.git 110476  ./config 198970  . When developing packages, especially making new ones, having your own repo is quite handy. It's even better if you make your own fork of the packages repo on github and work with that on your server as you make changes. Then once you have it ready you can just submit a merge request there.

I don't know about bandwidthd but outbound loadbalancing has changed in 2.0. To configure it you setup a gateway group (system >> routing >> groups) and add your WANs to it. Then assign each wan a tier, all tier 1 will result in equal priority and hence load balancing. Use lower tiers if you want failover. Now edit your firewall rules to use the gateway groups as gateway. Steve Edit: Exactly which version are you running? If you are running the 'official' RC1 release, 26.02.2011, the try a much more recent snapshot. A lot has been fixed since then.

I have checked my config backup with the xmllint command and it has problems with letter ñ, I change it and I can restore the configuration from 1.2.3 to 2.0 version. Maybe that's the problems with continuous automatic reset configuration, I gonna do test to confirm that.

Nope, not us. Clearly we aren't "Proffesional" ;-)

Possibly, with the Captive Portal functionality. If you configure it to authenticate against your active directory you may be able to get it to work.

Thanks for using it. Spread the word :-)