2 # wan devices configuration
6 bool "Wan interfaces support"
8 Wide Area Networks (WANs), such as X.25, Frame Relay and leased
9 lines, are used to interconnect Local Area Networks (LANs) over vast
10 distances with data transfer rates significantly higher than those
11 achievable with commonly used asynchronous modem connections.
13 Usually, a quite expensive external device called a `WAN router' is
14 needed to connect to a WAN. As an alternative, a relatively
15 inexpensive WAN interface card can allow your Linux box to directly
18 If you have one of those cards and wish to use it under Linux,
19 say Y here and also to the WAN driver for your card.
25 # There is no way to detect a comtrol sv11 - force it modular for now.
27 tristate "Comtrol Hostess SV-11 support"
28 depends on ISA && m && ISA_DMA_API && INET
30 Driver for Comtrol Hostess SV-11 network card which
31 operates on low speed synchronous serial links at up to
32 256Kbps, supporting PPP and Cisco HDLC.
34 The driver will be compiled as a module: the
35 module will be called hostess_sv11.
37 # The COSA/SRP driver has not been tested as non-modular yet.
39 tristate "COSA/SRP sync serial boards support"
40 depends on ISA && m && ISA_DMA_API
42 Driver for COSA and SRP synchronous serial boards.
44 These boards allow to connect synchronous serial devices (for example
45 base-band modems, or any other device with the X.21, V.24, V.35 or
46 V.36 interface) to your Linux box. The cards can work as the
47 character device, synchronous PPP network device, or the Cisco HDLC
50 You will need user-space utilities COSA or SRP boards for downloading
51 the firmware to the cards and to set them up. Look at the
52 <http://www.fi.muni.cz/~kas/cosa/> for more information. You can also
53 read the comment at the top of the <file:drivers/net/wan/cosa.c> for
54 details about the cards and the driver itself.
56 The driver will be compiled as a module: the
57 module will be called cosa.
60 # Lan Media's board. Currently 1000, 1200, 5200, 5245
63 tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards"
64 depends on PCI && VIRT_TO_BUS
66 Driver for the following Lan Media family of serial boards:
68 - LMC 1000 board allows you to connect synchronous serial devices
69 (for example base-band modems, or any other device with the X.21,
70 V.24, V.35 or V.36 interface) to your Linux box.
72 - LMC 1200 with on board DSU board allows you to connect your Linux
73 box directly to a T1 or E1 circuit.
75 - LMC 5200 board provides a HSSI interface capable of running up to
78 - LMC 5245 board connects directly to a T3 circuit saving the
79 additional external hardware.
81 To change setting such as syncPPP vs Cisco HDLC or clock source you
82 will need lmcctl. It is available at <ftp://ftp.lanmedia.com/>
85 To compile this driver as a module, choose M here: the
86 module will be called lmc.
88 # There is no way to detect a Sealevel board. Force it modular
90 tristate "Sealevel Systems 4021 support"
91 depends on ISA && m && ISA_DMA_API && INET
93 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
95 The driver will be compiled as a module: the
96 module will be called sealevel.
100 tristate "Generic HDLC layer"
102 Say Y to this option if your Linux box contains a WAN (Wide Area
103 Network) card supported by this driver and you are planning to
104 connect the box to a WAN.
106 You will need supporting software from
107 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
108 Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
109 Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
111 To compile this driver as a module, choose M here: the
112 module will be called hdlc.
117 tristate "Raw HDLC support"
120 Generic HDLC driver supporting raw HDLC over WAN connections.
125 tristate "Raw HDLC Ethernet device support"
128 Generic HDLC driver supporting raw HDLC Ethernet device emulation
129 over WAN connections.
131 You will need it for Ethernet over HDLC bridges.
136 tristate "Cisco HDLC support"
139 Generic HDLC driver supporting Cisco HDLC over WAN connections.
144 tristate "Frame Relay support"
147 Generic HDLC driver supporting Frame Relay over WAN connections.
152 tristate "Synchronous Point-to-Point Protocol (PPP) support"
155 Generic HDLC driver supporting PPP over WAN connections.
160 tristate "X.25 protocol support"
161 depends on HDLC && (LAPB=m && HDLC=m || LAPB=y)
163 Generic HDLC driver supporting X.25 over WAN connections.
167 comment "X.25/LAPB support is disabled"
168 depends on HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y
171 tristate "Goramo PCI200SYN support"
172 depends on HDLC && PCI
174 Driver for PCI200SYN cards by Goramo sp. j.
176 If you have such a card, say Y here and see
177 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
179 To compile this as a module, choose M here: the
180 module will be called pci200syn.
185 tristate "SBE Inc. wanXL support"
186 depends on HDLC && PCI
188 Driver for wanXL PCI cards by SBE Inc.
190 If you have such a card, say Y here and see
191 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
193 To compile this as a module, choose M here: the
194 module will be called wanxl.
198 config WANXL_BUILD_FIRMWARE
199 bool "rebuild wanXL firmware"
200 depends on WANXL && !PREVENT_FIRMWARE_BUILD
202 Allows you to rebuild firmware run by the QUICC processor.
203 It requires as68k, ld68k and hexdump programs.
205 You should never need this option, say N.
208 tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)"
209 depends on HDLC && PCI
211 Driver for the Cyclades-PC300 synchronous communication boards.
213 These boards provide synchronous serial interfaces to your
214 Linux box (interfaces currently available are RS-232/V.35, X.21 and
215 T1/E1). If you wish to support Multilink PPP, please select the
216 option later and read the file README.mlppp provided by PC300
219 To compile this as a module, choose M here: the module
220 will be called pc300.
225 bool "Cyclades-PC300 MLPPP support"
226 depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP
228 Multilink PPP over the PC300 synchronous communication boards.
230 comment "Cyclades-PC300 MLPPP support is disabled."
231 depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
233 comment "Refer to the file README.mlppp, provided by PC300 package."
234 depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
237 tristate "Cyclades PC300 RSV/X21 alternative support"
238 depends on HDLC && PCI
240 Alternative driver for PC300 RSV/X21 PCI cards made by
241 Cyclades, Inc. If you have such a card, say Y here and see
242 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
244 To compile this as a module, choose M here: the module
245 will be called pc300too.
247 If unsure, say N here.
250 tristate "SDL RISCom/N2 support"
251 depends on HDLC && ISA
253 Driver for RISCom/N2 single or dual channel ISA cards by
254 SDL Communications Inc.
256 If you have such a card, say Y here and see
257 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
259 Note that N2csu and N2dds cards are not supported by this driver.
261 To compile this driver as a module, choose M here: the module
267 tristate "Moxa C101 support"
268 depends on HDLC && ISA
270 Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd.
272 If you have such a card, say Y here and see
273 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
275 To compile this driver as a module, choose M here: the
276 module will be called c101.
281 tristate "FarSync T-Series support"
282 depends on HDLC && PCI
284 Support for the FarSync T-Series X.21 (and V.35/V.24) cards by
285 FarSite Communications Ltd.
287 Synchronous communication is supported on all ports at speeds up to
288 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC,
289 Frame Relay or X.25/LAPB.
291 If you want the module to be automatically loaded when the interface
292 is referenced then you should add "alias hdlcX farsync" to
293 /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or
294 simply use "alias hdlc* farsync" to indicate all of them.
296 To compile this driver as a module, choose M here: the
297 module will be called farsync.
300 tristate "Etinc PCISYNC serial board support"
301 depends on HDLC && PCI && m
303 Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens)
306 This is supposed to work with the four port card. Take a look at
307 <http://www.cogenit.fr/dscc4/> for further information about the
310 To compile this driver as a module, choose M here: the
311 module will be called dscc4.
314 bool "Etinc PCISYNC features"
317 Due to Etinc's design choice for its PCISYNC cards, some operations
318 are only allowed on specific ports of the DSCC4. This option is the
319 only way for the driver to know that it shouldn't return a success
320 code for these operations.
322 Please say Y if your card is an Etinc's PCISYNC.
325 bool "Hard reset support"
328 Various DSCC4 bugs forbid any reliable software reset of the ASIC.
329 As a replacement, some vendors provide a way to assert the PCI #RST
330 pin of DSCC4 through the GPIO port of the card. If you choose Y,
331 the driver will make use of this feature before module removal
332 (i.e. rmmod). The feature is known to be available on Commtech's
333 cards. Contact your manufacturer for details.
335 Say Y if your card supports this feature.
338 tristate "Frame Relay DLCI support"
340 Support for the Frame Relay protocol.
342 Frame Relay is a fast low-cost way to connect to a remote Internet
343 access provider or to form a private wide area network. The one
344 physical line from your box to the local "switch" (i.e. the entry
345 point to the Frame Relay network, usually at the phone company) can
346 carry several logical point-to-point connections to other computers
347 connected to the Frame Relay network. For a general explanation of
348 the protocol, check out <http://www.mplsforum.org/>.
350 To use frame relay, you need supporting hardware (called FRAD) and
351 certain programs from the net-tools package as explained in
352 <file:Documentation/networking/framerelay.txt>.
354 To compile this driver as a module, choose M here: the
355 module will be called dlci.
358 int "Max DLCI per device"
362 How many logical point-to-point frame relay connections (the
363 identifiers of which are called DCLIs) should be handled by each
364 of your hardware frame relay access devices.
369 tristate "SDLA (Sangoma S502/S508) support"
370 depends on DLCI && ISA
372 Driver for the Sangoma S502A, S502E, and S508 Frame Relay Access
375 These are multi-protocol cards, but only Frame Relay is supported
376 by the driver at this time. Please read
377 <file:Documentation/networking/framerelay.txt>.
379 To compile this driver as a module, choose M here: the
380 module will be called sdla.
383 config WAN_ROUTER_DRIVERS
384 tristate "WAN router drivers"
385 depends on WAN_ROUTER
387 Connect LAN to WAN via Linux box.
389 Select driver your card and remember to say Y to "Wan Router."
390 You will need the wan-tools package which is available from
391 <ftp://ftp.sangoma.com/>. For more information read:
392 <file:Documentation/networking/wan-router.txt>.
394 Note that the answer to this question won't directly affect the
395 kernel except for how subordinate drivers may be built:
396 saying N will just cause the configurator to skip all
397 the questions about WAN router drivers.
402 tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)"
403 depends on WAN_ROUTER_DRIVERS && (PCI || ISA)
405 Cyclom 2X from Cyclades Corporation <http://www.cyclades.com/> is an
406 intelligent multiprotocol WAN adapter with data transfer rates up to
407 512 Kbps. These cards support the X.25 and SNA related protocols.
409 While no documentation is available at this time please grab the
411 <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
412 to make it compile with the current wanrouter include files; efforts
413 are being made to use the original package available at
414 <ftp://ftp.sangoma.com/>).
416 Feel free to contact me or the cycsyn-devel mailing list at
417 <acme@conectiva.com.br> and <cycsyn-devel@bazar.conectiva.com.br> for
418 additional details, I hope to have documentation available as soon as
419 possible. (Cyclades Brazil is writing the Documentation).
421 The next questions will ask you about the protocols you want the
422 driver to support (for now only X.25 is supported).
424 If you have one or more of these cards, say Y to this option.
426 To compile this driver as a module, choose M here: the
427 module will be called cyclomx.
430 bool "Cyclom 2X X.25 support (EXPERIMENTAL)"
431 depends on CYCLADES_SYNC
433 Connect a Cyclom 2X card to an X.25 network.
435 Enabling X.25 support will enlarge your kernel by about 11 kB.
437 # X.25 network drivers
439 tristate "LAPB over Ethernet driver (EXPERIMENTAL)"
440 depends on LAPB && X25
442 Driver for a pseudo device (typically called /dev/lapb0) which allows
443 you to open an LAPB point-to-point connection to some other computer
444 on your Ethernet network.
446 In order to do this, you need to say Y or M to the driver for your
447 Ethernet card as well as to "LAPB Data Link Driver".
449 To compile this driver as a module, choose M here: the
450 module will be called lapbether.
455 tristate "X.25 async driver (EXPERIMENTAL)"
456 depends on LAPB && X25
458 Send and receive X.25 frames over regular asynchronous serial
459 lines such as telephone lines equipped with ordinary modems.
461 Experts should note that this driver doesn't currently comply with
462 the asynchronous HDLS framing protocols in CCITT recommendation X.25.
464 To compile this driver as a module, choose M here: the
465 module will be called x25_asy.
470 tristate "Granch SBNI12 Leased Line adapter support"
473 Driver for ISA SBNI12-xx cards which are low cost alternatives to
476 You can find more information and last versions of drivers and
477 utilities at <http://www.granch.ru/>. If you have any question you
478 can send email to <sbni@granch.ru>.
480 To compile this driver as a module, choose M here: the
481 module will be called sbni.
485 config SBNI_MULTILINE
486 bool "Multiple line feature support"
489 Schedule traffic for some parallel lines, via SBNI12 adapters.
491 If you have two computers connected with two parallel lines it's
492 possible to increase transfer rate nearly twice. You should have
493 a program named 'sbniconfig' to configure adapters.