"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> OK, but the attribute is getting written to the accouting detail file,
> so if it is getting into the accounting detail file (which is just a text
> file) then why can I not write it to MySQL.
I don't know. See the SQL queries, and SQL logs for d
>
> The request is logged to the accounting detail file, and THEN the
> FreeRADIUS-Proxied-To is generated, and the packet is proxied.
>
> Order is important. Since the packet was logged before it was
> proxied, there is no FreeRADIUS-Proxied-To attribute to log.
>
OK, but the attribute is ge
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I guess what has me stumped, is if it is showing up in the detail file
> then why wouldn't it show up sqltrace.sql ?
>
> When I use NTRadping, I add the Freeradius-Proxied-To = 111.222.111.222
> and it is sent by NTRadping as a name/value pair and g
> > 2. But when I use something like NTRadping to test the accounting start
> > and accounting stop and send the additional attributes
> > "Freeradius-Proxied-To"
> > it gets written to both the master detail file and my radacct table.
>
> Find out what's different between the packets from the N
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I am currently in the process of setting up MySQL to handle the
> accounting records. Just about everything seems to working except I
> cannot get the attribute "Freeradius-Proxied-To" to write to my
> radacct table.
Odds are that the attribute i
HI,
I am using FreeRADIUS-0.9.1 primarily to proxy requests to other ISP's
radius
servers. I have 4 dial up accelerator servers that are acting as NAS's
(clients to
our radius server). I have added the vendors dictionary to FreeRADIUS and
all seems to be working well, requests are proxied reliab
