A (very very) quick test seems to indicate the patch fixed the corrupted .cap files. I'll hammer on it some more and see if I can manage to get it to misbehave again. ;)

@David Szpunar
To add something to you comment:

Just create two aliases:
One Alias with all the pfsense interfaces IPs (if you have different VLANs) and the one alias for the ports (like 22, 80, 443) for accessing pfsense webGUI.

The you only have to create one block rule on top with destination IPs-Alias and Destination Ports-Alias. Thats all.

i don't suspect the wireless hardware; i suspect the config being written to it is wrong. i guess i need to modify the scripts to log what config is actually set to confirm that.

The DHCP daemon itself only keeps one large leases file, it doesn't split them up. While it would be possible to do this it would increase the complexity of the page quite a bit. At this point it would be too much to make it into 2.0. You could open a feature request ticket at http://redmine.pfsense.org/ with a target of 'future' and perhaps for 2.1 or later a developer or volunteer might take that on.

Yes, I've got your method working.
You also have to turn off "Allow DNS server list to be overridden by DHCP/PPP on WAN" in order for it to work.

Disabling the configuration sync won't disable CARP failover.

Server-bridge only makes sense for bridging clients and giving them IPs.

That is what I want, get a IP address of the LAN with my openvpn connection.

Thanks ermal, limiters work as you said

i've added this floating rule on the vpn-server end:

dir: in
dest: 10.10.10.0/24  (subnet of client-lan)
in/out: limit_in / limit_out

pfsense is great ;)

@root2020:

This is the same results that I was having when I pushed the "system logs button", on a previous build. What did you do to cause it to lock up?

http://forum.pfsense.org/index.php/topic,37712.0.html

I was viewing the traffic graph when it crashed. I did notice that it was not displaying the host ip or bandwidth in / out info either. Also the Dynamic DNS ip was not showing green as it should. After going back to the build 2.0_RC3 June 21 all seems to be working.

vmxnet drivers are in the open vm tools package.

e1000 works just as well as the e1000e for most environments.

Hello!

I had the same problem this week.
It´s not PfSense fault.

Virtualbox has made changes in v4.0.6
Check this link out, you have to set promiscuos mode for the PfSense internal nics.
http://forums.virtualbox.org/viewtopic.php?f=7&t=41036#p184544

This is what I did for my LAN and OPT interface. My 3 nics are Intel E1000 nics.
Command:
(VBoxManage setextradata [VM_NAME] "VBoxInternal/Devices/[e1000/pcnet]]/[slot]/LUN#0/Config/IfPolicyPromisc" "allow-all")
For ex:
VBoxManage setextradata VM_namehere "VBoxInternal/Devices/e1000/1/LUN#0/Config/IfPolicyPromisc" "allow-all"
VBoxManage setextradata VM_namehere "VBoxInternal/Devices/e1000/2/LUN#0/Config/IfPolicyPromisc" "allow-all"

Then it worked for me.

/illern

The only way to be sure, that there is no connection/communication between different VLANs is this:
@wallabybob:

I assume those rules posted are PASS rules rather than BLOCK rules.

Firewall rules are processed top down, terminating on first match.

On VoIP interface, to allow access to the internet and block access to LAN subnet AND Video subnet you could use a ruleset like the following:

ID  Proto    Source  Port  Destination  Port  Gateway  Queue  Schedule  Description 
BLOCK    TCP/UDP    VOIP net    *    VIDEO net      *        *        none            Block VoIPnet to Videonet
BLOCK    TCP/UDP    VOIP net    *    LANnet        *        *        none            Block  VoIPnet to LAN net       
ALLOW    TCP/UDP    VOIP net    *    *              *        *        none            Allow VoIP to everywhere else

or this one:

@GruensFroeschli:

An even easier solution would be to use aliases.

Create an alias containing all your local subnets.
Assuming that all your local subnets are RFC1918:

Alias: rfc1918_nets
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16

Now create a single allow rule with as destination NOT the rfc1918_net alias.

ID  Proto    Source  Port  Destination    Port  Gateway  Queue  Schedule  Description 
ALLOW    TCP/UDP    VOIP net    *    !rfc1918_nets    *        *        none            Allow all destinations except local ones.

@cmb:

Loss to your gateway very rarely has anything to do with the firewall, usually ISP issues, or modem issue, or something of that nature (especially if it pops up out of nowhere on a system that was previously working, regardless of upgrading it as nothing that impacts that has changed in a long time).

I am sure that the problem is ADSL modern. Actually I just get a new one from my ISP and everything works well in the past several well.

In another topic I mentioned about PPPoE disconnect is also solved….

Thanks for all of you~

Found a discussion about this very subject here:

http://forums.openvpn.net/topic7168.html

if im not wrong, you cant use 2 wan`s with same GW, i think you must use 1 WAN ( with 1 public IP ) + a VIP ( the other public IP ) and do 1:1 NAT for the second public IP

OK, sorry…
Back to http://forum.pfsense.org/index.php/topic,38093.0.html then…

Thank you sir :-)  I do believe I may write a basic Multi-Wan online how-to after all of this :-)

I've been following along the setup guides which are "stuck" at the top of this forum…but already several gotchas:

a.  The load balancing thread makes the process much more complicated...all you need is one rule!
b.   Pass thru VPN does not work unless you turn on sticky connections.
c.   Floating rules have no mention in the multi-wan setup... I found this which is a bit misleading: http://forum.pfsense.org/index.php/topic,28121.0.html
d.  Context help is not there for packages generally in in RC3

I will search up the multi-wan, squid and floating rules and play some more tonight.  Given that (based on the above) I'm likely to encounter incorrect information...is there a thread link that you know is correct for squid on psSense2, multiwan, with floating rules?

When done all of this, I will edit my thread over at small net builder..and replicate in the form of a user guide here :-)