@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?

I guess i was using an old version .. now Wallwatcher rocks  ;D

The gateway boxes from TUT systems do this. As do some of the commercial hotel gateways (linux based). It is kind of a nasty hack- if you plug one into an existing network, they will wreak havoc as they respond to every arp request…

@dotdash: There have been numerous threads on similar issues, they may offer some help. http://forum.pfsense.org/index.php/topic,8844.0.html http://forum.pfsense.org/index.php/topic,7030.0.html Thank you. As far as I read, It Seams to be another MS/Windows Joke (Another plus one)!

Just because 6.2 is end of life does not mean our team cannot support it.

true  or maybe an option that could say just install and notify that the updates are going to be installed on the next reboot i would think the server load would increase a little but not too much since it would just be checking to see if it needs updating…

@rgomes: I'm having trouble setting up a DMZ, I've tried everything i could think of, but there is no way I can allow (some) access from the DMZ to the lan. In despair, I even setup some rules allowing anything from any to any on both dmz and lan interfaces but still nothing. I can access the dmz machines from the lan but not the other way around… I'm losing my patience because I'm pretty sure it should be working. Any ideas? thanks Seams to be an old problem,… See This: http://forum.pfsense.org/index.php/topic,7316.0.html Regards.

You'll find other threads on this, the OpenBSD NTP server takes a long time (tens of minutes) before it syncs.  IMO it's far, far, poorer than the stock ISC version.  On the other hand, I've not been bothered enough by it to actually look to creating a package ;)

Hrm. Real strange. I went down to the serverroom and the first port (where the TP-cable from the pfsense box is plugged) just blinked. Off and on. The link was gigabit, but it just went off and on. I tried with the old cable - and it worked! Sorry for this post, i could have tried this myself before writing a thread. Whats the chance of getting a defective network cable? :-)

Unsupported –> you're on your own. pfSense is FreeBSD and not Linux. You might want to install the developer version, since it's kind of a standard FreeBSD6.2 with pfSense on top.