Well the webgui IS the gui.
How many rules are you talking about?

If you use aliases appropriatly you can reduce the amount of rules drastically.
IMO if you loose overview over your rules a rewrite is called for (with correct documentation).

pefect, thanks!

Threads automatically lock after a certain amount of time with no new posts, it probably just expired.

I haven't seen any posts from the person who was planning on making them in quite some time.

http://doc.pfsense.org/index.php/FTP_Troubleshooting

Hi,

Thanks for your response.

The strange thing is I already editted that file. When I call on it directly I only see the 4 hrs graph,when I go through the menu it show all at an average of 5 minutes (300 sec) but the numbers dont' seem to add up.

Strange…. Any thoughts?

radius server ip is going to be the ip of your radius authentication server and the shared secret is the secret ket you setup on the radius server to check for when other computers would like to talk to it. How far have you gotten in your setup as of now?

usually they are flag files that are just touched so that other processes which are run periodically (cron, etc) can see some action that needs to be done.

Not sure about the one named "touch" that was probably a bug somewhere or perhaps done by hand(?)

Yeah, it's broken on 1.2.3 release.
See here: http://forum.pfsense.org/index.php/topic,21381.0.html

"0 24 * * *" is what you give crontab for the date.

You probably want something like:

date +%Y%m%d%H%M%S in that place.

I checked it, it seems like pretty good.
I am gonna install pfsense 1.2.3 upgrade, I checked the upgrade guide.it seems like it is pretty safe doing that.
but since I am not very knowledgeable about pfsense, I have little concerns.
if you guys kindly share your suggestions before doing this upgrade, I really appreciate.
Thank you

@crazybyte:

Could you explain why it works only after the service is ran for some time?

My guess is that the ntp server needs some time to pass to be confident that the ntp client has stabilised its time offset calculation and that the server doesn't offer the service until that has happened.

I tested an other CF-Card (2GB instead of 4GB), and nanobsd is working like expected: on boot, I can change interactively which slice to boot, mount shows /dev/ufs/pfsense0 and pfsense1 for slice 1 and 2, and I can change the bootup slice in Webgui without errors.

Thank you for your comments.

Up to last week I knew that pfsense is great. Now I know additionally that this forum is great, too.

On embedded, /var is a memory disk, only about 30MB in size.

You must disable squid's caching if you want to run it on embedded – its useful only for access control and authentication in that context.

If you really want caching, you'll need to manually connect and configure some kind of volatile storage (e.g. external or secondary HDD) and set squid to go there. There have been other threads in the forum that discuss this, but it is unsupported.

@Perry:

Might help http://forum.pfsense.org/index.php/topic,14847.0.html

I went through many posts in the forum but I missed this one… it contains exactly what I need. Thanks a million!