Firewallrules always work for incoming traffic at an interface. You don't have to allow traffic passing out on any interface. So basically the pfSense itself is allowed always to go anywhere (in case you use the dns forwarder).

Yes there are, but I cannot recall which ones.

@almedin:

OK, but this is not something that i want… please see that functionality in RadiusManager (www.dmasoftlab.com) - that's something I would like to see in pfsense

Start a bounty then.

Usually I only want to listen on the lan anyways so I hard card the flag -i (interface name) into the rc.d file.  Then ntop will start using the lan interface.

I think I got it, in VI it was showing some escapce characters improperly.  When I used the built in editor in PFsense and removed them it read the file.  I also pointed radius to a different user file in freeradius.inc and radiusd.conf so they would read the file I'm going to generate.  If I'm not mistaken this will effectively break the gui user admin and allow me to work with just the text file anyways…?  Kind of ghetto but it should work right?

Have a look at the tinydns*.png's at http://pfsense.com/~sullrich/pics/?M=D . It's an upcoming package that is under developement atm.

Well here is the update on the radius package:

Install Package
go to terminal issue:
pkg_delete freeradius-1.1.3_1
(some errors about not being to delete everything will come up, that's fine)
pkg_add -r freeradius
start the service, done deal

Sorry I don't know more than that but it should make it easier for the problem to be fixed, thanks to everyone who helpmed me out.

Cool, thanks !

@Tabun:

Hello,

i've installed the spamd package from the package manager, but i'm not able to start the service.
In the Status-> Services window shows "stopped", if i click on start service button i'll become the message "spamd started"
but nothing goes on and the status is still stopped.

I've uninstalled and reinstalled the package, but have the same problem.

Thank for any help..

(pfsense V. 1.01 (Full install), spamd version 4.3)

Solved now

this is the package that you can install from pfsense
i have maked it stop and then start with the logging options

Whats meant to happen(mine doesn't even work) is:

Black list and greylist IP addresses get sent to the pfsense box on port 25. It whittles away their time and resources. Once it has met the conditions to be allowed to send(time, connections etc), it's meant to whitelist the IP address of the sender and then port forward directly to your specified mail server. This means spammers never touch your server and waste it's resources.

It's a great solution.

I haven't gotten this working yet but i would love to get this working. I can't troubleshoot it that far as I don't have the know how :)

I never had somebody else with the same issue that I had so I could never compare.

Once you hit the whitelist its meant to redirect your connection to port 25. I could get it to open port 25 on a grey or blacklist but as soon as it hit whitelist, no connection on port 25 for that whitelisted IP address.

Update to the latest snapshot: http://www.pfsense.com/~sullrich/1.0.1-SNAPSHOT-12-14-2006/

@redseawireless:

2 Gigs with Quad processor and still taking a crap! I am processing traffic across my wireless network covering over 150 square kilometers!
On a average day 3000 to 3800 users! CPU Load 6 to 8 percent! Memory at 1 to 2 percent! Plenty of room to run Snort and Ntop on same machine! Do you have any relevant info on this matter?

You're going to have to give more information. Be specific in telling us your testing methods. What version of pfsense are you on? Also show us log outputs when ntop goes down, etc.

I've been running snort and ntop for weeks now with no problems.

Not sure if this helps, but I had a similar issue that was caused by special characters in the ntop admin password.
  I have verified that the following special characters do not work: &)=%#!?}]
  These special characters do work: (^$@~<>{[
Those are the only characters I had the time to test.

Mail it to coreteam@pfsense.com .

You have a bounty!

I'll keep you informed.

As for now I have squid working, but I had to NAT all proxy packages to the WAN adres where squid is listening, for this test it works fine, but I don't want to enable a proxy server for the whole world.

Also squid is running fine, but at this moment I don't run squid as daemon (I want to see what's going on in the test envoirment)

I've done it now thanks ;D

I changed the enable:NO to YES in the shell script so that it always starts up by default.

Thanks for the XML explanation as well.

Well it's an IE thing…..seems to work fine in firefox.