Not yet:

Beginning package installation for mailscanner...
Downloading package configuration file... done.
Saving updated package information... done.
Downloading mailscanner and its dependencies...
Checking for package installation...
 Downloading http://e-sac.siteseguro.ws/pfsense/8/All/MailScanner-4.84.5_3.tbz ...  could not download from there or http://ftp2.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.1-release/All/MailScanner-4.84.5_3.tbz.
of MailScanner-4.84.5_3 failed!

Installation aborted.Backing up libraries...
Removing package...
Starting package deletion for MailScanner-4.84.5_3...done.
Skipping package deletion for perl-5.12.4_3 because it is a dependency.
Starting package deletion for pyzor-0.5.0_2...done.
Starting package deletion for p5-Mail-SPF-2.007...done.
Starting package deletion for p5-IP-Country-2.27...done.
Removing mailscanner components...
Tabs items... done.
Menu items... done.
Services... done.
Loading package instructions...
Include file mailscanner.inc could not be found for inclusion.
Deinstall commands...
Not executing custom deinstall hook because an include is missing.
Removing package instructions...done.
Auxiliary files... done.
Package XML... done.
Configuration... done.
Cleaning up... Failed to install package.

Installation halted.

at last getting some hits.

I don't even know how to see squid logs, except than going to diagnostics, edit file, /var/squid/logs/cache.log but i don't see any miss/hit statistics there.

anyways as soon as i disabled dynamic caching the "LAN out" number is growing faster than "WAN in" in interface statistics.

So at last my squid cache is working.

Maybe i got confused because the previous squid 3.3.4 release was not caching for some reason even when dynamic content caching was off.

Thanks marcelloc

Rich,

Your widescreen update does work in v2.1, sorry no screen shots (yet!), unfortunately the "all.css" file that is included in the zip file appears to be old and misses some later updates.

The dashboard (index.php) has an issue with the HTML DIV statements, it's giving an error message.  I'm not at home at present and will try and find the culprit, but may be something to do with the closing DIV statement before column 1 ("col1").

Definitely a thumbs up from me (and probably lots from Supermule ).

 
Upgraded to RC0 last night.  And all seemed fine.  Today though the web interface is extremely slow.  Say about 5 minutes to prompt for user credentials.
 
This warning was displayed at top of browser window.
 
Warning: session_start(): open(/var/tmp//sess_97c0b0e10ddfe1c34e6390f2a65e16ac, O_RDWR) failed: Input/output error (5) in /etc/inc/auth.inc on line 1320
 
Seems to be routing traffic fine though.
 

Samsung has a new batch Enterprise ready drives for folks that have systems that are going to really beat on it, 3.4 PB of writes.

http://www.theregister.co.uk/2013/05/23/samsung_s843t_upgrade/

I'm really partial to the Samsung drives, not for any hard reason but because I like the idea that they make their own memory chips and controllers and don't rely on outside vendors for them.

Jimp,  2.2... Waaahhh! I haven't even started whining "are we there yet" over 2.1 and now I'm waiting on 2.2.   :-)

Try again please.

I did not had time to revise all compile options to move it to official repo.

arkadaşlar ilginizi çeker mi bilmiyorum ama;

benim de üzerinde çalıştığım ama kısa zaman önce ara vermek zorunda kaldığım bir fikrim vardı.

Daloradius diye bir proje var. bunu pfsense 'ye freeradius ile birlikte dahil etmek mümkün oluyor. Dolayısı ile freeradius 'u etkin ve amacına uygun bir şekilde kullanmak mümkün oluyor.

Yakın zamanda bunu tamamlamayı düşünüyorum.

saygılar,

There were a couple instances of the manifest file on servers that I didn't get to update earlier, they should be OK now.

The drop-down menus should be showing an RC choice for everyone now, no matter which mirror gets hit.

I have OpenBGP package installed, and it was running fine with pfSense 2.0.1 and 2.0.2.  Unfortunately after installing the 2.0.3 update the bgpd will not start.

I have tried to find information in the logs, but not really sure where to look, or what to look for.

Any assistance on how to resolve this problem would be much appreciated.

• The unit did not boot the original OS. It has no way of telling what it's doing either. Most appliances have a integrated small speaker or a LCD. It could potentially be a DOA, but i have no clue if it works or not.

More info: http://www.gondolin.se/blog.html#stm150

For me it sounds like the device was broken before you got it. If the manufacturer fixes your device, please try again with pfSense and inform us about the result.