# SPDX-License-Identifier: GPL-2.0-only # # [31mCONFIG_SLIP[0m network device configuration # config [31mCONFIG_SLIP[0m tristate "SLIP (serial line) support" depends on [31mCONFIG_TTY[0m ---help--- Say Y if you intend to use [31mCONFIG_SLIP[0m or CSLIP (compressed [31mCONFIG_SLIP[0m) to connect to your Internet service provider or to connect to some other local Unix box or if you want to configure your Linux box as a Slip/CSlip server for other people to dial in. [31mCONFIG_SLIP[0m (Serial Line Internet Protocol) is a protocol used to send Internet traffic over serial connections such as telephone lines or null modem cables; nowadays, the protocol [31mCONFIG_PPP[0m is more commonly used for this same purpose. Normally, your access provider has to support [31mCONFIG_SLIP[0m in order for you to be able to use it, but there is now a [31mCONFIG_SLIP[0m emulator called SLiRP around (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use [31mCONFIG_SLIP[0m over a regular dial up shell connection. If you plan to use SLiRP, make sure to say Y to CSLIP, below. The [31mCONFIG_NET[0m-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>, explains how to configure [31mCONFIG_SLIP[0m. Note that you don't need this option if you just want to run term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP support will enlarge your kernel by about 4 KB. If unsure, say N. To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will be called slip. config [31mCONFIG_SLHC[0m tristate ---help--- This option enables Van Jacobsen serial line header compression routines. if [31mCONFIG_SLIP[0m config [31mCONFIG_SLIP_COMPRESSED[0m bool "CSLIP compressed headers" depends on [31mCONFIG_SLIP[0m select [31mCONFIG_SLHC[0m ---help--- This protocol is faster than [31mCONFIG_SLIP[0m because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain [31mCONFIG_SLIP[0m. If you plan to use SLiRP, the [31mCONFIG_SLIP[0m emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use [31mCONFIG_SLIP[0m over a regular dial up shell connection, you definitely want to say Y here. The [31mCONFIG_NET[0m-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>, explains how to configure CSLIP. This won't enlarge your kernel. config [31mCONFIG_SLIP_SMART[0m bool "Keepalive and linefill" depends on [31mCONFIG_SLIP[0m ---help--- Adds additional capabilities to the [31mCONFIG_SLIP[0m driver to support the RELCOM line fill and keepalive monitoring. Ideal on poor quality analogue lines. config [31mCONFIG_SLIP_MODE_SLIP6[0m bool "Six bit SLIP encapsulation" depends on [31mCONFIG_SLIP[0m ---help--- Just occasionally you may need to run IP over hostile serial networks that don't pass all control characters or are only seven bit. Saying Y here adds an extra mode you can use with [31mCONFIG_SLIP[0m: "slip6". In this mode, [31mCONFIG_SLIP[0m will only send normal ASCII symbols over the serial device. Naturally, this has to be supported at the other end of the link as well. It's good enough, for example, to run IP over the async ports of a Camtec JNT Pad. If unsure, say N. endif # [31mCONFIG_SLIP[0m |