under status > system how many of your firewall states are full?  You may also check under states to see what they are being used on, let me know what you see there.

I see, thanks Hoba!  ;)

yeah i know and ive tried belive me. I have an dell optilex gx270 series and iwe putted 32Mb at share (the lowest) but it ignored my setting. Anyway imp. is that the problem is fixed. best regards

@hoba: Already implemented in the HEAD version (developement version of next major release). For now use hidden config.xml option (see http://faq.pfsense.com/index.php?action=artikel&cat=10&id=38&artlang=en&highlight=hidden ). Following the link from FAQ: Error: Unexpected output from cvs co: cvs checkout: cannot open /cvsroot/pfSense/conf.default/config.xml,v: Permission denied cvs checkout: could not read RCS file for pfSense/conf.default/config.xml (expected "pfSense/conf.default/config.xml" but got "")

heh, eoppoe ? :) –Bill

Use one system for everything and add a failoversystem if needed. You can setup individual DHCPs for each interface and seperate networks by firewallrules where needed.

mpd has three mtu change points link_Mtu link_mru iface_mtu all can be found in /etc/inc/vpn.inc under the pppoe function. test first with ping to see where this needs to be before you start to set it

You can edit the snort rule to detect file transfers on any port. The only problem with using snort to block file transfers is if someone initiates a file transfer, snort will block that IP from having ANY contact to your network. So basically it will cut off the file transfer and any further IM traffic to that IP for an hour.

cmb edit: removed broken link, add text from that old page Set the protocol to SFTP (allow SCP fallback). Make sure you are using username root rather than admin.

That is a good article depicting the problems of restricting Skype, Messenger, and P2P traffic.

You only can disable the console completely at system>advanced

interfaces.inc thanks, /gbosco

winscp will return an error to the caller if it fails.  Check for a failure code.  This is all possible on windows shell scripting.

modified /var/etc/mpd.conf, and set a more generous timing when MPD determines LCP echo timeout. set link keep-alive 30 300 (it was: set link keep-alive 10 60) I didn´t loose the connection for more than 24 hours now - which is a record! I would wish pfSense had a feature under PPPoE, where it is possible to set those values. Thanks to anyone who participated to this thread. /gbosco

We're finishing up the website this week.