Re: (RADIUS) Invalid request authenticator. (fwd)

Scot W. Hetzel (hetzels@westbend.net)
Wed, 29 Apr 1998 20:23:50 -0500

-----Original Message-----
From: MegaZone <megazone@megazone.org>

>It has been reported by a number of people. Current theory is that
>the addition of Vendor-Specific, and the fact that the current RADIUS
>server doesn't understand it, means the authenticator calculations
>don't match. Don't know if that's the case, seems probable.
>

Thanks for the theory, now if we could only get it as a fact. :)

>>All three new entries were added.
>>They only show up on Stop records from Portmaster2.
>
>No, this is from a PM-3. Vendor-Specific was added in the 3.8 betas,
>which are only available on PM-3s. Unless you are in a closed beta for
>PM-2s - in which case you've violated your agreement by posting about it
>here. 'portmaster2' is coming from your DNS.
>
I took his message as referring to PM3s only. Its just that he might have
his PM3s labeled as portmaster1, portmaster2, portmaster3, ..., portmasterN.

Scot

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-radius' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>