Confirmed on May 9 snapshot. PBR is working again. Thanks.

Tested this on the ALIX instead of VMWare… and it works.

Seems it's something to do with the Virtual USB device of VMWare Server...

Floating rules are rules which can apply on any interface in any direction.

They are useful in part because they do allow you to specify the behavior of traffic leaving pfSense itself, such as load balancing and traffic shaping.

You should be able to use a floating rule to accomplish the DNS routing you want.

Okay. Now the wizard went through. But I needed to lower the p2pcatchall %…
I had put in 90% of the bandwidth and got the reported error. If I choose 20% everything seems to get generated...

Weird...

@adx442:

Just to chime in with my anecdotal evidence, I had the same problem with my Alix 2D3 board using a January snapshot, where it would crash within 8 hours to 1 day, and reverted to 1.2.3.  I'm now using the 2GB May 2nd snapshot for NanoBSD, and it's been stable on my hardware for about 3 days.

I had problems also with January (and February and March and April) snapshots, but the disable hardware checksum offload trick worked for me (now using May 3rd).

Thank you, I just tried this and really, it makes it ALOT easier to follow when you're playing with slices!

Actually, I seem to have fixed it by specifying ICMP as the protocol in the rule, and then switching back to "any".

It now seems to also take ICMP packets and put them in the right queue.

@ermal:

I think that maybe the way is as you say, but I had my doubts. I tried putting in the ACK/Queue rule the same queue for both rules, but the configuration complained with a "ACK queue must not be the same that the queue configured" error.

So, when I want that the ACKs goes to a queue that it's already shaped, simply I don't put an ACK queue specification in the rule.

@danswartz:

That is exactly what I want.

Thanks both of you, guys.

@jimp:

before doing anything else, recreate that crash and then type "bt" at the debugger prompt. That will get a backtrace which will help track the problem down.

After updating to the latest build I needed to rebuild my default gateway interface names in the firewall rules etc.  After doing this I do not have had the FTP crash.
Updating to latest build and updating configs helped

@cdx304:

I have had no problems with the latest  build .The only thing i would like to see is nat ability in Pfsense since were are using a large case's  it would be nice to have a storage drive in pfsense like a 1 or 2TB drive .

pfSense is a firewall and should be treated as that! It is kinda insecure to put your valuable data right into your firewall!

Well you can enable static ARP.
Essentially you have a static ARP-table.
If the client has a different IP than in the table he wont be able to communicate with the pfSense (though with every other client in it's broadcast domain)

Use the gateway group on a Firewall->Rule.

You cannot use SSL port without configuring certificates and what not which is not that easy.
Just use standard port.

Go to gateways and put that in the monitor ip.
In 2.0 that setting is not use anymore and you can control from GUI the monitorip.

I would go ahead and do some speed testing from the 2 groups and see what happens.  Trial and Error baby!

thanks for the info will update and get this sorted.

The problem still persist with the newest 05/04/10 build. I had to delete the rrd files again, after an upgrade from 1.2.3…