Ok, I got a hint. I was mistaken, it was doing the mess for '\n' and
for '\t' also in accounting but I find from where it comes.
In my default/post-auth I had :
update reply{
Tunnel-Type = 13
Tunnel-Medium-Type = 6
# I use the real ID for setting the vlan nu
Stun Box wrote:
> So, why do I get that behaviour ? May it come from my configuration files ??
I have no idea. Perhaps you could be more specific about what you're
seeing. Use real examples.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
So, why do I get that behaviour ? May it come from my configuration files ??
Thanks for reading,
G.
2009/8/15 Alan DeKok :
> Stun Box wrote:
>> but the server does the escaping stuff for \t in the access and
>> accounting packets received,
>> and for the \n only for access and *not* for accoun
Stun Box wrote:
> but the server does the escaping stuff for \t in the access and
> accounting packets received,
> and for the \n only for access and *not* for accounting.
Huh? The same code is run in both cases. There is no magic "string
handling for accounting" versus "string handling for a
but the server does the escaping stuff for \t in the access and
accounting packets received,
and for the \n only for access and *not* for accounting. Is that a bug
or I misconfigured something ?
Thanks for reading,
G.
2009/8/14 Alan DeKok :
> Stun Box wrote:
>> The mystery is why there is two b
Stun Box wrote:
> The mystery is why there is two backslash for each "User-Name"
> excepted in the accounting request ? (I ask, because it does the mess
> in my sql base for accounting).
Because the server understands \t, ", and \n in strings. For this to
work, it has to treat the backslash cha
Hello everybody,
I'm doing some tests with wpa_supplicant(freebsd) + aironet 1252 +
freeradius2.1.6 (freebsd portage). And I have a mystery I can not
explain.
I test 2 user with a domain. This is my configuration files for
wpa_supplicant. They have just their first user letter mismatching.
USER_
7 matches
Mail list logo
