On Mon, 26 Jun 2000, Clifford Kite wrote:
|I'm using pppd 2.4.0b2 and am unable to run as root and make it request
|CHAP or PAP during LCP negotiations by explicitly specifying auth, or
|require-chap, or require-pap. Is that supposed to happen?
I now believe the real problem was simply my lack of understanding about
how the local and remote names and secrets need to be specified to pppd.
Apparently if you require the peer to authenticate itself to you with one
of these options then you had better be configured so that pppd believes
a priori that the authentication can actually take place.
|Moreover, running as root and using auth, or require-chap, or require-pap,
|and specifying the option "allow-ip 128.83.0.0/16", results in the error
|message
|
| invalid address length 162 in auth. address list
|
|and the connection is disallowed with the message
|
| Peer is not authorized to use remote address 128.83.xxx.xxx
|
|The man pages say that the form of the IP address specification for the
|allow-ip option is the same as that for a secrets line. What's up doc?
This has been fixed in 2.4.0b3.
---
Clifford Kite
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
