ppp-2.3.0-static.diff
Patch to ppp-2.3.0 to support using static IP addresses with
Mgetty and AutoPPP. Does not affect normal dynamic assignments.
This patch is for 2.3.0 only and not very well tested, comments
welcome. Apply with "patch -p1" in the top directory of the
ppp-2.3.0 sources. After getting ppp-2.3.0 to compile cleanly on
your system, patch and re-compile. (No need to re-compile kernel)
While the patches should work with any authentication method, we
did not have success getting 2.3.0 to work with USE_PAM=1 option.
(Out of the box). We use shadow passwords and "make HAS_SHADOW=1".
Bottom line...you should get ppp-2.3.0 working BEFORE you apply
the patches.
After patching and re-compiling, update the pap-secrets file to
contain the entries of those users you want to have static
IP addresses. Typical entry might look like:
#client server secret IP addresses
jdoe * realpswd 207.69.189.15
* * "" *
Also, inform your static IP users to include their IP when
connecting. ex: pppd 207.69.189.15:
Or for Windows folks "check" Specify an IP address.
Note: The second line is what most folks will use to authenticate
users who will be dynamically assigned their addresses by
/dev/ttyXX. This along with the login option allows users to
be PAP authenticated against the /etc/passwd or /etc/shadow.
If you enter each and every user into your pap-secrets file
and do not have the last line,(wildcards line) you MUST place
a "*" at the end of each users line. Without it authentication
will fail. For example:
#client server secret IP addresses
jdoe * passwd 207.69.189.15 *
This "*" at the end allows the patches to work properly without
changing the normal process. The IP address is normally assigned
via the /etc/ppp/options.ttyXX file. The patches do not interfere
with this process at all. The only thing different is when the
user tells pppd he has his own address, pppd will allow him to use
it, if he and his address are authenticated via the pap-secrets file.
The only thing to remember, is tell your static IP users to set the
"correct" IP or they will be assigned the normal dynamic address.
(And of course that's not what we want) :>) If you have any
questions....
While I tested this as many ways as our systems would allow, no warranty
is implied. They work well for us.
Jeff Myers <jmyers@southcom.net>