I wrote a perl script that tries to get around this. Unfortunately it
assumes a PM-3 will always display one type of address format for any one
session -- either IP address or host address. (Any multichannel user will
have identical IP address assignments so you can skip over those dups.) For
example, here's the 2 situations I would expect (assuming 192.192.192.1 is
a pointer to host1.domain.com):
S0 - - Log/Net In IDLE 0 0
S1 usera 192.192.192.1 Netwrk In ESTABLISHED 9 0
S2 usera 192.192.192.1 Netwrk In ESTABLISHED 9 0
or
S0 - - Log/Net In IDLE 0 0
S1 usera host1.domain.com Netwrk In ESTABLISHED 9 0
S2 usera host1.domain.com Netwrk In ESTABLISHED 9 0
But here's what occasionally shows up
S0 - - Log/Net In IDLE 0 0
S1 usera host1.domain.com Netwrk In ESTABLISHED 9 0
S2 usera 192.192.192.1 Netwrk In ESTABLISHED 9 0
Which is strange since the PM-3 obviously knows what 192.192.192.1 maps to.
I guess I could make the script do reverse lookups on the fly, but man is
that going to slow down the script. Any other suggestions? Megazone? Could
this be considered a very low priority bug?
The script is vailable at
ftp://ftp2.vcnet.com/pub/radius/abuser.pl
and requires pmwho and pmcom to run.
Jon