Should be fixed in next snap.

After Panic Please Try to Type RESET at console.
But I think is some bug in XML.

Feature requests come under the Bounty forum, where you suggest a feature and offer the amount of money it's worth to you.

As for the VPN, it sounds like you need to make the VPN your default route, not sure how you'd do that with IPsec though.  One traditional alternative is to specify the VPN as the route for 0.0.0.0/1 and 128.0.0.0/1.

hehe ^^

One week later. Trying pfSense-2.0-ALPHA-ALPHA-2G-20090912-0741-nanobsd.img

horray! I see and can configure wireless in pfsense webinterface.
Ahhh, grateful!

Responding to this old ticket because I am also having trouble with wol.

Tested using
2.0-ALPHA-ALPHA built on Sat Aug 22 01:39:53 UTC 2009 FreeBSD 7.2-RELEASE-p3 nanobsd
and
2.0-ALPHA-ALPHA built on Sat Jul 25 23:59:13 EDT 2009 FreeBSD 7.2-RELEASE-p2 full install

I will test with a more recent snapshot as soon as I can.

Problem 1, there was a typo in the wake all section that was giving an error.
"Fatal error: Function name must be a string in /usr/local/www/services_wol.php on line 53"
I have a pending merge request to fix that, it is a little typo with a $ in front of a function name.

Problem 2, the wol command wasn't even on either of those images.  No wol command under /usr/local/bin.  Because the webgui doesn't give any feedback on the execution of the wol command, I only just realized that was the problem.  I created another patch to add some checks to services_wol.php so that the user is notified if the wol command doesn't work.

Just wanted to give others a heads up if they notice this also.
Josh

I played around with it a little and this is what I found.

Just clicking on the green arrow to disable the rules doesn't work.  You have to edit the rule, check disable, save, apply changes, edit rule, uncheck disable, save, apply changes and then the queue is applied correctly.

Interfaced don't need to be applied.  The point of the floating rules was that the interface didn't need to be selected so you can classify traffic with less work.

I think what adding a specific interface did, which disabling and enabling does also, is force the rule to be rebuilt.

My rule went from this.

pass  out  proto tcp  from any to any port = 3389  label "USER_RULE: m_Other MSRDP outbound"

to this.

pass  out  proto tcp  from any to any port = 3389  keep state  queue (qOthersHigh,qACK)  label "USER_RULE: m_Other MSRDP outbound"

Josh

and what's happend with limiter and captive portal problems??? is it fixed???  :'(

8.0 build plz…I've waited enough as a matter of "restarting the builder".

cheers,

Why should it remove the rules when a service dies?!
It is not its duty!!!!

Its harmless i have committed a fix for this.
The filter reload has actually happened, quite fast in 2.0 actually, and this message was just wrongly there if you did not have a cluster active.

Hi,

I'm not quite understand what youre really looking for but assuming youre trying to force the kernel loads that ko while booting. It's really simple, not pfsense issue, very basic FreeBSD behavior, just edit loader.conf and add a line to specify the ko which you're willing to load at boot time. If I am missing your point then forget'bout it  ;D

cheers,

I built the package there was a conflict in pfsense 2.0 that tries to use a TFTP proxy. I need to get a pfsense 2.0 system up again to test to make sure the problem is fixed.