alright, i found the root cause. it's due to our radius server does not respond to it.

thank for the reply, that sounds good i will try release 2 of pfs, i have to find my way using radius server then.

I'm not sure anyone has this working all the way. You might have more luck searching for the phrase "single sign-on" instead of auto login.

There isn't a way to let users manage their own passwords in pfSense right now.

You could setup a FreeRADIUS server, point the CP authentication at it, and find a web-based GUI for FreeRADIUS that includes a mechanism that lets the user change their own password.

I've now been informed that this is not the case - That the portion that was locked down was relative to the users accessing a Enterprise authenticated network…

So, I'm going to try a standard Captive Portal...

@renoid:

Hi,

I have installed Pfsense 1.2.3 rc3 with captive portal and Per user bandwidth limit, it works fine.

I wondered if is possible to assign more bandwith to determinate user.

Thanks in advance

tutorials please ? i'am very need it

@tenso:

hello
the configuration file clients.conf radius we have the following syntax
Customer host.domainname
(
secret = motdepasseradius
shortname alias =
nastype = Other
)
in this file are given addresses of access points that have the right to access the radius server for authentication
but what these attributes  secret shortname and nastype represent ?

my access points can not access to the RADIUS server
What should I change on the client file. conf
thank

Ok. It goes like this:

client 192.168.15.254 {
        secret          = yoursharedsecret
        shortname      = Hotel-California
}

First word is client and it is your access unit/server/AP/whatever. It is not customer, it is hard-coded and all radius servers have it.
You can use host name but, please, don't. Use IP address.

Brackets are curly - no other can be used (for freeradius) I don't have other radius server here so I can't check them now.

Secret is a secret word (not known/shared/whatever to other people/systems) shared only between your client access unit/server/AP/whatever. Yes, you can use the same one for all your systems.

Shortname is, well, shortname. Name your client as you wish.

nastype=other is OK.

Is that enough for get you started?

Please read HOWTO's but feel free to ask.

Sasa

Hi thanks for the reply.

The problem is both the users are on the same interface, I've figured out how to do it using just squidguard by putting the proxy settings into the browser but what I was hoping I could do was have a transparent proxy, and then Captive Portal could use the SquidGuard users and settings for its login.

Although I am presuming this isn't possible  ???

I got frustrated and started changing settings all over the place on the iPad as well as the pfSense side.  I guess its possible I disabled the setting and wasn't aware, as the iPad is now working with redirection turned back on.

thank you
it works

Add a static route that will direct traffic to that IP out a gateway IP on the MAN interface.

Cool looks like what I was looking for.  Thanks!

Thank you.

It seems to work.

Through much testing I found the error.

This was caused by the default gateway in the final rule.
The default gateway must be "default". if you use any other gateway (directly or balancer) it will not work and react as described above.