Yeah that navigation deal is sort of a known issue. I thought there was already a ticket for that, though it was for the Cron package (Cron, Backup, and Shellcmd were all written by the same guy). If you open a ticket make sure it's under the "packages" area (http://redmine.pfsense.org/projects/pfsense-packages) since that is am issue with the individual packages' code and not an issue in the base system.

I'll have a look at the boot log more in depth later, but a quick scan of it looked OK.

Problem solved…
change cpu core in bios from all core to dual core and restart everything go fine.

If it was an early beta4 that is expected. You just need to edit/save gateways and they're OK again. That was quite a while ago though.

Hey Jim,

Got everything to work with 2.0 beta!  Now I'm looking to install Kismet or something similar.  It would be nice to have that as part of the 2.0 build.

@Jonb:

I have noticed on build 28/12/10 that if you install squid then remove it the deletion process removed files required for the racoon to work.

Hi !

Yes, issue is identified, I had exactly the same problem: http://redmine.pfsense.org/issues/875

Regards,
Pierre

@j_f:

When is the estimated time for snort-inline to be included in the pfsense2 beta?

inline won't be included in 2.0.

The only change between those two revisions was the addition of a cron job, nothing that should have touched the certs.

I got around this by removing the &id=0 from the URL.

Well I don't know if the redirect statement on the PPTP tab should enable some kind of hidden rule. But of course you need GRE (IP 47) and 1723tcp forwarded to your server. You could check if there are any rules by having a look at /tmp/rules.debug while you deactivate your forwards. Just input a redirect server under PPTP and click save and look at the rules file…

Done. Its the following bug report:

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

You need to modify the source for this.
It is not present for the moment to do such things.

Yes, also tried with my DynDNS name…

Please provide the system log.

Not sure it's that big of a deal, and the deamon that collects the info (apinger) may be replaced anyway in 2.1.

thanks for replay. When try latest iso i386 12 jan 2011,after setting up voucher thru captiveportal, I restore my currently used voucher thru Diagnostic,Backup/Restores .i reboot my firewall,But ,when I view Status:Captive Portal:Voucher, empty(zero) at Active and used voucher,THEY LIKE NEW GENERATE VOUCHER.

@BuLLeT:

I don't have much time today to work on that, but i will look forward if the team of pfsense does not correct the error first

I am experiencing the same problem with squid3 since the early betas of pfsense 2.0

The simplest solution I found is to comment out the line
reply_body_max_size
in /usr/local/pkg/squid.inc

it's required to do so after each update of firmware only, not after each restart of service or server