(RADIATOR) Request Attributes using PacketTrace

[Steve Lalonde]

Hi

I'm using PacketTrace to help debug my radius config, I'm getting all  
the reply attributes but none of the request attributes. Only way I  
can see the request attributes is to run the whole config at trace 4  
but that hurts at 15 requests a second :( the handler I'm working on  
only gets 1 request every 5 mins.

So question is where do I put the PacketTrace to see the request  
attributes for just this handler?

I have tried in the client section but no luck.


Only thing I can think of is to proxy the request to a spare server  
but thats not really a solution when debugging a single customer  
problem.


I can do it with monitor but trace 4 even with trace_username is  
logging every sql query for the entire server. I could edit SqlDb.pm  
and turn that off but then I cant see the queries for the debugging. I  
would also have to get lucky with the trace_username as there are 400  
users on the handler I'm trying to work on.


Any ideas?


-- 
Steve Lalonde RTFM
Chief Technical Officer
Entanet International Ltd
http://www.enta.net/



--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.