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.

Per the transparent firewall doc, and per my set up, I do not have block private networks enabled.
I've reverted my pfSense ips from the same subnet as my private internal network behind ISA. here's the current traffic path, I'm assuming this may be more of an ISA issue and I'll have to look elsewhere =/

[]Cablemodem–-------->[10.0.0.1pfsenseWAN]=[10.0.0.2pfsenseLAN]–-------->[64.176.xxx.xxx public ip ISA]=[10.0.1.1]–------->internal network (10.0.1.0/24 subnet)

I guess my question would be, how can I configure pfSense to route it's own internet access directly out, rather then having to go into ISA, and back out... ie

Current default gateway on pfSense WAN is 10.0.1.1 the internal adapter/address on my ISA server, so traffic has to go into ISA, be routed back out thru ISA for pfSense to get internet, aswell as the DNS servers (per the doc) are my internal DNS servers, thus it tries to go into my network thru ISA and back out to pfSense.

I've tried setting up the default gateway to my public IPs gateway I get on the public address of my ISA box, same with the DNS servers, but of course it fails as the adapters are IPed with a 10.0.0.0/24 subnet.

Again, I'm pretty new to routing and the like, so maybe what I'm wanting to do isn't possible how I'm trying to do it, just basically get pfSense to have internet access with out having to go into my private network, then back out.

@gbosco:

mpd version 3.18

is this version containing the patch available on m0n0 1.3b2, regarding TCP MSS clamping?

from m0n0 1.3b2 changelog:

"…back-ported MSS clamping fix from MPD 4.0b5 to MPD 3.18 (fixes MTU problems with PPPoE client)"

/gbosco

No it doesn't as it's not needed.  We run PF, not IPF which the patch was required for IIRC.