RE: Leading \000 in accounting-records

2004-05-10 Thread Michael Markstaller
it. Michael -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan DeKok Sent: Friday, April 30, 2004 8:37 PM To: [EMAIL PROTECTED] Subject: Re: Leading \000 in accounting-records Michael Markstaller [EMAIL PROTECTED] wrote: I'm getting some

Re: Leading \000 in accounting-records

2004-05-10 Thread Alan DeKok
Michael Markstaller [EMAIL PROTECTED] wrote: just verified with cvs-snapshot-20040506 and the leading \000 are gone in Tunnel* attribs. Good. except in attribute Acct-Tunnel-Connection, it still reads=20 Acct-Tunnel-Connection =3D \0002475495 It's not a tagged attribute. The RFC says

Re: Leading \000 in accounting-records

2004-04-30 Thread Chris Brotsos
On Apr 30, 2004, at 1:37 PM, Alan DeKok wrote: Michael Markstaller [EMAIL PROTECTED] wrote: I'm getting some strange leading \000 in some L2tp-attributes within accounting records like (IPs are changed): Tunnel-Server-Endpoint:0 =3D \00010.11.1.1 It's a bug. Just out of curiosity, was

Re: Leading \000 in accounting-records

2004-04-30 Thread Alan DeKok
Chris Brotsos [EMAIL PROTECTED] wrote: Just out of curiosity, was this bug just recently introduced into the system? I ask because we are running a CVS head after 0.9.3 and don't have this problem. No, it's most likely due to a client doing weird things. If the tag is zero, then the

Leading \000 in accounting-records

2004-04-29 Thread Michael Markstaller
I'm getting some strange leading \000 in some L2tp-attributes within accounting records like (IPs are changed): Tunnel-Server-Endpoint:0 = \00010.11.1.1 Tunnel-Client-Endpoint:0 = \00010.1.1.1 Tunnel-Assignment-Id:0 = \0001 Tunnel-Client-Auth-Id:0 = \000lac_xyz