hi i did change my isp really and back to the previous one  :D still one more problem bugging me here, it is squid upstream proxy not working with pfsense, and most of the isp here wants us to use it when connection becomes bad, well one day might work thanks

You missunderstand what the gateway means. It means if traffic on this interface comes in and matches the rule it will be send to the gateway. If you set * (default) it will be processes by the routingtable of pfSense. Right now you force the traffic somewhere. But inbound on the interface itself that doesnt make any sense. As a rule of thumb you can say: never edit the gateway unless you REALLY know that you want to force traffic this way. It's usually better to add static routes to the routing table and let the gateway on *.

I think if you issued that statement before, then it would make more sense as to why it is never conveyed.  Now that you said that - it makes complete sense and understandable.  I would agree - staying ahead of the competitors.

@cmb: I don't think I've ever heard of a CF writer that won't work. I've used no name generic ones and various name brands. I mostly use Sandisk 8 in 1 (older model) or 12 in 1 writers, might also be a newer one from Sandisk by now. I really like my Sandisk writers, and they don't cost much more than anything else. That's what I would recommend. Thanks cmb

Yeah, i've tried that, but as soon as the lease time goes out, i loose the connection.

thank you

I have tried changing "Firewall Optimization Options" under Advanced to "Conservative" but this has had no effect.  This idle connection dropping just started happening after upgrading to 1.2-RELEASE.  Before the upgrade we never had any issues with idle connections and we feel that enabling ssh keep alives in the client is more of a "hack".  Also, some SFTP clients some of our employees are using do not support keep alive.  This was working previously and I'm more interested in learning how to get it back to allowing idle connections how it used to be.

http://devwiki.pfsense.org/FTPTroubleShooting http://forum.pfsense.org/index.php/topic,7001.0.html

You can create limits on a per-rule basis.  When editing the rule (or creating a new rule) check out the Advanced buttons and there are a number of fine-grained options for limiting.

Not atm and afaik it's only a maybe for 1.3

When I managed to figure out what the problem was, and it's not pfsense  8) My nokia N810 uses wifi power saving which it set to maximum by default. There is a know issue with connecting to Atheros based wifi cards. Setting the power saving to intermediate solved the problem. I also have a Fonera, which has the same Atheros chipset as my wifi card in my pfsense firewall, and it too has the same problems.

If you ever find an open source project that provides reliable WAN acceleration, let us know. It's something we may be interested in implementing in the future.

@valnar: Does pfsense work with NAT-T?  That was a deal breaker for me. 1.3 will.

Did you even read the thread i posted??? I replace syslog by syslog-ng, work great. i have made a script who send the logs by e-mail, and rotate the log. the logs are stored on the pfsense hdd, and i think, they could be sent in external hdd or similar.

These days, top uses the sysctls I mentioned, so if you want to see how top uses the sysctls, you just have to read the C code. I was looking on a 6.3-RELEASE i386 machine to try to get as near as possible to pfSense. If I have missed anything from my answer or it's inaccurate, do correct it.

when you did all of this under nat did you turn off Advance outbound Nat and then set static ports to on? that is what i had to do to get linksys and cisco phones to work with my Voip

Squid is a terrible reverse proxy, varnish is a better one.  There is some interest in a package for it, but nobody's stepped up to work on one yet.  Perhaps you should consider a bounty project for a varnish package.