Thank you Sai and GruensFroeschli, Your support has been much appreciated. This thread can be closed.

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

This is how i look for packages http://portsmon.freebsd.org/portoverview.py?category=&portname=redir&wildcard=

@Juve: I'm currently using a simple bash script calling wget with some POST parameters (auth + backup page parameters). working well since november 2005.  ;) I finally have time to get this integrated into my RANCID backup environment and was looking to do JUST that.  Rather than recreating the wheel, could you post your code to do what you're doing?  It'll save me time and likely a headache. nb

@killgannon: … i cant even ping opt1 from anything on opt1.... Are you sure you got the alias definition for 'Wireless net' right? You use it for the access rule on the wireless tab. If you can't even ping OPT1 from within OPT1 then the traffic gets blocked at the interface for some reason. Try to find out why.

@GruensFroeschli: http://forum.pfsense.org/index.php?action=search http://forum.pfsense.org/index.php/topic,7057.0.html Sorry about that! I did a search of the forum yesterday and never saw this one… thanks!

Also diagnostics/states or status/system logs/firewall

LOL, from the makers of MRTG, I should have remembered that one…!! Thanks! :D

Format the stick and only use it to store the config booting from the livecd. This is option 98, not 99.

Things regarding virtual IPs are often not working due to arpcache issues of the devices in front of you. Try to reboot the device in front of you or take down the line for some minutes to make the arp caches expire.

it's not vro but vr0 (this is the number zero, not the letter "o").

Upgrade to 1.2 release or maybe even reinstall. RC4 is outdated.

I found that the developer version is 1.2-BETA-1.iso.gz. Is it this one that I should use? Thank you.

The administrator of ma.cx have disabled ezard.ma.cx for now. [1] Advanced Options [2]State Type You can use these to help guard against DOS attacks Yeah, it looks like that would help… but it could be a bit cumbersome if you were trying to make a firewall more resistant to attacks on all ports and destinations. I'd have to think about a good way to handle some sort of global settings. What I did find helpful was increasing the number of states the firewall could track. I bumped it up from 10k to 40k and then 64k. The higher the setting, the more responsive the firewall itself remained while under attack and with the state tracking table full. I was watching memory consumping (the ALIX box has 256MB total) and total free memory didn't seem to change much even when tracking 64k connection. In the past I've seen reports of anywhere from 3k to 1k of memory used by each connection tracked. Anyone know if these are still correct?

LAGG isn't supported under pfSense 1.2, regardless of the version of the underlying FreeBSD.  If you try to make this work, you are on your own.

Ok it will log the extended information, but when I deselect that option it leaves the firewall log empty. I tried /etc/rc.d/syslogd stop / start No effect.