(RADIATOR) radpwtst trace level 3

[Hugh Irvine]

Hello William -

You should consider Radar for per-object level debugging.

	http://www.open.com.au/radar

Of course you can always telent to the Monitor port and enter the 
low-level commands, but using Radar is *much* easier.

You can also use the PacketTrace parameter in your configuration file.

Have a look at the Monitor and PacketTrace sections of the Radiator 
3.3.1 reference manual.

regards

Hugh


On Thursday, October 3, 2002, at 07:26 AM, William Hernandez wrote:

> Hello everyone,
>
> Using the radpwtst of Radiator 3.3.1 there is no difference in output
> between "radpwtst -trace 2" and "radpwtst -trace  3" and "radpwtst
> -trace 4" provides way too much output.
> # radpwtst -trace 3
> sending Access-Request...
> OK
>
> I seem to recall that with Radiator 2.18.2
> # radpwtst -trace
> would output the attributes in the Access-Accept and the final result.
>
> This was simpler and cleaner output.
>
> Is "radpwtst -trace 3" working correctly?
>
> Thanks in advance,
> William
>
> ===
> 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.
>
>

NB: I am travelling this week, so there may be delays in our 
correspondence.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
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.