Yes it is, you can modify a lot with it. and if you think roadwarrior setup, you can set server to work on tcp 443, so almost none can alter that traffic

Has anyone got failover working on 2.0RC3?  I have been trying to get this working for several days now and and have not been successful.

Not it is not considered today in code for this. You can do this during the prune-ing of the users where the re-authentication take place and check if there is any change and modify values. Should not be hard.

You are sure that no limit is reached on states? Also can you show if the cpu is busy doing something?

Thanks, will check with the siproxyd people.

You have to use 1:1 NAT for your servers from what i understand on your description.

@jimp: Should be OK in the next new snap. Thanks, jimp! @Nachtfalke: Strangely I noticed this with Aastra VoIP phones, which, by default, assign a host name starting with the phone's (numeric) model number…  Glad it will be sorted going forward... --td

thanks a lot for the tips! ;)

Do what Nachtfalke said, change the settings to 2000 lines, turn on logging to a syslog server and point it to the ip address of your pc, download and install syslog watcher on your pc and you're good to go.

Confirm, Snapshot - 2.0-RC3 (i386) built on Mon Aug 8 19:26:45 EDT 2011 - works fine. Tnx.

After reading this: http://nmap.org/docs/discovery.pdf The solution was to use:  nmap -sP -PS x.x.x.x/yy problem solved.

@ermal: I can not stress it enough. You can assign the bridge as anything else with the same results it is not necessary for it to be LAN! I hope that we understand each other…(and that my English isn't to bad)... Well It isn't clear to me why I had to restart pfSense at point 6. Because before system restart pfSense doesn't respond to ping and after it does. After restart I doesn't change anything. Maybe should be there checkbox or something to enable automatic restart if it is needed.

Snapshots are not and have never been signed. You need to fix your update URL, you are likely trying to hit the old update URL that no longer functions. See the sticky post in this board: http://forum.pfsense.org/index.php/topic,38687.0.html

Use a newer snapshot.

Is traffic being rejected on the perimeter or the internal firewall?

my config is also mostly basic stuff, static arp entries under dhcp and using DNS forwarder and no static DNS entries but from the last 2-3 snaps its working fine now for some reason.

Are you using SSL/TLS? For a tunnel between two sites only? Then you should be using a /30 subnet there, not /29.