Thanks for your reply, but I wounder how to do it, what attributes do I need to maintain in radius server, and how to build a php page that shows such information after a user log out?

your help is much appreciated

Regards
bassam

it is really faster …

Would do but as it is a CD version I am using the .iso.gz (2007-Mar-25 14:03:52) and it currently fails to mount the file system part way through the boot.

Don't know whether this is linked with the nice warning at the top of the forum, something I have done incorrectly or a bug.

You can with PHP.

hoo boy, that did it!  Not sure why I didn't think of that, but no more problems for the last hour or so.  Thanks again

"This setting limits the number of concurrent connections to the captive portal HTTP(S) server. This does not set how many users can be logged in to the captive portal, but rather how many users can load the portal page or authenticate at the same time! Default is 4 connections per client IP address, with a total maximum of 16 connections."

Look at the date.  That files is rebuilt hourly but we only bump the version weekly or so.

Thank you guys my problem is solved :)

Shouldnt be a problem.  I run a site with much more ppl.

Thanks, this should be fixed now.

@DanielSHaischt:

RTFM  ;D

http://www.freebsd.org/cgi/man.cgi?query=fetch&apropos=0&sektion=0&manpath=FreeBSD+6.2-RELEASE&format=html

He is "too lazy" to read a manual.  He wants everyone to spoon feed him so he doesn't have to "lift a finger"

:rolls eyes:

Sorry, I was wrong with my last post.

The problem still exists. After a reboot, no access from inside to outside without creating and deleting a dummy-nat-rule.

Regards,
Manue

yea i know syncing is hard…
so then I'll speak to Jonathan to find out if we can change to native php support in mono

PS: Why it takes 16sec to bring up the CP page comparing to 3 sec in mono?

This probably is best adressed at the m0n0 mailinglist. The CP is just a port of their code. Please verify this behaviour with a recent m0n0 before posting there.

@jeroen234:

user must have access to port 8000  (this is where the portal lives)

Yes, anything prior to recent snapshots needs a rule on the interface to permit traffic to port 8000.  Recent snapshots automatically install the needed rules behind the scenes.

Thanks for the clarification.

Maybe I should look into radius servers instead of pfsense. Maybe it is possible to get a radius server to pull parts of its database from a central server while using a local database at the same time…

Christian

After reading thru the thread before posting by post I had noticed that and have set it up accordingly. The DHCP server that assigns IP addresses on that interface assigns the interface as the primary DNS server.

Still NO go.  ;-(

If this works note that you will have to change it this way whenever you touch the captive portal settings and hit save.