Thanks!
If you want to send me a PM or repost here after any changes are made to this i would be happy to test it for you!

-E

@cmb:

That's the problem, the new IPsec doesn't put the source IP in there and hence it isn't used. Will report to the author of the new IPsec code.

UPDATE !!!

Seems this is fixed in the current SNAPSHOT.  I re-installed from ISO and reapplied backed up config and all is well.

This is the problem with the "RBA" (roles based access) as I've experienced too.  When you setup users/groups and take away the "ALL" then they cannot access the "index.php" and the post login always throws an error saying "user /you do not have access to the index.php".

Essentially, it's as follows:

Create manual outbound NAT rules from each private network to each public network, respectively

Add load balancer pools for each multi-WAN variation you want. In my case, I have one where both are round-robin, another where WAN1 fails to WAN2, and a 3rd where WAN2 fails to WAN1

Add outbound firewall rules for your local segment(s), choosing the appropriate gateway to be sent out (e.g. Round Robin, WAN1->WAN2, or WAN2->WAN1).

If that's not quite specific enough, have a look at the multi-WAN wiki entry: http://doc.pfsense.org/index.php/MultiWanVersion1.2

I did specify a number of schedules, but at this time no rule is actually using a schedule.

I don't have active portal activated yet.

The build is from yesterday evening:

1.3-ALPHA-ALPHA
built on Mon Oct 20 17:56:29 EDT 2008

Hello,

Are you willing to communicate between LAN/LAN_OUT? Can you provide here a simple diagram showing which is which, ping to/from, where PC(s) located…etc for us to understand clearly?

cheers,

Hi,

No new snaps since 20-Oct-2008 18:24, when can I expect new snap which your commits included?

@ermal:

slightly different fix commited.
thanks.

cheers,

Hello,

Just checking…it seems to be the same with the full. I don't use https for LAN access though... ;D

cheers,

Hi

Finally up-to-date with the latest. All issues reported here in this thread seems to be addressed and looks good for now :D I will keep my eyes on my box for a couple of more days or so.

Thanks ermal for your dedication!

cheers,

It always used to sync on user-defined name, not interface name, and that's the way it should still be. Otherwise you could never have two boxes with different physical interfaces, and that works fine. This sounds like a regression, ticket created. http://cvstrac.pfsense.org/tktview?tn=1823

Search the forum. This has been discussed multiple times.

Also:
http://doc.pfsense.org/index.php/When_Will_A_Release_Occur

I've seen this warning a on pfSense 1.2.1 enough to wonder if it is always there. I've not seen any problems associated with it.
Test the firewall and if it you find problems then consider reinstall otherwise I wouldn't be too concerned about it.

Same Here

its fixed.