We just assumed the customer base of a local ISP and we are retaining
their name for their users. This second ISP's customer lists are
maintained on a seperate authentication server so that we can maintain
and bill them seperately.
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)
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).
Any suggestions would be GREATLY appreciated!
--
Senior Partner of New Age Consulting Service, Cleveland Ohio (216)-619-2015
SLIP/PPP/Unix Shell 28.8k / ISDN / Leased Line
http://www.nacs.net info@nacs.net (216)-524-8414