I've been searching the docs/wiki, and can't seem to find an answer to this... what variables are available to store in the rad post auth? the sql query shows username, password, reply and date/time... Sorry if this is documented somewhere, I just couldn't find it. Steve
On 12/05/11 15:38, Steve Staples wrote:
I've been searching the docs/wiki, and can't seem to find an answer to this...
what variables are available to store in the rad post auth?
The post-auth SQL query can access any variable in the packet. If you want to store extra fields, just extend your SQL schema and change the SQL query
On Thu, 2011-05-12 at 17:06 +0100, Phil Mayers wrote:
On 12/05/11 15:38, Steve Staples wrote:
I've been searching the docs/wiki, and can't seem to find an answer to this...
what variables are available to store in the rad post auth?
The post-auth SQL query can access any variable in the packet. If you want to store extra fields, just extend your SQL schema and change the SQL query - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I understand that the query can get access to any variable, but what is in the packet normally? or is there not a "standard" set of attributes/elements in the packet? i guess i will just have to play and see... Steve
Steve Staples wrote:
I understand that the query can get access to any variable, but what is in the packet normally? or is there not a "standard" set of attributes/elements in the packet?
There is NOTHING standard in the packet. If you want to know what's in the packet, use debugging mode, or wireshark. Alan DeKok.
On Fri, 2011-05-13 at 07:04 +0200, Alan DeKok wrote:
Steve Staples wrote:
I understand that the query can get access to any variable, but what is in the packet normally? or is there not a "standard" set of attributes/elements in the packet?
There is NOTHING standard in the packet.
If you want to know what's in the packet, use debugging mode, or wireshark.
Alan DeKok.
Thanks Alan, I wasn't sure if there was or not a standard... I guess now I can understand why you get frustrated at *some* people (others just deserve it). I appreciate your time and reply. Steve.
Steve Staples wrote:
I wasn't sure if there was or not a standard... I guess now I can understand why you get frustrated at *some* people
Exactly. Q: What's in the Access-Request? A: I've been doing this for 15 years. I have no idea. Q: Why not? You're the expert! A: There are too many broken NAS vendors. Q: But you can guess, can't you? A: No. I *really* mean "I have no idea". As always, the only way to tell what's going on is to run the server in debugging mode. Alan DeKok.
On 05/12/2011 08:35 PM, Steve Staples wrote:
I understand that the query can get access to any variable, but what is in the packet normally? or is there not a "standard" set of attributes/elements in the packet?
No. It depends entirely on the NAS i.e. it's specific to you and your installation. Some attributes your NAS *might* send, and which *might* be useful, are: Calling-Station-Id Called-Station-Id *-AVPair (e.g. Cisco-AVPair = "ssid=FOOBAR") ...and so on.
participants (3)
-
Alan DeKok -
Phil Mayers -
Steve Staples