Re: PortMaster 3.3.1c1 upgrade - logins now failing
Bill Butler (bill@telalink.net)
Sun, 30 Jun 96 18:32:47 -0500
>On Fri, 28 Jun 1996, Mike Peterson wrote:
>
>> I have just upgraded 2 PortMaster PM-2's to version 3.3.1c1;
>> one works fine, and one will not talk to anyone successfully
>> over the serial ports (but pmconsole, and telnet to it work fine).
>>
>> Problem 1) User is coming in, modems appear to negotiate a 28800
>> session, but as soon as PPP starts, he is disconnected. The 'auth'
>> syslog shows:
>>
>> pm1 dialnet: port S2 xxxxx succeeded dest 199.71.60.1
>> pm1 dialnet: port S2 ppp_sync failed dest 199.71.60.1
>> pm1 S2: Session Terminated - NAS Error - PPP Unknown State
>>
>> He could connect until the upgrade was installed.
>
>Is this happening to more than one user?
>
>>
>>
>> Problem 2) User is being refused RADIUS authentication, only since
>> upgrade was installed. The 'auth' syslog shows:
>>
>> pm1 dialnet: port S0 yyyyyy@zzz login failed
>> pm1 portmaster: port S0 session disconnected user yyyyyy@zzz
>>
>> and the 'radiusd' logfile shows:
>>
>> rad_authenticate: 7/78 'yyyyyy@zzz' at pm1 dumb
>> Authentication: 7/78 'yyyyyy@zzz' via pm1 from pm1 0 dumb -
>> FAILED Authentication failure
>>
>> (We are using Merit RADIUS, and passing @zzz to a remote server).
>
>Is this happening to more than one user? Have you checked the logs on the
>remote server?
After upgrading to 3.3.1c1, We are experiencing precisely the same
problems. Yes it is happening to more than 1 user.....all users as a
matter of fact. Downgrading to the previous OS solves the problem.
--
Bill Butler
Bill@Telalink.Net
President, Chief Operating Officer
615.321.9100 ext.230
Key fingerprint = 11 B6 5E FB 6C 9C 3A 54 EB 6D 57 5E D4 13 6D 38