OpenVPN does a keep-alive on its own, IPsec does keep-alive if you fill in an IP of the remote LAN in the keep-alive box on the tunnel config.

If you're bridging 2 interfaces then you must use the same IP range on all interfaces. Can you clarify what you're pinging from where?

Just about all CF cards created in the last few years have wear leveling.  You'll be fine with that card and the 4GB NanoBSD image.

Using beta 2. Dosen't seem to have the problem…  yet :)

@XIII: I thought that was on the roadmap? is it just that it has not yet been implemented? Per-page permissions are there, but not "read only users" that can look but not touch. There's no code around for that that I'm aware of.

pfSense isn't linux, its FreeBSD.  OSX isn't linux either.  Its based, loosely, around the FreeBSD core.

well actually i got it from you wagonza. i searched for missing gateway and came across that

Also, what sshclient are you using ? I have noticed trouble with some clients sending unwanted characters when working on older unix-systems.

@jimp: Have you rebooted since that change? Some processes will only pick up a TZ change after a reboot. Hmm.  Probably not.  I'll give that a shot.

Hi and thanks for the feedback. @eirikz: What version of Vmware is this ? ESX ? Server ? Workstation ? I'm using the vmware player. @eirikz: Also, you are on a totally different subnet, so no wonder you cannot reach the pfsense.. I'm aware of that. I was expecting that windows would take care of the network addresses in this virtual lan. Even so, I tried setting up the lan address in both subnets (192.168.30.2 and 192.168.229.2) without success. Do you have any check list or troubleshooting guide for this kind of issues? thanks again for the help

If these are internal interfaces, they do not require and should not even have gateways set. Items inside those subnets should use pfSense as their gateway, and pfSense will use its routing table to forward them on, which if 1.2.3.4 is the gateway to your upstream, it will all route properly.

I think I might have answered by own question; http://forum.pfsense.org/index.php/topic,26759.0.html

I was completely wrong on the subnet masks. My subnet mask for my WAN interface was incorrect. Thanks for the prompt help and the link. It's working perfectly now.

Running "top" to see what process(es) are tying up the CPU would be a prudent first step in troubleshooting this.

I didn't. I guess it's the Netopia 4541 router on the WAN end which bring this. There is no option in the menus to act on this.

@jasonlitka: 2.1 only has 4 open tickets.  We should see it by the end of January, right?   :) Add in all the "future" ones :-)

Has no one an idea?

Please start new threads for new issues. This is the second post of yours which I had to split into a new topic due to unrelated content.