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.

I have the same Optional interface ping problem… http://forum.pfsense.org/index.php/topic,9834.0.html

http://ex-parrot.com/~pdw/iftop/ Iftop is nice ..  real time traffic monitoring/graphing. I installed it on pfsense 1.2 by downloading the binary package for iftop from a freebsd 6.2 mirror somewhere [image: iftop_normal.png] its not a gui app though, have to use it from ssh or console

@cmb: That's actually exactly what I was talking about in our dev IRC channel yesterday. Its logging sucks, its functionality is weird, it just seems to be a general PITA. I'm strongly considering replacing it with FreeBSD's stock ntpd (which I believe is ISC's). It is, and I for one would be grateful if that happened.  I'm too used to being able to set iburst and know that within a couple of minutes of booting up my clock will be synced.

Sweet, Dynamic dns works. Thank you all for your input. Regards, Fred

And does the radius-function work? ??? And does anyone knows a manual in cooperation with microsoft 2003 server? Thnx,

It doesn't get all the blog posts, just release announcements and anything else major. I don't believe it's archived anywhere. If you want email notification of blog posts, this looks like it should do just that: http://www.rssfwd.com/

I had the bridging well done because i could get an ip with my laptop,but pfsense took ages to get an ip and only today i manage to do it.

@GREG3f: Is 1.3 available now?  If not, is there an ETA? It'll be available for testing purposes in a month or less, but won't be a final, stable release until 2009. Though a lot of our users have been running beta versions since the very early days. Once it hits beta, we will be willing to provide commercial support on it with the caveat it may not be as stable as 1.2 yet. No clue and not going to guess when it might hit beta.

Thanks for the reply sai, will there be anything special I will have to do for setup on the pfsense box?

Because you don't control the actual endpoint connecting you to the Internet, you can't effectively traffic shape. After re-reading my post I realized that I misspoke.  The dsl gateway is in the comm room and I do have access to it.  Would prefer to have the pfSense server in my office but if I can't have it here, I can put it in the actual comm room.  I have full control to the end point, the server location was just a preference.  The gateway, on the other hand, can not be moved from the comm room. Is it possible to shape traffic when the gateway provides the switch & wireless?  I guess the problem is, it would look something like this: Scenario 1: Internet > Gateway > pfSense When it should probably look something like this: Scenario 2: Internet > dslModem > pfsense > switch & wireless access point Is the first scenario possible, or is only the second going to cut it?  If only the second will cut it, I think we can use the gateway as a dsl modem by turning off the wireless.

Summary (as you seemed to have missed the point): your firewall/proxy server should run as few services as possible.  The more it does, the more likely it is to have vulnerabilities that can be exploited, rendering it as effective as a chocolate teapot.

heres the screenshot for my print server [image: hpprintserver.jpg] [image: hpprintserver.jpg_thumb]

From what I see on my dd-wrt there should be nothing stopping you. Just disable the WAN connection and DHCP server then it just becomes a normal access point. [image: ddwrt.jpg] [image: ddwrt.jpg_thumb]

endly found this : http://forum.pfsense.org/index.php/topic,372.msg2274.html#msg2274 I think I can deduce that "affinity" is by default enabled in 1.2-release ? However, I'm still waiting for some confirmations, plus I don't really understand what is, in this context the "sticky" option. Is this the "affinity" (english is not my mothertongue sorry) ?

It's under the individual interface tabs, and it is checked by default. Thanks very much, this fixed the problem nicely.  I don't understand how I could ping the modem with this checked though? Anyway, it's working now.  Installing Squid as we speak, and I'll go from there.  Thanks for the help, I really appreciate it!

A wild guess is that you need http://doc.pfsense.org/index.php/Static_Port else "system logs", "states" and "Packet Capture" could help you finding out whats wrong.

right now pfsense is setup that it does have a public ip quick question does the block private address feature block  128.210.0.0 subnet?