2 # PPP network device configuration
6 tristate "PPP (point-to-point protocol) support"
9 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
10 the same purpose: sending Internet traffic over telephone (and other
11 serial) lines. Ask your access provider if they support it, because
12 otherwise you can't use it; most Internet access providers these
13 days support PPP rather than SLIP.
15 To use PPP, you need an additional program called pppd as described
16 in the PPP-HOWTO, available at
17 <http://www.tldp.org/docs.html#howto>. Make sure that you have
18 the version of pppd recommended in <file:Documentation/Changes>.
19 The PPP option enlarges your kernel by about 16 KB.
21 There are actually two versions of PPP: the traditional PPP for
22 asynchronous lines, such as regular analog phone lines, and
23 synchronous PPP which can be used over digital ISDN lines for
24 example. If you want to use PPP over phone lines or other
25 asynchronous serial lines, you need to say Y (or M) here and also to
26 the next option, "PPP support for async serial ports". For PPP over
27 synchronous lines, you should say Y (or M) here and to "Support
28 synchronous PPP", below.
30 If you said Y to "Version information on all symbols" above, then
31 you cannot compile the PPP driver into the kernel; you can then only
32 compile it as a module. To compile this driver as a module, choose M
33 here. The module will be called ppp_generic.
38 tristate "PPP BSD-Compress compression"
41 Support for the BSD-Compress compression method for PPP, which uses
42 the LZW compression method to compress each PPP packet before it is
43 sent over the wire. The machine at the other end of the PPP link
44 (usually your ISP) has to support the BSD-Compress compression
45 method as well for this to be useful. Even if they don't support it,
46 it is safe to say Y here.
48 The PPP Deflate compression method ("PPP Deflate compression",
49 above) is preferable to BSD-Compress, because it compresses better
52 Note that the BSD compression code will always be compiled as a
53 module; it is called bsd_comp and will show up in the directory
54 modules once you have said "make modules". If unsure, say N.
57 tristate "PPP Deflate compression"
62 Support for the Deflate compression method for PPP, which uses the
63 Deflate algorithm (the same algorithm that gzip uses) to compress
64 each PPP packet before it is sent over the wire. The machine at the
65 other end of the PPP link (usually your ISP) has to support the
66 Deflate compression method as well for this to be useful. Even if
67 they don't support it, it is safe to say Y here.
69 To compile this driver as a module, choose M here.
75 Say Y here if you want to be able to filter the packets passing over
76 PPP interfaces. This allows you to control which packets count as
77 activity (i.e. which packets will reset the idle timer or bring up
78 a demand-dialed link) and which packets are to be dropped entirely.
79 You need to say Y here if you wish to use the pass-filter and
80 active-filter options to pppd.
85 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
86 depends on PPP && EXPERIMENTAL
92 Support for the MPPE Encryption protocol, as employed by the
93 Microsoft Point-to-Point Tunneling Protocol.
95 See http://pptpclient.sourceforge.net/ for information on
96 configuring PPTP clients and servers to utilize this method.
99 bool "PPP multilink support (EXPERIMENTAL)"
100 depends on PPP && EXPERIMENTAL
102 PPP multilink is a protocol (defined in RFC 1990) which allows you
103 to combine several (logical or physical) lines into one logical PPP
104 connection, so that you can utilize your full bandwidth.
106 This has to be supported at the other end as well and you need a
107 version of the pppd daemon which understands the multilink protocol.
112 tristate "PPP over ATM"
113 depends on ATM && PPP
115 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
116 This implementation does not yet comply with section 8 of RFC2364,
117 which can lead to bad results if the ATM peer loses state and
118 changes its encapsulation unilaterally.
121 tristate "PPP over Ethernet (EXPERIMENTAL)"
122 depends on EXPERIMENTAL && PPP
124 Support for PPP over Ethernet.
126 This driver requires the latest version of pppd from the CVS
127 repository at cvs.samba.org. Alternatively, see the
128 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
129 which contains instruction on how to use this driver (under
130 the heading "Kernel mode PPPoE").
133 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
134 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
136 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
138 This driver requires pppd plugin to work in client mode or
139 modified pptpd (poptop) to work in server mode.
140 See http://accel-pptp.sourceforge.net/ for information how to
144 tristate "PPP over L2TP (EXPERIMENTAL)"
145 depends on EXPERIMENTAL && L2TP && PPP
147 Support for PPP-over-L2TP socket family. L2TP is a protocol
148 used by ISPs and enterprises to tunnel PPP traffic over UDP
149 tunnels. L2TP is replacing PPTP for VPN uses.
152 tristate "PPP support for async serial ports"
156 Say Y (or M) here if you want to be able to use PPP over standard
157 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
158 a modem (not a synchronous or ISDN modem) to contact your ISP, you
161 To compile this driver as a module, choose M here.
166 tristate "PPP support for sync tty ports"
169 Say Y (or M) here if you want to be able to use PPP over synchronous
170 (HDLC) tty devices, such as the SyncLink adapter. These devices
171 are often used for high-speed leased lines like T1/E1.
173 To compile this driver as a module, choose M here.