blob: 91a38edf8ae4cb4efab4597ba66c6fac6a6b1bbd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
#########################################################################
#
# Example of ppp.linkup file
#
#
# This file is checked when PPP establishes a connection.
# PPP searches the labels in this file as follows:
#
# 1) The label that matches the IP number assigned to our side.
#
# 2) The label specified on the command line to ppp.
#
# 3) If no label has been found, use MYADDR if it exists.
#
# $Id: ppp.linkup.sample,v 1.8 1997/08/25 01:07:08 brian Exp $
#
#########################################################################
# If we've got 192.244.176.32 as our address, then regard peer as a gateway
# to 192.244.176.0 network.
#
192.244.176.32:
add 192.244.176.0 0 HISADDR
# If we are invoked with an argument ``iij-demand'', then delete all
# existing route entries and add the peer as the default gateway.
#
iij-demand:
delete ALL
add 0 0 HISADDR
# Otherwise, simply add peer as default gateway.
#
MYADDR:
delete 0
add 0 0 HISADDR
# If we are invoked with an argument ``pmdemand'', then
# delete all existing (wrong) routing entries and add the peer IP
# as our default gateway.
# This is vital if you don't already know either sides IP number.
#
# We create a loopback route to ourselves so that we can "ping"
# our side of the connection
#
# We also want to execute a script on startup. This script can do
# nice things such as kick off "sendmail -q", "popclient my.isp" and
# "slurp -d news". It can be passed MYADDR, HISADDR and INTERFACE
# too - useful for informing a DNS.
#
pmdemand:
delete ALL
add 0 0 HISADDR
add MYADDR 255.255.255.255 127.0.0.1
!bg /etc/ppp/ppp.etherup.pmdemand
|
