Hi, I have a problem with FR 3.0.12 as a proxy with a perl modules in the authorize section which does not include the EAP-Message attributes from the incoming request into the outgoing proxy request. When I disable the perl module, the EAP-Message is proxied correctly and the problem only occurs with multiple EAP-Message attributes. I found this conversation from 11/2016 which seems to be related: http://freeradius.1045715.n5.nabble.com/PERL-and-EAL-TLS-Modul-gt-Failed-to-... However, the conversation seems to have stopped without a solution or fix and I don't see anything in the release notes of 3.0.13 or 3.0.14 either... so I guess the issue has not been taken care of yet. Here's some debugging output: (1255) Received Access-Request Id 41 ... length 804 (1255) User-Name = "x" ... (1255) EAP-Message = 0x0276024819800000023e16030302061000020202006288d372a198ab690b34793275ed4eb9b448611f3cf207b5321e147bd85ce371e5d95b9f43572fab73517455ef1b3fe3eca0232825c5feb7e7233c3b08cd9d77205d49a157afa734730496f7a2b9b284654486313cc104e5f70fbd0ff2b5478549a5 ... (1255) session-state: No cached attributes (1255) # Executing section authorize from file server.conf (1255) authorize { (1255) [preprocess] = ok (1255) exec_perl: $RAD_REQUEST{'User-Name'} = &request:User-Name -> 'x' ... (1255) exec_perl: $RAD_REQUEST{'EAP-Message'} = &request:EAP-Message -> '0x0276024819800000023e16030302061000020202006288d372a198ab690b34793275ed4eb9b448611f3cf207b5321e147bd85ce371e5d95b9f43572fab73517455ef1b3fe3eca0232825c5feb7e7233c3b08cd9d77205d49a157afa734730496f7a2b9b284654486313cc104e5f70fbd0ff2b5478549a5d992778059693e3857f542e79b6bcca778b991167120b479ac90efc8508af066f6e600720b1f43130963f9f9299b91736210d6e3ad28eaed792800c9dff95c7df1eeae1a2bd5f18394c41476d38e8a348f2f0093890dd192695840f6e681ccc6cdb79b95fba1cd6a479d9ff8bc57312454d9203e9d19e4544650374e4f632bbb2cac4dfa501401862b3eb2152d7dc96b2d30a736233ba77600009a7ca4702d76ddd4f5e5afd9f00426ff88b8fb07902e7aacdfd76ec86847600c764177b435f8cdf2c4b44a6b62154c60640ff21ccac1105a8f0088a6e6582d7e70f525829b90a2961348e569fc71be3347280381c7d8b58d0c3a502042539092d31e73e0f44ffdfb01b618c4b0be79df064e3584c62e9374ddba8301e7afa9fcca4f286b8463b2b6d885088db0c1275873714904141ab79b62f5a8f363466c33c659d58f139cbaaf6db5b3aa7b6eececc1224c626b22bb529fba206d8816fa9da708cf223e3c50079e3378cfd37890b331f0092ad5ae62e218c3dde18d974ff24318bb16639702399448d62b92' ... (1255) exec_perl: &request:User-Name = $RAD_REQUEST{'User-Name'} -> 'x' (1255) exec_perl: ERROR: Failed to create pair &request:EAP-Message = $RAD_REQUEST{'EAP-Message'} -> '0x0276024819800000023e16030302061000020202006288d372a198ab690b34793275ed4eb9b448611f3cf207b5321e147bd85ce371e5d95b9f43572fab73517455ef1b3fe3eca0232825c5feb7e7233c3b08cd9d77205d49a157afa734730496f7a2b9b284654486313cc104e5f70fbd0ff2b5478549a5d992778059693e3857f542e79b6bcca778b991167120b479ac90efc8508af066f6e600720b1f43130963f9f9299b91736210d6e3ad28eaed792800c9dff95c7df1eeae1a2bd5f18394c41476d38e8a348f2f0093890dd192695840f6e681ccc6cdb79b95fba1cd6a479d9ff8bc57312454d9203e9d19e4544650374e4f632bbb2cac4dfa501401862b3eb2152d7dc96b2d30a736233ba77600009a7ca4702d76ddd4f5e5afd9f00426ff88b8fb07902e7aacdfd76ec86847600c764177b435f8cdf2c4b44a6b62154c60640ff21ccac1105a8f0088a6e6582d7e70f525829b90a2961348e569fc71be3347280381c7d8b58d0c3a502042539092d31e73e0f44ffdfb01b618c4b0be79df064e3584c62e9374ddba8301e7afa9fcca4f286b8463b2b6d885088db0c1275873714904141ab79b62f5a8f363466c33c659d58f139cbaaf6db5b3aa7b6eececc1224c626b22bb529fba206d8816fa9da708cf223e3c50079e3378cfd37890b331f0092ad5ae62e218c3dde18d974ff24318bb16639702399448d62b92' ... (1255) [exec_perl] = noop ... (1255) } # authorize = ok (1255) Starting proxy to home server ... port 1812 (1255) # Executing section pre-proxy from file server.conf (1255) pre-proxy { (1255) } # pre-proxy = noop (1255) Proxying request to home server ... port 1812 timeout 5.000000 (1255) Sent Access-Request Id 130 from ... length 273 ... (1255) User-Name = "x" (1255) EAP-Message = 0x ... Waking up in 0.1 seconds. Kind regards, Thor