]>
Commit | Line | Data |
---|---|---|
9113567e | 1 | --- ppp-2.3.5.orig/debian/README.debian Thu Jan 1 01:00:00 1970 |
2 | +++ ppp-2.3.5/debian/README.debian Tue Feb 2 19:07:33 1999 | |
3 | @@ -0,0 +1,145 @@ | |
4 | +PPP for Debian | |
5 | +--------------- | |
6 | + | |
7 | +Upgrading from Previous versions to 2.3.1 and beyond. | |
8 | +-------------------------------- | |
9 | + | |
10 | +The default setup in /etc/ppp/options is to turn authentication on. | |
11 | + | |
12 | +This may cause you not to be able to log into your ISP any more, if they do | |
13 | +not support PAP or CHAP authentication. All you need to do is set ``noauth'' | |
14 | +either on pppd's command line or in /etc/ppp/peers/provider, in order to switch | |
15 | +it off for this connection. | |
16 | + | |
17 | +[Don't just turn it off again in the options file, since it is better to deny | |
18 | + access by default for security reasons.] | |
19 | + | |
20 | +Apparently some people have had problems with /etc/chatscripts not | |
21 | +ending up owned by root.dip. Just run | |
22 | + | |
23 | + chown root.dip /etc/chatscripts | |
24 | + | |
25 | +PAM Support (needed for inbound PAP): | |
26 | +------------------------------------ | |
27 | + | |
28 | +pppd with PAM support for inbound PAP logins is available by installing | |
29 | +ppp-pam, which contains a replacement /usr/sbin/pppd. | |
30 | + | |
31 | +Cheers, Phil. | |
32 | +<phil@hands.com> | |
33 | + | |
34 | +--------- | |
35 | + | |
36 | +This release provides scripts to conveniently control ppp from user space. | |
37 | +Note that the scripts only work with the proper setup in /etc/ppp. Edit | |
38 | +the configuration files and test the operation of your link in superuser | |
39 | +mode first. | |
40 | + | |
41 | +Read the manpage for pon,poff,plog please. | |
42 | + | |
43 | +Available scripts: | |
44 | +------------------ | |
45 | + | |
46 | +pon Bring link up. Executes pppd and will immediately | |
47 | + return the command prompt while still dialing. | |
48 | + use plog to figure out what pppd does. | |
49 | + | |
50 | +poff Bring link down. Kills pppd | |
51 | + | |
52 | +plog shows the last lines of the pppd log. | |
53 | + | |
54 | +Outbound and Inbound Dialing Setup | |
55 | +---------------------------------- | |
56 | +pppd attempts to handle both inbound and outbound through one set of | |
57 | +configuration files. The /etc/ppp/options file has been set up for the most | |
58 | +common setups. Please do not change it if at all possible. Specify | |
59 | +parameters on the commandline if necessary. If you find a change that will | |
60 | +be beneficial to all then please tell me about it. | |
61 | + | |
62 | +Outbound Setup (Simple one server setup!) | |
63 | +-------------- | |
64 | + | |
65 | +Edit the file /etc/chatscripts/provider and make sure it contains what | |
66 | +you need to dialup into your server and eventually start up ppp on the | |
67 | +remote machine. | |
68 | + | |
69 | +Edit the file /etc/ppp/peers/provider and put all options in it that you need | |
70 | +to connect to your server. The most common options are already provided for | |
71 | +you. If you need the common PAP-Password authentication then add | |
72 | +user <username> to it. Otherwise you might also change the system name to be | |
73 | +like your username. The systemname is used for authentication if you do not | |
74 | +provide the "user" directive. See also pppd manpage. | |
75 | + | |
76 | +Note: If you are NOT using pap or chap authentication, you need to put | |
77 | + `noauth' in /etc/ppp/peers/provider to allow a connection to be made. | |
78 | + | |
79 | +Edit the file /etc/ppp/pap-secrets and put your password into the designated | |
80 | +location. | |
81 | + | |
82 | +You should then be able to start the ppp connection with pon. | |
83 | + | |
84 | +If you want to have ppp on bootup then rename the file | |
85 | +/etc/ppp/no_ppp_on_boot to /etc/ppp/ppp_on_boot. | |
86 | + | |
87 | +Inbound Setup (assuming mgetty 0.99 installed) | |
88 | +---------------------------------------------- | |
89 | +Edit the /etc/ppp/options file and uncomment the nameserver lines. Provide | |
90 | +the IP addresses that you want the users to use for their name services. | |
91 | + | |
92 | +Copy the file /etc/ppp/options.XX so that you have one options file | |
93 | +for each serial port you run mgetty on. Give each serial port an IP address | |
94 | +in those files. That way that port is locked into using that IP number. | |
95 | +Think what consequences that assignment might have for outbound use... | |
96 | + | |
97 | +That should be enough for dialup from a Win95 or NT Server. The | |
98 | +username/password on those system is used for a pap-authentication. | |
99 | +The /etc/ppp/pap-secrets is already set up for such a situation. Mgetty is | |
100 | +preconfigured to call pppd with parameters so that the pap-verification will | |
101 | +be done through the /etc/passwd file. | |
102 | + | |
103 | +All your users should now be able to establish ppp connections by just | |
104 | +specifying phone#, username,password from Win95 etc. | |
105 | + | |
106 | +Inbound dialup using dialup Scripts: | |
107 | +A ppp session can be established from the regular Linux prompt by executing | |
108 | +/usr/sbin/pppd. The user is limited to use the assigned IP adddress in | |
109 | +/etc/ppp/options.ttyname and will not be able to override it. | |
110 | + | |
111 | +Permissions: | |
112 | +------------ | |
113 | +Access to PPPD is controlled via the membership in the "dip" group. | |
114 | + | |
115 | +Demand Dialup links: | |
116 | +-------------------- | |
117 | +You need to have the kernel patched in order to support demand dialup with | |
118 | +the patches for ppp 2.3!!!! | |
119 | + | |
120 | +Add the following options to /etc/ppp/peers/provider: | |
121 | + | |
122 | +demand idle 600 holdoff 20 | |
123 | + | |
124 | +to set up demand dialing. 600 seconds (=10 Minutes) idle time disconnects. | |
125 | +20 seconds between attempts to connect. This setup implies the "persist" | |
126 | +option. You might also want to enable ppp on boot up so you wont have to | |
127 | +worry about the ppp connection at all. | |
128 | + | |
129 | +Syslog Facility Level: | |
130 | +---------------------- | |
131 | + | |
132 | +The default level of LOG_DAEMON has been overridden (as described in the | |
133 | +pppd(8) man page), to be LOG_LOCAL2. The intent being thst local2 be sent | |
134 | +to /var/log/ppp.log for use by plog. | |
135 | + | |
136 | +Not implemented: | |
137 | +---------------- | |
138 | +- Password expiration. Was implemented with a direct call to a non-exported | |
139 | + function in libshadow. Why are they doing such things? | |
140 | + | |
141 | +Kernel Update | |
142 | +------------- | |
143 | +As of version 2.3.1 the kernel stuff is broken. See the file | |
144 | + | |
145 | +kernel.fix2.0.30-2 in this directory. | |
146 | + | |
147 | +Christoph Lameter, <clameter@debian.org> 22 July 1997 | |
148 | + | |
149 | --- ppp-2.3.5.orig/debian/ip-down Thu Jan 1 01:00:00 1970 | |
150 | +++ ppp-2.3.5/debian/ip-down Tue Feb 2 19:07:33 1999 | |
151 | @@ -0,0 +1,43 @@ | |
152 | +#!/bin/sh | |
153 | +# | |
154 | +# $Id$ | |
155 | +# | |
156 | +# This script is run by the pppd _after_ the link is brought down. | |
157 | +# It uses run-parts to run scripts in /etc/ppp/ip-down.d, so to delete | |
158 | +# routes, unset IP addresses etc. you should create script(s) there. | |
159 | +# | |
160 | +# Be aware that other packages may include /etc/ppp/ip-down.d scripts (named | |
161 | +# after that package), so choose local script names with that in mind. | |
162 | +# | |
163 | +# This script is called with the following arguments: | |
164 | +# Arg Name Example | |
165 | +# $1 Interface name ppp0 | |
166 | +# $2 The tty ttyS1 | |
167 | +# $3 The link speed 38400 | |
168 | +# $4 Local IP number 12.34.56.78 | |
169 | +# $5 Peer IP number 12.34.56.99 | |
170 | +# $6 Optional ``ipparam'' value foo | |
171 | + | |
172 | +# The environment is cleared before executing this script | |
173 | +# so the path must be reset | |
174 | +PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin | |
175 | +export PATH | |
176 | +# These variables are for the use of the scripts run by run-parts | |
177 | +PPP_IFACE="$1" | |
178 | +PPP_TTY="$2" | |
179 | +PPP_SPEED="$3" | |
180 | +PPP_LOCAL="$4" | |
181 | +PPP_REMOTE="$5" | |
182 | +PPP_IPPARAM="$6" | |
183 | +export PPP_IFACE PPP_TTY PPP_SPEED PPP_LOCAL PPP_REMOTE PPP_IPPARAM | |
184 | + | |
185 | +# as an additional convienince, $PPP_TTYNAME is set to the tty name, | |
186 | +# stripped of /dev/ (if present) for easier matching. | |
187 | +PPP_TTYNAME=`/usr/bin/basename "$2"` | |
188 | +export PPP_TTYNAME | |
189 | + | |
190 | +# Main Script starts here | |
191 | + | |
192 | +run-parts /etc/ppp/ip-down.d | |
193 | + | |
194 | +# last line | |
195 | --- ppp-2.3.5.orig/debian/ip-up Thu Jan 1 01:00:00 1970 | |
196 | +++ ppp-2.3.5/debian/ip-up Tue Feb 2 19:07:33 1999 | |
197 | @@ -0,0 +1,44 @@ | |
198 | +#!/bin/sh | |
199 | +# | |
200 | +# $Id$ | |
201 | +# | |
202 | +# This script is run by the pppd after the link is established. | |
203 | +# It uses run-parts to run scripts in /etc/ppp/ip-up.d, so to add routes, | |
204 | +# set IP address, run the mailq etc. you should create script(s) there. | |
205 | +# | |
206 | +# Be aware that other packages may include /etc/ppp/ip-up.d scripts (named | |
207 | +# after that package), so choose local script names with that in mind. | |
208 | +# | |
209 | +# This script is called with the following arguments: | |
210 | +# Arg Name Example | |
211 | +# $1 Interface name ppp0 | |
212 | +# $2 The tty ttyS1 | |
213 | +# $3 The link speed 38400 | |
214 | +# $4 Local IP number 12.34.56.78 | |
215 | +# $5 Peer IP number 12.34.56.99 | |
216 | +# $6 Optional ``ipparam'' value foo | |
217 | + | |
218 | +# The environment is cleared before executing this script | |
219 | +# so the path must be reset | |
220 | +PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin | |
221 | +export PATH | |
222 | +# These variables are for the use of the scripts run by run-parts | |
223 | +PPP_IFACE="$1" | |
224 | +PPP_TTY="$2" | |
225 | +PPP_SPEED="$3" | |
226 | +PPP_LOCAL="$4" | |
227 | +PPP_REMOTE="$5" | |
228 | +PPP_IPPARAM="$6" | |
229 | +export PPP_IFACE PPP_TTY PPP_SPEED PPP_LOCAL PPP_REMOTE PPP_IPPARAM | |
230 | + | |
231 | + | |
232 | +# as an additional convenience, $PPP_TTYNAME is set to the tty name, | |
233 | +# stripped of /dev/ (if present) for easier matching. | |
234 | +PPP_TTYNAME=`/usr/bin/basename "$2"` | |
235 | +export PPP_TTYNAME | |
236 | + | |
237 | +# Main Script starts here | |
238 | + | |
239 | +run-parts /etc/ppp/ip-up.d | |
240 | + | |
241 | +# last line | |
242 | --- ppp-2.3.5.orig/debian/options Thu Jan 1 01:00:00 1970 | |
243 | +++ ppp-2.3.5/debian/options Tue Feb 2 19:07:33 1999 | |
244 | @@ -0,0 +1,278 @@ | |
245 | +# /etc/ppp/options | |
246 | +# | |
247 | +# $Id$ | |
248 | +# | |
249 | +# Originally created by Jim Knoble <jmknoble@mercury.interpath.net> | |
250 | +# Modified for Debian by alvar Bray <alvar@meiko.co.uk> | |
251 | +# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org> | |
252 | +# | |
253 | +# Use the command egrep -v '#|^ *$' /etc/ppp/options to quickly see what | |
254 | +# options are active in this file. | |
255 | + | |
256 | +# Specify which DNS Servers the incoming Win95 or WinNT Connection should use | |
257 | +# Two Servers can be remotely configured | |
258 | +# ms-dns 192.168.1.1 | |
259 | +# ms-dns 192.168.1.2 | |
260 | + | |
261 | +# Specify which WINS Servers the incoming connection Win95 or WinNT should use | |
262 | +# ms-wins 192.168.1.50 | |
263 | +# ms-wins 192.168.1.51 | |
264 | + | |
265 | +# Run the executable or shell command specified after pppd has | |
266 | +# terminated the link. This script could, for example, issue commands | |
267 | +# to the modem to cause it to hang up if hardware modem control signals | |
268 | +# were not available. | |
269 | +#disconnect "chat -- \d+++\d\c OK ath0 OK" | |
270 | + | |
271 | +# async character map -- 32-bit hex; each bit is a character | |
272 | +# that needs to be escaped for pppd to receive it. 0x00000001 | |
273 | +# represents '\x01', and 0x80000000 represents '\x1f'. | |
274 | +asyncmap 0 | |
275 | + | |
276 | +# Require the peer to authenticate itself before allowing network | |
277 | +# packets to be sent or received. | |
278 | +# Please do not disable this setting. It is expected to be standard in | |
279 | +# future releases of pppd. Use the call option (see manpage) to disable | |
280 | +# authentication for specific peers. | |
281 | +auth | |
282 | + | |
283 | +# Use hardware flow control (i.e. RTS/CTS) to control the flow of data | |
284 | +# on the serial port. | |
285 | +crtscts | |
286 | + | |
287 | +# Use software flow control (i.e. XON/XOFF) to control the flow of data | |
288 | +# on the serial port. | |
289 | +#xonxoff | |
290 | + | |
291 | +# Specifies that certain characters should be escaped on transmission | |
292 | +# (regardless of whether the peer requests them to be escaped with its | |
293 | +# async control character map). The characters to be escaped are | |
294 | +# specified as a list of hex numbers separated by commas. Note that | |
295 | +# almost any character can be specified for the escape option, unlike | |
296 | +# the asyncmap option which only allows control characters to be | |
297 | +# specified. The characters which may not be escaped are those with hex | |
298 | +# values 0x20 - 0x3f or 0x5e. | |
299 | +#escape 11,13,ff | |
300 | + | |
301 | +# Don't use the modem control lines. | |
302 | +#local | |
303 | + | |
304 | +# Specifies that pppd should use a UUCP-style lock on the serial device | |
305 | +# to ensure exclusive access to the device. | |
306 | +lock | |
307 | + | |
308 | +# Use the modem control lines. On Ultrix, this option implies hardware | |
309 | +# flow control, as for the crtscts option. (This option is not fully | |
310 | +# implemented.) | |
311 | +modem | |
312 | + | |
313 | +# Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd | |
314 | +# will ask the peer to send packets of no more than <n> bytes. The | |
315 | +# minimum MRU value is 128. The default MRU value is 1500. A value of | |
316 | +# 296 is recommended for slow links (40 bytes for TCP/IP header + 256 | |
317 | +# bytes of data). | |
318 | +#mru 542 | |
319 | + | |
320 | +# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot" | |
321 | +# notation (e.g. 255.255.255.0). | |
322 | +#netmask 255.255.255.0 | |
323 | + | |
324 | +# Disables the default behaviour when no local IP address is specified, | |
325 | +# which is to determine (if possible) the local IP address from the | |
326 | +# hostname. With this option, the peer will have to supply the local IP | |
327 | +# address during IPCP negotiation (unless it specified explicitly on the | |
328 | +# command line or in an options file). | |
329 | +#noipdefault | |
330 | + | |
331 | +# Enables the "passive" option in the LCP. With this option, pppd will | |
332 | +# attempt to initiate a connection; if no reply is received from the | |
333 | +# peer, pppd will then just wait passively for a valid LCP packet from | |
334 | +# the peer (instead of exiting, as it does without this option). | |
335 | +#passive | |
336 | + | |
337 | +# With this option, pppd will not transmit LCP packets to initiate a | |
338 | +# connection until a valid LCP packet is received from the peer (as for | |
339 | +# the "passive" option with old versions of pppd). | |
340 | +#silent | |
341 | + | |
342 | +# Don't request or allow negotiation of any options for LCP and IPCP | |
343 | +# (use default values). | |
344 | +#-all | |
345 | + | |
346 | +# Disable Address/Control compression negotiation (use default, i.e. | |
347 | +# address/control field disabled). | |
348 | +#-ac | |
349 | + | |
350 | +# Disable asyncmap negotiation (use the default asyncmap, i.e. escape | |
351 | +# all control characters). | |
352 | +#-am | |
353 | + | |
354 | +# Don't fork to become a background process (otherwise pppd will do so | |
355 | +# if a serial device is specified). | |
356 | +#-detach | |
357 | + | |
358 | +# Disable IP address negotiation (with this option, the remote IP | |
359 | +# address must be specified with an option on the command line or in an | |
360 | +# options file). | |
361 | +#-ip | |
362 | + | |
363 | +# Disable magic number negotiation. With this option, pppd cannot | |
364 | +# detect a looped-back line. | |
365 | +#-mn | |
366 | + | |
367 | +# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e. | |
368 | +# 1500). | |
369 | +#-mru | |
370 | + | |
371 | +# Disable protocol field compression negotiation (use default, i.e. | |
372 | +# protocol field compression disabled). | |
373 | +#-pc | |
374 | + | |
375 | +# Require the peer to authenticate itself using PAP. | |
376 | +#+pap | |
377 | + | |
378 | +# Don't agree to authenticate using PAP. | |
379 | +#-pap | |
380 | + | |
381 | +# Require the peer to authenticate itself using CHAP [Cryptographic | |
382 | +# Handshake Authentication Protocol] authentication. | |
383 | +#+chap | |
384 | + | |
385 | +# Don't agree to authenticate using CHAP. | |
386 | +#-chap | |
387 | + | |
388 | +# Disable negotiation of Van Jacobson style IP header compression (use | |
389 | +# default, i.e. no compression). | |
390 | +#-vj | |
391 | + | |
392 | +# Increase debugging level (same as -d). If this option is given, pppd | |
393 | +# will log the contents of all control packets sent or received in a | |
394 | +# readable form. The packets are logged through syslog with facility | |
395 | +# daemon and level debug. This information can be directed to a file by | |
396 | +# setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If | |
397 | +# pppd is compiled with extra debugging enabled, it will log messages | |
398 | +# using facility local2 instead of daemon). | |
399 | +#debug | |
400 | + | |
401 | +# Append the domain name <d> to the local host name for authentication | |
402 | +# purposes. For example, if gethostname() returns the name porsche, | |
403 | +# but the fully qualified domain name is porsche.Quotron.COM, you would | |
404 | +# use the domain option to set the domain name to Quotron.COM. | |
405 | +#domain <d> | |
406 | + | |
407 | +# Enable debugging code in the kernel-level PPP driver. The argument n | |
408 | +# is a number which is the sum of the following values: 1 to enable | |
409 | +# general debug messages, 2 to request that the contents of received | |
410 | +# packets be printed, and 4 to request that the contents of transmitted | |
411 | +# packets be printed. | |
412 | +#kdebug n | |
413 | + | |
414 | +# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer | |
415 | +# requests a smaller value via MRU negotiation, pppd will request that | |
416 | +# the kernel networking code send data packets of no more than n bytes | |
417 | +# through the PPP network interface. | |
418 | +#mtu <n> | |
419 | + | |
420 | +# Enforce the use of the hostname as the name of the local system for | |
421 | +# authentication purposes (overrides the name option). | |
422 | +#usehostname | |
423 | + | |
424 | +# Set the assumed name of the remote system for authentication purposes | |
425 | +# to <n>. | |
426 | +#remotename <n> | |
427 | + | |
428 | +# Add an entry to this system's ARP [Address Resolution Protocol] | |
429 | +# table with the IP address of the peer and the Ethernet address of this | |
430 | +# system. | |
431 | +proxyarp | |
432 | + | |
433 | +# Use the system password database for authenticating the peer using | |
434 | +# PAP. Note: mgetty already provides this option. If this is specified | |
435 | +# then dialin from users using a script under Linux to fire up ppp wont work. | |
436 | +# login | |
437 | + | |
438 | +# If this option is given, pppd will send an LCP echo-request frame to | |
439 | +# the peer every n seconds. Under Linux, the echo-request is sent when | |
440 | +# no packets have been received from the peer for n seconds. Normally | |
441 | +# the peer should respond to the echo-request by sending an echo-reply. | |
442 | +# This option can be used with the lcp-echo-failure option to detect | |
443 | +# that the peer is no longer connected. | |
444 | +lcp-echo-interval 30 | |
445 | + | |
446 | +# If this option is given, pppd will presume the peer to be dead if n | |
447 | +# LCP echo-requests are sent without receiving a valid LCP echo-reply. | |
448 | +# If this happens, pppd will terminate the connection. Use of this | |
449 | +# option requires a non-zero value for the lcp-echo-interval parameter. | |
450 | +# This option can be used to enable pppd to terminate after the physical | |
451 | +# connection has been broken (e.g., the modem has hung up) in | |
452 | +# situations where no hardware modem control lines are available. | |
453 | +lcp-echo-failure 4 | |
454 | + | |
455 | +# Set the LCP restart interval (retransmission timeout) to <n> seconds | |
456 | +# (default 3). | |
457 | +#lcp-restart <n> | |
458 | + | |
459 | +# Set the maximum number of LCP terminate-request transmissions to <n> | |
460 | +# (default 3). | |
461 | +#lcp-max-terminate <n> | |
462 | + | |
463 | +# Set the maximum number of LCP configure-request transmissions to <n> | |
464 | +# (default 10). | |
465 | +#lcp-max-configure <n> | |
466 | + | |
467 | +# Set the maximum number of LCP configure-NAKs returned before starting | |
468 | +# to send configure-Rejects instead to <n> (default 10). | |
469 | +#lcp-max-failure <n> | |
470 | + | |
471 | +# Set the IPCP restart interval (retransmission timeout) to <n> | |
472 | +# seconds (default 3). | |
473 | +#ipcp-restart <n> | |
474 | + | |
475 | +# Set the maximum number of IPCP terminate-request transmissions to <n> | |
476 | +# (default 3). | |
477 | +#ipcp-max-terminate <n> | |
478 | + | |
479 | +# Set the maximum number of IPCP configure-request transmissions to <n> | |
480 | +# (default 10). | |
481 | +#ipcp-max-configure <n> | |
482 | + | |
483 | +# Set the maximum number of IPCP configure-NAKs returned before starting | |
484 | +# to send configure-Rejects instead to <n> (default 10). | |
485 | +#ipcp-max-failure <n> | |
486 | + | |
487 | +# Set the PAP restart interval (retransmission timeout) to <n> seconds | |
488 | +# (default 3). | |
489 | +#pap-restart <n> | |
490 | + | |
491 | +# Set the maximum number of PAP authenticate-request transmissions to | |
492 | +# <n> (default 10). | |
493 | +#pap-max-authreq <n> | |
494 | + | |
495 | +# Set the CHAP restart interval (retransmission timeout for | |
496 | +# challenges) to <n> seconds (default 3). | |
497 | +#chap-restart <n> | |
498 | + | |
499 | +# Set the maximum number of CHAP challenge transmissions to <n> | |
500 | +# (default 10). | |
501 | +#chap-max-challenge | |
502 | + | |
503 | +# If this option is given, pppd will rechallenge the peer every <n> | |
504 | +# seconds. | |
505 | +#chap-interval <n> | |
506 | + | |
507 | +# With this option, pppd will accept the peer's idea of our local IP | |
508 | +# address, even if the local IP address was specified in an option. | |
509 | +#ipcp-accept-local | |
510 | + | |
511 | +# With this option, pppd will accept the peer's idea of its (remote) IP | |
512 | +# address, even if the remote IP address was specified in an option. | |
513 | +#ipcp-accept-remote | |
514 | + | |
515 | +# Disable the IPXCP and IPX protocols. | |
516 | +# To let pppd pass IPX packets comment this out --- you'll probably also | |
517 | +# want to install ipxripd, and have the Internal IPX Network option enabled | |
518 | +# in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info. | |
519 | +noipx | |
520 | + | |
521 | +# ---<End of File>--- | |
522 | + | |
523 | --- ppp-2.3.5.orig/debian/options.ttyXX Thu Jan 1 01:00:00 1970 | |
524 | +++ ppp-2.3.5/debian/options.ttyXX Tue Feb 2 19:07:33 1999 | |
525 | @@ -0,0 +1,19 @@ | |
526 | +# If you need to set up multiple serial lines then copy | |
527 | +# this file to | |
528 | +# options.<ttyname> for each tty with a modem on it. | |
529 | +# | |
530 | +# The options.tty file will assign an IP address to each PPP connection | |
531 | +# as it comes up. They must all be distinct! | |
532 | +# | |
533 | +# Example: | |
534 | +# options.ttyS1 for com2 under DOS. | |
535 | +# | |
536 | +# Edit the following line so that the first IP address | |
537 | +# mentioned is the is the IP address of your host while the second | |
538 | +# is the ip address of the serial port | |
539 | +# | |
540 | +# I usually use the convention hostname + dash + last 2 character of | |
541 | +# the ttyname to refer to serial ports. | |
542 | +# For example servername-s1 for ttyS1 on server "servername" | |
543 | + | |
544 | +hostname:hostname-s1 | |
545 | --- ppp-2.3.5.orig/debian/pap-secrets Thu Jan 1 01:00:00 1970 | |
546 | +++ ppp-2.3.5/debian/pap-secrets Tue Feb 2 19:07:33 1999 | |
547 | @@ -0,0 +1,37 @@ | |
548 | +# This is a pap-secrets file to be used with the AUTO_PPP function of mgetty | |
549 | +# mgetty-0.99 is preconfigured to startup pppd with the login option which | |
550 | +# will cause pppd to consult /etc/passwd after a user has passed this file | |
551 | +# Dont be disturbed therfore by the fact that this file defines logins with | |
552 | +# any password for users. /etc/passwd will catch passwd mismatches. | |
553 | +# | |
554 | +# This file should block ALL users that should not be able to do AUTO_PPP! | |
555 | +# AUTO_PPP bypasses the usual login program so its necessary to list all | |
556 | +# system userids with regular passwords here! | |
557 | +# | |
558 | +# ATTENTION: The definitions here can allow users to login without a | |
559 | +# password if you dont use the login option of pppd! | |
560 | +# The /etc/ppp/options file installed has the login option enabled | |
561 | + | |
562 | +# INBOUND connections | |
563 | + | |
564 | +# Every regular user can use PPP and has to use passwords from /etc/passwd | |
565 | +* hostname "" * | |
566 | + | |
567 | +# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any | |
568 | +# other accounts that should not be able to use pppd! | |
569 | +guest hostname "*" - | |
570 | +master hostname "*" - | |
571 | +root hostname "*" - | |
572 | +support hostname "*" - | |
573 | +stats hostname "*" - | |
574 | + | |
575 | +# OUTBOUND connections | |
576 | + | |
577 | +# Here you should add your userid password to connect to your providers via | |
578 | +# pap. The * means that the password is to be used for ANY host you connect | |
579 | +# to. Thus you do not have to worry about the foreign machine name. Just | |
580 | +# replace password with your password. | |
581 | +# If you have different providers with different passwords then you better | |
582 | +# remove the following line. | |
583 | + | |
584 | +hostname * password | |
585 | --- ppp-2.3.5.orig/debian/plog Thu Jan 1 01:00:00 1970 | |
586 | +++ ppp-2.3.5/debian/plog Tue Feb 2 19:07:33 1999 | |
587 | @@ -0,0 +1,2 @@ | |
588 | +#!/bin/sh | |
589 | +tail $* /var/log/ppp.log | |
590 | --- ppp-2.3.5.orig/debian/plog.1 Thu Jan 1 01:00:00 1970 | |
591 | +++ ppp-2.3.5/debian/plog.1 Tue Feb 2 19:07:33 1999 | |
592 | @@ -0,0 +1 @@ | |
593 | +.so pon.1 | |
594 | --- ppp-2.3.5.orig/debian/poff Thu Jan 1 01:00:00 1970 | |
595 | +++ ppp-2.3.5/debian/poff Tue Feb 2 19:07:33 1999 | |
596 | @@ -0,0 +1,53 @@ | |
597 | +#!/bin/sh | |
598 | + | |
599 | +# $Id$ | |
600 | +# Written by Phil Hands <phil@hands.com>, distributed under the GNU GPL | |
601 | + | |
602 | +SIG=TERM DONE=stopped; | |
603 | + | |
604 | +getopts rdch FLAG | |
605 | +case $FLAG in | |
606 | + "r") SIG=HUP DONE=signalled; shift ;; | |
607 | + "d") SIG=USR1 DONE=signalled; shift ;; | |
608 | + "c") SIG=USR2 DONE=signalled; shift ;; | |
609 | + "h") cat <<!EOF! | |
610 | +usage: $0 [options] [provider] | |
611 | + | |
612 | +options: | |
613 | + -r cause pppd to drop the line and redial | |
614 | + -d toggles the state of pppd's debug option | |
615 | + -c cause pppd to renegotiate compression | |
616 | + -h this help summary | |
617 | +!EOF! | |
618 | + exit 1 | |
619 | + ;; | |
620 | +esac | |
621 | + | |
622 | +PROVIDER=$1 | |
623 | + | |
624 | + | |
625 | +# Lets see how many pppds are running.... | |
626 | +set -- `cat /var/run/ppp*.pid 2>/dev/null` | |
627 | + | |
628 | +case $# in | |
629 | + 0) # pppd only creates a pid file once ppp is up, so let's try killing pppd | |
630 | + # on the assumption that we've not got that far yet. | |
631 | + kill -${SIG} `ps axw | egrep "pppd call [[:alnum:]]+" | grep -v grep | awk '{print $1}'` | |
632 | + exit 0 | |
633 | + ;; | |
634 | + 1) # If only one was running then it can be killed using the pid | |
635 | + kill -${SIG} $1 | |
636 | + exit 0 | |
637 | + ;; | |
638 | + *) # More than one! Aieehh.. We have to use ps to figure it out. | |
639 | + # If no arguments were specified, then assume the 'provider' default. | |
640 | + PID=`ps axw | egrep "pppd call ${PROVIDER:-provider}[[:space:]]*\$" | grep -v grep | awk '{print $1}'` | |
641 | + if [ $PID ]; then | |
642 | + kill -${SIG} ${PID} | |
643 | + exit 0 | |
644 | + else | |
645 | + echo "I could not find a pppd process or provider '${PROVIDER:-provider}'. None ${DONE}" | |
646 | + exit 1 | |
647 | + fi | |
648 | + ;; | |
649 | +esac | |
650 | --- ppp-2.3.5.orig/debian/poff.1 Thu Jan 1 01:00:00 1970 | |
651 | +++ ppp-2.3.5/debian/poff.1 Tue Feb 2 19:07:33 1999 | |
652 | @@ -0,0 +1 @@ | |
653 | +.so pon.1 | |
654 | --- ppp-2.3.5.orig/debian/pon Thu Jan 1 01:00:00 1970 | |
655 | +++ ppp-2.3.5/debian/pon Tue Feb 2 19:07:33 1999 | |
656 | @@ -0,0 +1,2 @@ | |
657 | +#!/bin/sh | |
658 | +/usr/sbin/pppd call ${1:-provider} | |
659 | --- ppp-2.3.5.orig/debian/pon.1 Thu Jan 1 01:00:00 1970 | |
660 | +++ ppp-2.3.5/debian/pon.1 Tue Feb 2 19:07:33 1999 | |
661 | @@ -0,0 +1,44 @@ | |
662 | +.Id $Id$ | |
663 | +.TH PLOG 1 "Oct 1996" local "Linux Programmer's Manual" | |
664 | +.SH NAME | |
665 | +pon, poff, plog \- startup, shutdown, or list the log of the PPP connection. | |
666 | +.SH SYNOPSIS | |
667 | +.B pon | |
668 | +.br | |
669 | +.B poff | |
670 | +.br | |
671 | +.B plog | |
672 | +.SH DESCRIPTION | |
673 | +.B pon | |
674 | +and | |
675 | +.B poff | |
676 | +switch the ppp connection on and off. Progress and logged events related to | |
677 | +the ppp connection can be viewed using | |
678 | +.B plog | |
679 | +.SH REQUIREMENTS FOR the p-commands to work | |
680 | +.TP 8 | |
681 | +.B /etc/ppp/chatscripts/provider | |
682 | +must contain the correct chatscript to connect to your provider. All users | |
683 | +that are supposed to be able to use the p-commands should have read access | |
684 | +to this file. | |
685 | +.br | |
686 | +.TP 8 | |
687 | +.B /etc/ppp/options | |
688 | +contains the options for ppp to connect to your provider. This file also | |
689 | +must be readable by all users who should be able to use the p-commands. | |
690 | +.SH FILES | |
691 | +.I /etc/ppp/chatscripts/provider | |
692 | +.br | |
693 | +.I /etc/ppp/peers/provider | |
694 | +.br | |
695 | +.I /etc/ppp/options | |
696 | +.br | |
697 | +.I /var/log/ppp.log | |
698 | +.br | |
699 | +.I /etc/ppp/pap-secrets | |
700 | +.br | |
701 | +.I /etc/ppp/chap-secrets | |
702 | +.SH SEE ALSO | |
703 | +pppd(8), chat(8), and the documentation in /usr/doc/ppp | |
704 | +.SH AUTHOR | |
705 | +The p-commands were written by Christoph Lameter <clameter@debian.org> | |
706 | --- ppp-2.3.5.orig/debian/ppp-2.3.0.STATIC.README Thu Jan 1 01:00:00 1970 | |
707 | +++ ppp-2.3.5/debian/ppp-2.3.0.STATIC.README Tue Feb 2 19:07:33 1999 | |
708 | @@ -0,0 +1,54 @@ | |
709 | + | |
710 | +ppp-2.3.0-static.diff | |
711 | + | |
712 | + Patch to ppp-2.3.0 to support using static IP addresses with | |
713 | + Mgetty and AutoPPP. Does not affect normal dynamic assignments. | |
714 | + This patch is for 2.3.0 only and not very well tested, comments | |
715 | + welcome. Apply with "patch -p1" in the top directory of the | |
716 | + ppp-2.3.0 sources. After getting ppp-2.3.0 to compile cleanly on | |
717 | + your system, patch and re-compile. (No need to re-compile kernel) | |
718 | + While the patches should work with any authentication method, we | |
719 | + did not have success getting 2.3.0 to work with USE_PAM=1 option. | |
720 | + (Out of the box). We use shadow passwords and "make HAS_SHADOW=1". | |
721 | + Bottom line...you should get ppp-2.3.0 working BEFORE you apply | |
722 | + the patches. | |
723 | + | |
724 | + After patching and re-compiling, update the pap-secrets file to | |
725 | + contain the entries of those users you want to have static | |
726 | + IP addresses. Typical entry might look like: | |
727 | + | |
728 | + #client server secret IP addresses | |
729 | + jdoe * realpswd 207.69.189.15 | |
730 | + * * "" * | |
731 | + | |
732 | + Also, inform your static IP users to include their IP when | |
733 | + connecting. ex: pppd 207.69.189.15: | |
734 | + Or for Windows folks "check" Specify an IP address. | |
735 | + | |
736 | + Note: The second line is what most folks will use to authenticate | |
737 | + users who will be dynamically assigned their addresses by | |
738 | + /dev/ttyXX. This along with the login option allows users to | |
739 | + be PAP authenticated against the /etc/passwd or /etc/shadow. | |
740 | + If you enter each and every user into your pap-secrets file | |
741 | + and do not have the last line,(wildcards line) you MUST place | |
742 | + a "*" at the end of each users line. Without it authentication | |
743 | + will fail. For example: | |
744 | + | |
745 | + #client server secret IP addresses | |
746 | + jdoe * passwd 207.69.189.15 * | |
747 | + | |
748 | + This "*" at the end allows the patches to work properly without | |
749 | + changing the normal process. The IP address is normally assigned | |
750 | + via the /etc/ppp/options.ttyXX file. The patches do not interfere | |
751 | + with this process at all. The only thing different is when the | |
752 | + user tells pppd he has his own address, pppd will allow him to use | |
753 | + it, if he and his address are authenticated via the pap-secrets file. | |
754 | + The only thing to remember, is tell your static IP users to set the | |
755 | + "correct" IP or they will be assigned the normal dynamic address. | |
756 | + (And of course that's not what we want) :>) If you have any | |
757 | + questions.... | |
758 | + | |
759 | +While I tested this as many ways as our systems would allow, no warranty | |
760 | +is implied. They work well for us. | |
761 | + | |
762 | +Jeff Myers <jmyers@southcom.net> | |
763 | --- ppp-2.3.5.orig/debian/provider Thu Jan 1 01:00:00 1970 | |
764 | +++ ppp-2.3.5/debian/provider Tue Feb 2 19:59:00 1999 | |
765 | @@ -0,0 +1,21 @@ | |
766 | +# These are the options to dial out to your service provider | |
767 | +# Please customize them correctly. Only the "provider" file will | |
768 | +# be handled by poff and pon. | |
769 | + | |
770 | +# You usually need this if there is no PAP authentication | |
771 | +noauth | |
772 | + | |
773 | +# The chatscript (be sure to edit that file too) | |
774 | +connect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/provider" | |
775 | + | |
776 | +# Routing | |
777 | +defaultroute | |
778 | + | |
779 | +# Default Modem (you better replace this with /dev/ttySx!) | |
780 | +/dev/modem | |
781 | + | |
782 | +# Speed | |
783 | +38400 | |
784 | + | |
785 | +# Keep Modem up even if connection fails | |
786 | +persist | |
787 | --- ppp-2.3.5.orig/debian/provider.chatscript Thu Jan 1 01:00:00 1970 | |
788 | +++ ppp-2.3.5/debian/provider.chatscript Tue Feb 2 19:07:33 1999 | |
789 | @@ -0,0 +1,7 @@ | |
790 | +ABORT BUSY | |
791 | +ABORT "NO CARRIER" | |
792 | +ABORT VOICE | |
793 | +ABORT "NO DIALTONE" | |
794 | +"" ATDT<edit phone number here> | |
795 | +ogin <put login name here> | |
796 | +word \q<put password here> | |
797 | --- ppp-2.3.5.orig/debian/win95.ppp Thu Jan 1 01:00:00 1970 | |
798 | +++ ppp-2.3.5/debian/win95.ppp Tue Feb 2 19:07:33 1999 | |
799 | @@ -0,0 +1,42 @@ | |
800 | +Short Guide on How to run a Win95 Connection with PPPD to Debian Linux | |
801 | +---------------------------------------------------------------------- | |
802 | + | |
803 | +1. Do not mess around with the Win95 configuration. | |
804 | + Do not manually configure DNS, Scripts etc. | |
805 | + Do not switch on the terminal windows. | |
806 | + Accept all defaults or better leave it as | |
807 | + it was at installation. | |
808 | + | |
809 | +2. You need to have a getty program that supports | |
810 | + automatic PPP protocol detection such as mgetty-0.99 | |
811 | + | |
812 | + You also need to have a pppd that supports remote DNS configuration. | |
813 | + The ppp usually coming with Debian has these options since ppp-2.2.0f-4 | |
814 | + | |
815 | + Without the extended ppp you still have to configure the DNS Server | |
816 | + on the Win95 wanting to connect to your Debian Linux Box. | |
817 | + | |
818 | +3. Configure PPP on Debian | |
819 | + A) Change the dns lines in /etc/ppp/options and review the | |
820 | + complete file for things you need to do. | |
821 | + | |
822 | + B) Make sure that your /etc/ppp/pap-secrets file is set | |
823 | + up correctly. It should allow your users in /etc/passwd | |
824 | + to establish ppp connections without a password. pppd will | |
825 | + check against /etc/passwd too! | |
826 | + The pap-secrets installed by this package is set up correctly | |
827 | + to handle user logins via pap. | |
828 | + If you are having trouble with authentication then remove | |
829 | + /etc/ppp/pap-secrets completely and it will usually work. | |
830 | + | |
831 | +4. Win95 PPP Dialup | |
832 | + Click on Dialup-Connection | |
833 | + A. Enter phone number of your linux server | |
834 | + B. Enter username when prompted | |
835 | + C. Enter password when prompted | |
836 | + | |
837 | +Win95 should connect to your Linux PPPD without problems and automatically | |
838 | +configure all IP-Addresses, Netmasks and DNS Servers. You can immediately | |
839 | +start Netscape, Internet Explorer or any other TCP/IP tools. | |
840 | + | |
841 | +Christoph Lameter, September 27, 1996 (clameter@debian.org) |