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.
>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.
>Wed Apr 29 17:43:38 1998: [374] Vendor-Specific = ""
>Wed Apr 29 17:43:38 1998: [374] Service-Type = Framed-User
>Wed Apr 29 17:43:38 1998: [374] Framed-Protocol = PPP
>Wed Apr 29 17:43:38 1998: [374] Framed-IP-Address = 209.20.190.221
>Wed Apr 29 17:43:38 1998: [374] Acct-Delay-Time = 0
>Wed Apr 29 17:43:38 1998: [374] accounting: client portmaster2.rcia.com sent
>accounting-request with invalid request authenticator
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>^^^
>Wed Apr 29 17:43:38 1998: [374] Sending Accounting-Response for id 167 to
>portmaster2 (209.20.190.3)
-MZ
-- <URL:mailto:megazone@megazone.org> Gweep, author, webmaster, human being, me "A little nonsense now and then, is relished by the wisest men" 781-788-0130 <URL:mailto:megazone@gweep.net> <URL:http://www.megazone.org/> Hail Discordia! - 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/>