[RADIATOR] ServerTACACSPLUS logging improvements

Hartmaier Alexander alexander.hartmaier at t-systems.at
Wed Jun 8 03:28:35 CDT 2016


On 2016-05-31 15:24, Heikki Vatiainen wrote:
> On 31.5.2016 12.57, Hartmaier Alexander wrote:
>
>>>> - Could not get peer name on TacacsplusConnection socket: Transport
>>>> endpoint is not connected
>>> Hmm, that's happening very early withing server tacacsplus, so there's
>>> no request, client, etc is available yet. Improvements here may be
>>> small, if any.
>> Than please at least add more information to the error message itself so
>> that at least the misbehaving client can be identified.
> Hmm, do you get these often? Also, does your configuration have FarmSize
> enabled? This error occurs very early after the new connection has been
> accepted. The code tries to figure out the address and port of the
> client, but getpeername call fails.
Yes, all the time. No FarmSize so far. So these are reverse dns lookups?
Can we disable them?
>
> I noticed the accept for the new connection is done slightly differenty
> than what the StreamServer class does, so I was thinking if this is
> something StreamServer does better in farm size environments.
>
> I'll see if there's anything more that can be logged too.
Thanks!
>
> Thanks,
> Heikki
>



*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
Handelsgericht Wien, FN 79340b
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then
delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*


More information about the radiator mailing list