This is definately wrong. RadiusNT 2.5.2xx and higher validate
the entire packet ahead of time, and your length above is larger
than the packet data (so its malformed and we ignore the request).
This is from WUPG test (see the FAQ entry below for more details).
Send: %01D%00,0123456789012345%01%06TEST%02%18abcdefghijklmnop
> Expected command response: %03d
> Send to disconnect: (nothing entered here)
You have two choices for an expect. In either case, the
second late should match the second letter of the expect
(and case does matter).
> This is what RadiusNT 2.5.214 sees when WUG tries to test it:
> radrecv: Request length:44 UDP Length:28 Request from netmon.ids.net -
> Malformed Packet
> Resp Time: 0 Auth: 1/0 -> 1 Acct: 3/0/0 -> 3
>
> Very odd......
This is from the RadiusNT FAQ. The only different here is the
new stuff prefers the %00 type characters wheras the older stuff
uses the \x type notation.
> ipSwitch
>
> Can I use WhatsUp to monitor the status of RadiusNT running as a service?
>
> WhatsUp Gold can monitor your RADIUS servers and tell you about
> an outage. Instructions are included with it on how to monitor a
> RADIUS server.
>
> For RadiusNT:
>
> Create a user called wupg (or test, or whatever, just make it four
> characters) with a password of "ANY" (no quotes, all uppercase).
> The parameters shouldn't make since for a normal user to login as.
> I use a User-Service=Dialback to insure no one can use the account.
>
> Restart RadiusNT is in text mode.
>
> In WUPG, enter the following:
> Port: 1645 UDP
>
> Send on connect: "\aD\@,0123456789012345\a\fwupg\b%18abcdefghijklmnop"
>
> Expect after: "\bD"
>
> You can change the wupg name to any four characters, just don't change anything else in the send string.
>
--Dale E. Reed Jr. Emerald and RadiusNT/X__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart