I have just had a similar problem on a 2.0.36 / pppd-2.3.4 system which I am
setting up for dial in
- the debug logs showed authentication failing
- experimentation showed that this occurred if I tried to set IP addresses
- further experimentation showed that it was failing on authorisation of the IP
address for the remote system.
I solved it by adding * (all IP addresses) in the 4th field of the pap-secrets
Not sure if this will solve your problem but its worth checking / trying
David H
Matthew wrote:
> Hi I have a weird problem,
>
> We have 6 dialin servers that are all configured identical. One decides not
> to work.
>
> But only PAP doesnt work on it, I have checked everywere and file
> permissions, and file content is correct, does anyone have an idea where I
> should look?
>
> What happens when I log in is this, if i choose a shell login I get the
> normal login prompt, and that works fine, if i choose a PAP style login, the
> modems connect, and the dialing modem seems normal, the modem on the modem
> pool machine does seem normal too, but it can not send any data, not even
> the authenication stuff. Where am I going wrong? I've racked my brain trying
> to figure out where things are wrong but I cant quite make it.
>
> Any help will be muchly appreciated.
>
> System specs are, linux 2.0.35, pppd 2.3.5, kernel driver stock that came
> with 2.0.35 kernel (ie 2.2.0) works well on the other 5 servers so that
> 'cant' be the fault I hope.
>
> regards
> Matthew
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]
--
-----------------------------------------------------------------------
David Hawke Ph: +64 9 846 9297
[EMAIL PROTECTED] Fax: +64 9 846 9293
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
