Difference in escaping character

Peter Balsianok balsianok.peter at gmail.com
Thu Apr 23 16:42:38 CEST 2015

I have checked Access-Accept packet via wireshark (There is everything ok).
I didn`t realize that this is behaviour of the radclient (how string are
printed to STDOUT)


On Thu, Apr 23, 2015 at 3:32 PM, Alan DeKok <aland at deployingradius.com>

> On Apr 23, 2015, at 9:22 AM, Peter Balsianok <balsianok.peter at gmail.com>
> wrote:
> > I have compared reply attributes between version 2.2.6 & 3.0.8 ( for the
> > same request), i found little difference for Cisco-AVPair attribute
> > (escaping \\n vs \n).
>   The server has been fixed to use correct escaping.
>   If you want a Perl string with a literal "\" followed by a literal "n",
> then use "\n" in a string.  If you want a Perl string with an embedded
> carriage return, then the string must contain an embedded carriage return.
>   Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html

More information about the Freeradius-Users mailing list