Thank you very much. On 2016-03-03 15:24, freeradius-users-request@lists.freeradius.org wrote:

Send Freeradius-Users mailing list submissions to freeradius-users@lists.freeradius.org

To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeradius.org/mailman/listinfo/freeradius-users [1] or, via email, send a message with subject or body 'help' to freeradius-users-request@lists.freeradius.org

You can reach the person managing the list at freeradius-users-owner@lists.freeradius.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Freeradius-Users digest..."

Today's Topics:

1. Re: RadPerf '-A delay, lifetime' arg does not copy the 'Calling-Station-Id' from Accept-Request (Alan DeKok) 2. linelog problem (Maja Wolniewicz) 3. Stripping prefix with unlang (Bernd) 4. Re: Stripping prefix with unlang (Herwin Weststrate) 5. Re: Stripping prefix with unlang (Alan DeKok) 6. Re: linelog problem (Alan DeKok)

----------------------------------------------------------------------

Message: 1 Date: Thu, 3 Mar 2016 08:17:24 -0500 From: Alan DeKok <aland@deployingradius.com> To: jbaltero@gmail.com, FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: RadPerf '-A delay, lifetime' arg does not copy the 'Calling-Station-Id' from Accept-Request Message-ID: <D0CC71E0-6386-4864-A2A4-865E115DC78A@deployingradius.com> Content-Type: text/plain; charset=us-ascii

On Mar 2, 2016, at 11:24 PM, Jim <jbalatero@visp.net> wrote:

...

As you can see on the Accounting-Request, there's no Calling-Station-Id. How do I get it to be included on the Accounting Packet?

We'll see if we can get a new version of radperf out soon to fix this.

Alan DeKok.

------------------------------

Message: 2 Date: Thu, 3 Mar 2016 14:28:45 +0100 From: Maja Wolniewicz <mgw@umk.pl> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: linelog problem Message-ID: <56D83C0D.5070709@umk.pl> Content-Type: text/plain; charset="utf-8"; Format="flowed"

We are running freeradius 3.0.11 on CentOS 6.7. Recently we experienced a few radius process hangs - it didn't handle any request and in the log appeared only a lot of:

Thu Mar 3 08:48:24 2016 : Error: (187540) Ignoring duplicate packet from client CM port 1814 - ID: 118 due to unfinished request in component post-auth module eduroam_log Thu Mar 3 08:48:33 2016 : Error: (187814) Ignoring duplicate packet from client CM port 1814 - ID: 152 due to unfinished request in component <core> module <queue>

Our investigation showed that these problems start after requests containing a "strange" username Wed Mar 2 08:01:52 2016 : Auth: (127068) Login incorrect: [юз] (from client AP-UMK port 20526 cli 88-A7-3C-DB-35-02) Thu Mar 3 08:48:14 2016 : Auth: (187534) Login incorrect: [በᑱ] (from client AP-SPEC port 36865 cli 24-0A-64-1F-C1-D3) Thu Mar 3 09:38:19 2016 : Auth: (53871) Login incorrect: [юз] (from client AP-UMK port 20613 cli 88-A7-3C-DB-35-02)

It turned out that it is caused by linelog module. After we removed %{User-Name} from this line

Access-Reject = "%S eduroam-auth#ORG=%{request:Realm}#USER=%{User-Name}#CSI=%{%{Calling-Station-Id}:-Unknown Caller Id}#NAS=%{%{request:NAS-IP-Address}:-No NAS IP}#CUI=%{%{reply:Chargeable-User-Identity}:-Unknown}#MSG=%{%{reply:Reply-Message}:-No Failure Reason}#RESULT=FAIL#"

the problem disappeared and strange usernames are handled smoothly.

It looks like a linelog bug.

Maja

-- Maja Gorecka-Wolniewicz mgw@umk.pl Uczelniane Centrum Information & Communication Informatyczne Technology Centre Uniwersytet Mikolaja Kopernika Nicolaus Copernicus University Coll. Maximum, pl. Rapackiego 1, 87-100 Torun, Poland tel.: +48 56-611-27-40 fax: +48 56-622-18-50 tel. kom.: +48-693032574