Hello Eric -
You will see something like this in your trace 4:
Sun Jan 20 19:23:21 2019: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 51327 ....
Code: Access-Request
Identifier: 160
Authentic: <239>m<213><226><243>fm<163><194><149><144><196><128><7><165><29>
Attributes:
User-Name = "toto@huGh"
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Identifier = "203.63.154.1"
NAS-Port = 1234
Called-Station-Id = "123456789"
Calling-Station-Id = "987654321"
NAS-Port-Type = Async
User-Password = 5=1b4<208>8b<170>!C<159>G<144><192><234>
this line:
*** Received from 127.0.0.1 port 51327 ….
shows you the IP address of the client sending the request (which matches on
the source IP address of the request)
and these lines *may* also identify the client (or not as the case may be - in
this particular case they don't)
NAS-IP-Address = 203.63.154.1
NAS-Identifier = “203.63.154.1"
hope that helps
regards
Hugh
> On 24 Jan 2019, at 12:11, Eric W. Bates <[email protected]> wrote:
>
> How do I see which <client> block an incoming Access-Request matches (or
> doesn't)?
>
> I have "Trace 4" turned on, and I'm seeing nothing that looks like
> information about which client is applying.
>
> Thanks.
>
> --
> Clark 159a, MS 46
> 508/289-3112
>
>
> _______________________________________________
> radiator mailing list
> [email protected]
> https://lists.open.com.au/mailman/listinfo/radiator
--
Hugh Irvine
[email protected]
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc.
Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc.
_______________________________________________
radiator mailing list
[email protected]
https://lists.open.com.au/mailman/listinfo/radiator
