Only about several hundred thousand people in Michigan using the MichNet
Dial In Network.
> What it boils down to is that we have been succesfully using Merit Radius
> 2.4.21 for the past 12 months with a single server and no Realm
> authentication. Our portmasters are configured to use the host: prompt,
> which allows the users to select PPP, Cslip or Terminal logins.
>
> Now that we have added Realm based authentication for this second base of
> customers, we are seeing 4 out of every 5 logins failing between the servers.
>
> Server A receives the request, determines that it is a Realm request and then
> forwards it to server B.
>
> This is a snippet of our logfile.
>
> Fri Sep 13 11:19:04 1996: rad_authenticate: 64/8 'kevinc@acclink.com' at
> 207.166.192.20 PPP
>
> Fri Sep 13 11:19:04 1996: rad_2rad_recv: Received unexpected reply to
> request 7 from '207.166.192.130[1645]' (type 3)
>
> Fri Sep 13 11:19:07 1996: rad_2rad_recv: Received unexpected reply to
> request 7 from '207.166.192.130[1645]' (type 3)
>
> Fri Sep 13 11:19:10 1996: rad_2rad_recv: Received unexpected reply to
> request 7 from '207.166.192.130[1645]' (type 3)
This sounds like the secrets between the two machines are messed up. Or
it may be a problem with the authenticator.
> I'm also receiving a -LOT- of requests from users that are using PAP that
> show up in the log file as "dumb" requests (Terminal / Shell Login).
The default behaviour of Merit RADIUS (in the absence of the Service-Type
attribute in the Access-Request) is to assume dumb terminal access.
Regards,
web...
-- William Bulley, N8NXN Senior Systems Research Programmer Merit Network Inc. Domain: web@merit.edu 4251 Plymouth Road MaBell: (313) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (313) 747-3185