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 && HDLC
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 && HDLC
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 && HDLC
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 clock source you will need lmcctl.
82 It is available at <ftp://ftp.lanmedia.com/> (broken link).
84 To compile this driver as a module, choose M here: the
85 module will be called lmc.
87 # There is no way to detect a Sealevel board. Force it modular
89 tristate "Sealevel Systems 4021 support"
90 depends on ISA && m && ISA_DMA_API && INET && HDLC
92 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
94 The driver will be compiled as a module: the
95 module will be called sealevel.
99 tristate "Generic HDLC layer"
101 Say Y to this option if your Linux box contains a WAN (Wide Area
102 Network) card supported by this driver and you are planning to
103 connect the box to a WAN.
105 You will need supporting software from
106 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
107 Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
108 Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
110 To compile this driver as a module, choose M here: the
111 module will be called hdlc.
116 tristate "Raw HDLC support"
119 Generic HDLC driver supporting raw HDLC over WAN connections.
124 tristate "Raw HDLC Ethernet device support"
127 Generic HDLC driver supporting raw HDLC Ethernet device emulation
128 over WAN connections.
130 You will need it for Ethernet over HDLC bridges.
135 tristate "Cisco HDLC support"
138 Generic HDLC driver supporting Cisco HDLC over WAN connections.
143 tristate "Frame Relay support"
146 Generic HDLC driver supporting Frame Relay over WAN connections.
151 tristate "Synchronous Point-to-Point Protocol (PPP) support"
154 Generic HDLC driver supporting PPP over WAN connections.
159 tristate "X.25 protocol support"
160 depends on HDLC && (LAPB=m && HDLC=m || LAPB=y)
162 Generic HDLC driver supporting X.25 over WAN connections.
166 comment "X.25/LAPB support is disabled"
167 depends on HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y
170 tristate "Goramo PCI200SYN support"
171 depends on HDLC && PCI
173 Driver for PCI200SYN cards by Goramo sp. j.
175 If you have such a card, say Y here and see
176 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
178 To compile this as a module, choose M here: the
179 module will be called pci200syn.
184 tristate "SBE Inc. wanXL support"
185 depends on HDLC && PCI
187 Driver for wanXL PCI cards by SBE Inc.
189 If you have such a card, say Y here and see
190 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
192 To compile this as a module, choose M here: the
193 module will be called wanxl.
197 config WANXL_BUILD_FIRMWARE
198 bool "rebuild wanXL firmware"
199 depends on WANXL && !PREVENT_FIRMWARE_BUILD
201 Allows you to rebuild firmware run by the QUICC processor.
202 It requires as68k, ld68k and hexdump programs.
204 You should never need this option, say N.
207 tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)"
208 depends on HDLC && PCI && BROKEN
210 This driver is broken because of struct tty_driver change.
212 Driver for the Cyclades-PC300 synchronous communication boards.
214 These boards provide synchronous serial interfaces to your
215 Linux box (interfaces currently available are RS-232/V.35, X.21 and
216 T1/E1). If you wish to support Multilink PPP, please select the
217 option later and read the file README.mlppp provided by PC300
220 To compile this as a module, choose M here: the module
221 will be called pc300.
226 bool "Cyclades-PC300 MLPPP support"
227 depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP
229 Multilink PPP over the PC300 synchronous communication boards.
231 comment "Cyclades-PC300 MLPPP support is disabled."
232 depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
234 comment "Refer to the file README.mlppp, provided by PC300 package."
235 depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
238 tristate "Cyclades PC300 RSV/X21 alternative support"
239 depends on HDLC && PCI
241 Alternative driver for PC300 RSV/X21 PCI cards made by
242 Cyclades, Inc. If you have such a card, say Y here and see
243 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
245 To compile this as a module, choose M here: the module
246 will be called pc300too.
248 If unsure, say N here.
251 tristate "SDL RISCom/N2 support"
252 depends on HDLC && ISA
254 Driver for RISCom/N2 single or dual channel ISA cards by
255 SDL Communications Inc.
257 If you have such a card, say Y here and see
258 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
260 Note that N2csu and N2dds cards are not supported by this driver.
262 To compile this driver as a module, choose M here: the module
268 tristate "Moxa C101 support"
269 depends on HDLC && ISA
271 Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd.
273 If you have such a card, say Y here and see
274 <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
276 To compile this driver as a module, choose M here: the
277 module will be called c101.
282 tristate "FarSync T-Series support"
283 depends on HDLC && PCI
285 Support for the FarSync T-Series X.21 (and V.35/V.24) cards by
286 FarSite Communications Ltd.
288 Synchronous communication is supported on all ports at speeds up to
289 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC,
290 Frame Relay or X.25/LAPB.
292 If you want the module to be automatically loaded when the interface
293 is referenced then you should add "alias hdlcX farsync" to
294 /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or
295 simply use "alias hdlc* farsync" to indicate all of them.
297 To compile this driver as a module, choose M here: the
298 module will be called farsync.
301 tristate "Etinc PCISYNC serial board support"
302 depends on HDLC && PCI && m
304 Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens)
307 This is supposed to work with the four port card. Take a look at
308 <http://www.cogenit.fr/dscc4/> for further information about the
311 To compile this driver as a module, choose M here: the
312 module will be called dscc4.
315 bool "Etinc PCISYNC features"
318 Due to Etinc's design choice for its PCISYNC cards, some operations
319 are only allowed on specific ports of the DSCC4. This option is the
320 only way for the driver to know that it shouldn't return a success
321 code for these operations.
323 Please say Y if your card is an Etinc's PCISYNC.
326 bool "Hard reset support"
329 Various DSCC4 bugs forbid any reliable software reset of the ASIC.
330 As a replacement, some vendors provide a way to assert the PCI #RST
331 pin of DSCC4 through the GPIO port of the card. If you choose Y,
332 the driver will make use of this feature before module removal
333 (i.e. rmmod). The feature is known to be available on Commtech's
334 cards. Contact your manufacturer for details.
336 Say Y if your card supports this feature.
339 tristate "Intel IXP4xx HSS (synchronous serial port) support"
340 depends on HDLC && ARM && ARCH_IXP4XX && IXP4XX_NPE && IXP4XX_QMGR
342 Say Y here if you want to use built-in HSS ports
346 tristate "Frame Relay DLCI support"
348 Support for the Frame Relay protocol.
350 Frame Relay is a fast low-cost way to connect to a remote Internet
351 access provider or to form a private wide area network. The one
352 physical line from your box to the local "switch" (i.e. the entry
353 point to the Frame Relay network, usually at the phone company) can
354 carry several logical point-to-point connections to other computers
355 connected to the Frame Relay network. For a general explanation of
356 the protocol, check out <http://www.mplsforum.org/>.
358 To use frame relay, you need supporting hardware (called FRAD) and
359 certain programs from the net-tools package as explained in
360 <file:Documentation/networking/framerelay.txt>.
362 To compile this driver as a module, choose M here: the
363 module will be called dlci.
366 int "Max DLCI per device"
370 How many logical point-to-point frame relay connections (the
371 identifiers of which are called DCLIs) should be handled by each
372 of your hardware frame relay access devices.
377 tristate "SDLA (Sangoma S502/S508) support"
378 depends on DLCI && ISA
380 Driver for the Sangoma S502A, S502E, and S508 Frame Relay Access
383 These are multi-protocol cards, but only Frame Relay is supported
384 by the driver at this time. Please read
385 <file:Documentation/networking/framerelay.txt>.
387 To compile this driver as a module, choose M here: the
388 module will be called sdla.
391 config WAN_ROUTER_DRIVERS
392 tristate "WAN router drivers"
393 depends on WAN_ROUTER
395 Connect LAN to WAN via Linux box.
397 Select driver your card and remember to say Y to "Wan Router."
398 You will need the wan-tools package which is available from
399 <ftp://ftp.sangoma.com/>.
401 Note that the answer to this question won't directly affect the
402 kernel except for how subordinate drivers may be built:
403 saying N will just cause the configurator to skip all
404 the questions about WAN router drivers.
409 tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)"
410 depends on WAN_ROUTER_DRIVERS && (PCI || ISA)
412 Cyclom 2X from Cyclades Corporation <http://www.avocent.com/> is an
413 intelligent multiprotocol WAN adapter with data transfer rates up to
414 512 Kbps. These cards support the X.25 and SNA related protocols.
416 While no documentation is available at this time please grab the
418 <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
419 to make it compile with the current wanrouter include files; efforts
420 are being made to use the original package available at
421 <ftp://ftp.sangoma.com/>).
423 Feel free to contact me or the cycsyn-devel mailing list at
424 <acme@conectiva.com.br> and <cycsyn-devel@bazar.conectiva.com.br> for
425 additional details, I hope to have documentation available as soon as
426 possible. (Cyclades Brazil is writing the Documentation).
428 The next questions will ask you about the protocols you want the
429 driver to support (for now only X.25 is supported).
431 If you have one or more of these cards, say Y to this option.
433 To compile this driver as a module, choose M here: the
434 module will be called cyclomx.
437 bool "Cyclom 2X X.25 support (EXPERIMENTAL)"
438 depends on CYCLADES_SYNC
440 Connect a Cyclom 2X card to an X.25 network.
442 Enabling X.25 support will enlarge your kernel by about 11 kB.
444 # X.25 network drivers
446 tristate "LAPB over Ethernet driver (EXPERIMENTAL)"
447 depends on LAPB && X25
449 Driver for a pseudo device (typically called /dev/lapb0) which allows
450 you to open an LAPB point-to-point connection to some other computer
451 on your Ethernet network.
453 In order to do this, you need to say Y or M to the driver for your
454 Ethernet card as well as to "LAPB Data Link Driver".
456 To compile this driver as a module, choose M here: the
457 module will be called lapbether.
462 tristate "X.25 async driver (EXPERIMENTAL)"
463 depends on LAPB && X25
465 Send and receive X.25 frames over regular asynchronous serial
466 lines such as telephone lines equipped with ordinary modems.
468 Experts should note that this driver doesn't currently comply with
469 the asynchronous HDLS framing protocols in CCITT recommendation X.25.
471 To compile this driver as a module, choose M here: the
472 module will be called x25_asy.
477 tristate "Granch SBNI12 Leased Line adapter support"
480 Driver for ISA SBNI12-xx cards which are low cost alternatives to
483 You can find more information and last versions of drivers and
484 utilities at <http://www.granch.ru/>. If you have any question you
485 can send email to <sbni@granch.ru>.
487 To compile this driver as a module, choose M here: the
488 module will be called sbni.
492 config SBNI_MULTILINE
493 bool "Multiple line feature support"
496 Schedule traffic for some parallel lines, via SBNI12 adapters.
498 If you have two computers connected with two parallel lines it's
499 possible to increase transfer rate nearly twice. You should have
500 a program named 'sbniconfig' to configure adapters.