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.

I see. I will definitely try another switch in that case. It was a cheap one I bought off of someone on ebay for ~20 dollars. TP-Link 16 port switch. I will test against a small netgear switch that I have and see how the performance is since I know its a good one.

Read the thread Cry Hovok provided: @David_W: Typically options such as LDAP support that create added dependencies on fairly 'heavyweight' libraries are disabled by default in FreeBSD ports - and are therefore disabled in the FreeBSD package. This is to avoid pulling in a load of unnecessary baggage that many will not use, also there are at least four options for the OpenLDAP client libraries (2.3 or 2.4; in either case with or without SASL). The www/squid30 port does have an LDAP option that you can set, but you'll need a FreeBSD box (or virtual machine) to build a suitable package, and you're on your own so far as getting the LDAP features going in pfSense.

With the box and a cross over cable set the lan ip to the one in the messed up rule. Fix the xml. Reboot system. Set the ip on client system and connect it to the system. open console and reset password if ness. Open web and input ip. This should work.