Try pfsense 1.2.3 - see http://blog.pfsense.org/?p=377 Note the remark about improved hardware support and the download link at the bottom of the page.

I try to start VPN, but this is not important. I lose connection when load satic route 192.168.0.0<->64.233.167.99. I want to restore connection without to preinstall PFsense if it possible from console.

@valnar: Exactly.  I can do that with any other self-created cert too though (which is what I want to avoid in the first place).  So what makes them special?  Am I missing something? No … yo're not missing something. As you thought already you have to buy a "official" SSL cert ... that will be the solution for your problem.

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

What else is happening on this box at the time?  What kind of bandwidth usage do you have going on?  How about firewall states?

ISTR that it is enabled by default and will connect to a randomly selected NTP server from pool.ntp.org.

I think you can change the listen port back to 80 from the config.xml

Thanks. I see the thread you pointed me to was back in 2007. Any idea if any advance/workaround has been found for the schedule/CP incompatibility? regards, Mark

What you want is to use the squid and squidguard package to do content filtering.  Read the packages forums.

Its already on 2.0!

Hi, is there any other way to do it ? CMD line ?

In the interest of keeping people updated who might also be experiencing this issue, I've upgraded to a beta of 1.2.3, and things seem to be working alright.  The issue appears to be an issue with PHP, as detailed in this link: http://pecl.php.net/bugs/bug.php?id=12608 I'm not enough of a guru to do a spot PHP upgrade, so I figured moving to BSD 7.1 (as 1.2.3 is moving to it) would help with the issue.  Whaddya know, it seems to be working so far.  ;D

Alright, I managed to solve the issue. My WAN was on the motherboard's builtin card (broadcomm something) and LAN was on a 3Com PCI card (marvell's chipset iirc). Anyway, I tried something random and swapped the interfaces so that WAN was on the 3Com and LAN was on the builtin and I'm no longer experiencing connectivity issues.