Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # wan devices configuration | |
3 | # | |
4 | ||
5 | menu "Wan interfaces" | |
6 | depends on NETDEVICES | |
7 | ||
8 | config WAN | |
9 | bool "Wan interfaces support" | |
10 | ---help--- | |
11 | Wide Area Networks (WANs), such as X.25, Frame Relay and leased | |
12 | lines, are used to interconnect Local Area Networks (LANs) over vast | |
13 | distances with data transfer rates significantly higher than those | |
14 | achievable with commonly used asynchronous modem connections. | |
15 | ||
16 | Usually, a quite expensive external device called a `WAN router' is | |
17 | needed to connect to a WAN. As an alternative, a relatively | |
18 | inexpensive WAN interface card can allow your Linux box to directly | |
19 | connect to a WAN. | |
20 | ||
21 | If you have one of those cards and wish to use it under Linux, | |
22 | say Y here and also to the WAN driver for your card. | |
23 | ||
24 | If unsure, say N. | |
25 | ||
26 | # There is no way to detect a comtrol sv11 - force it modular for now. | |
27 | config HOSTESS_SV11 | |
28 | tristate "Comtrol Hostess SV-11 support" | |
a5532606 | 29 | depends on WAN && ISA && m && ISA_DMA_API |
1da177e4 LT |
30 | help |
31 | Driver for Comtrol Hostess SV-11 network card which | |
32 | operates on low speed synchronous serial links at up to | |
33 | 256Kbps, supporting PPP and Cisco HDLC. | |
34 | ||
35 | The driver will be compiled as a module: the | |
36 | module will be called hostess_sv11. | |
37 | ||
38 | # The COSA/SRP driver has not been tested as non-modular yet. | |
39 | config COSA | |
40 | tristate "COSA/SRP sync serial boards support" | |
a5532606 | 41 | depends on WAN && ISA && m && ISA_DMA_API |
1da177e4 LT |
42 | ---help--- |
43 | Driver for COSA and SRP synchronous serial boards. | |
44 | ||
45 | These boards allow to connect synchronous serial devices (for example | |
46 | base-band modems, or any other device with the X.21, V.24, V.35 or | |
47 | V.36 interface) to your Linux box. The cards can work as the | |
48 | character device, synchronous PPP network device, or the Cisco HDLC | |
49 | network device. | |
50 | ||
51 | You will need user-space utilities COSA or SRP boards for downloading | |
52 | the firmware to the cards and to set them up. Look at the | |
53 | <http://www.fi.muni.cz/~kas/cosa/> for more information. You can also | |
54 | read the comment at the top of the <file:drivers/net/wan/cosa.c> for | |
55 | details about the cards and the driver itself. | |
56 | ||
57 | The driver will be compiled as a module: the | |
58 | module will be called cosa. | |
59 | ||
1da177e4 LT |
60 | # |
61 | # Lan Media's board. Currently 1000, 1200, 5200, 5245 | |
62 | # | |
63 | config LANMEDIA | |
64 | tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards" | |
65 | depends on WAN && PCI | |
66 | ---help--- | |
67 | Driver for the following Lan Media family of serial boards: | |
68 | ||
69 | - LMC 1000 board allows you to connect synchronous serial devices | |
70 | (for example base-band modems, or any other device with the X.21, | |
71 | V.24, V.35 or V.36 interface) to your Linux box. | |
72 | ||
73 | - LMC 1200 with on board DSU board allows you to connect your Linux | |
74 | box directly to a T1 or E1 circuit. | |
75 | ||
76 | - LMC 5200 board provides a HSSI interface capable of running up to | |
77 | 52 Mbits per second. | |
78 | ||
79 | - LMC 5245 board connects directly to a T3 circuit saving the | |
80 | additional external hardware. | |
81 | ||
82 | To change setting such as syncPPP vs Cisco HDLC or clock source you | |
83 | will need lmcctl. It is available at <ftp://ftp.lanmedia.com/> | |
84 | (broken link). | |
85 | ||
86 | To compile this driver as a module, choose M here: the | |
87 | module will be called lmc. | |
88 | ||
89 | # There is no way to detect a Sealevel board. Force it modular | |
90 | config SEALEVEL_4021 | |
91 | tristate "Sealevel Systems 4021 support" | |
d458fd82 | 92 | depends on WAN && ISA && m && ISA_DMA_API && INET |
1da177e4 LT |
93 | help |
94 | This is a driver for the Sealevel Systems ACB 56 serial I/O adapter. | |
95 | ||
96 | The driver will be compiled as a module: the | |
97 | module will be called sealevel. | |
98 | ||
1da177e4 LT |
99 | # Generic HDLC |
100 | config HDLC | |
101 | tristate "Generic HDLC layer" | |
102 | depends on WAN | |
103 | help | |
104 | Say Y to this option if your Linux box contains a WAN (Wide Area | |
105 | Network) card supported by this driver and you are planning to | |
106 | connect the box to a WAN. | |
107 | ||
108 | You will need supporting software from | |
109 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
110 | Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame | |
111 | Relay, synchronous Point-to-Point Protocol (PPP) and X.25. | |
112 | ||
113 | To compile this driver as a module, choose M here: the | |
114 | module will be called hdlc. | |
115 | ||
116 | If unsure, say N. | |
117 | ||
118 | config HDLC_RAW | |
eb2a2fd9 | 119 | tristate "Raw HDLC support" |
1da177e4 LT |
120 | depends on HDLC |
121 | help | |
122 | Generic HDLC driver supporting raw HDLC over WAN connections. | |
123 | ||
124 | If unsure, say N. | |
125 | ||
126 | config HDLC_RAW_ETH | |
eb2a2fd9 | 127 | tristate "Raw HDLC Ethernet device support" |
1da177e4 LT |
128 | depends on HDLC |
129 | help | |
130 | Generic HDLC driver supporting raw HDLC Ethernet device emulation | |
131 | over WAN connections. | |
132 | ||
133 | You will need it for Ethernet over HDLC bridges. | |
134 | ||
135 | If unsure, say N. | |
136 | ||
137 | config HDLC_CISCO | |
eb2a2fd9 | 138 | tristate "Cisco HDLC support" |
1da177e4 LT |
139 | depends on HDLC |
140 | help | |
141 | Generic HDLC driver supporting Cisco HDLC over WAN connections. | |
142 | ||
143 | If unsure, say N. | |
144 | ||
145 | config HDLC_FR | |
eb2a2fd9 | 146 | tristate "Frame Relay support" |
1da177e4 LT |
147 | depends on HDLC |
148 | help | |
149 | Generic HDLC driver supporting Frame Relay over WAN connections. | |
150 | ||
151 | If unsure, say N. | |
152 | ||
153 | config HDLC_PPP | |
eb2a2fd9 | 154 | tristate "Synchronous Point-to-Point Protocol (PPP) support" |
1da177e4 LT |
155 | depends on HDLC |
156 | help | |
157 | Generic HDLC driver supporting PPP over WAN connections. | |
158 | ||
159 | If unsure, say N. | |
160 | ||
161 | config HDLC_X25 | |
eb2a2fd9 | 162 | tristate "X.25 protocol support" |
1da177e4 LT |
163 | depends on HDLC && (LAPB=m && HDLC=m || LAPB=y) |
164 | help | |
165 | Generic HDLC driver supporting X.25 over WAN connections. | |
166 | ||
167 | If unsure, say N. | |
168 | ||
169 | comment "X.25/LAPB support is disabled" | |
170 | depends on WAN && HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y | |
171 | ||
172 | config PCI200SYN | |
173 | tristate "Goramo PCI200SYN support" | |
174 | depends on HDLC && PCI | |
175 | help | |
176 | Driver for PCI200SYN cards by Goramo sp. j. | |
177 | ||
178 | If you have such a card, say Y here and see | |
179 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
180 | ||
181 | To compile this as a module, choose M here: the | |
182 | module will be called pci200syn. | |
183 | ||
184 | If unsure, say N. | |
185 | ||
186 | config WANXL | |
187 | tristate "SBE Inc. wanXL support" | |
188 | depends on HDLC && PCI | |
189 | help | |
190 | Driver for wanXL PCI cards by SBE Inc. | |
191 | ||
192 | If you have such a card, say Y here and see | |
193 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
194 | ||
195 | To compile this as a module, choose M here: the | |
196 | module will be called wanxl. | |
197 | ||
198 | If unsure, say N. | |
199 | ||
200 | config WANXL_BUILD_FIRMWARE | |
201 | bool "rebuild wanXL firmware" | |
202 | depends on WANXL && !PREVENT_FIRMWARE_BUILD | |
203 | help | |
204 | Allows you to rebuild firmware run by the QUICC processor. | |
205 | It requires as68k, ld68k and hexdump programs. | |
206 | ||
207 | You should never need this option, say N. | |
208 | ||
209 | config PC300 | |
210 | tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)" | |
211 | depends on HDLC && PCI | |
212 | ---help--- | |
213 | Driver for the Cyclades-PC300 synchronous communication boards. | |
214 | ||
215 | These boards provide synchronous serial interfaces to your | |
216 | Linux box (interfaces currently available are RS-232/V.35, X.21 and | |
217 | T1/E1). If you wish to support Multilink PPP, please select the | |
218 | option later and read the file README.mlppp provided by PC300 | |
219 | package. | |
220 | ||
221 | To compile this as a module, choose M here: the module | |
222 | will be called pc300. | |
223 | ||
224 | If unsure, say N. | |
225 | ||
226 | config PC300_MLPPP | |
227 | bool "Cyclades-PC300 MLPPP support" | |
228 | depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP | |
229 | help | |
230 | Multilink PPP over the PC300 synchronous communication boards. | |
231 | ||
232 | comment "Cyclades-PC300 MLPPP support is disabled." | |
233 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | |
234 | ||
235 | comment "Refer to the file README.mlppp, provided by PC300 package." | |
236 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | |
237 | ||
238 | config N2 | |
239 | tristate "SDL RISCom/N2 support" | |
240 | depends on HDLC && ISA | |
241 | help | |
242 | Driver for RISCom/N2 single or dual channel ISA cards by | |
243 | SDL Communications Inc. | |
244 | ||
245 | If you have such a card, say Y here and see | |
246 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
247 | ||
248 | Note that N2csu and N2dds cards are not supported by this driver. | |
249 | ||
250 | To compile this driver as a module, choose M here: the module | |
251 | will be called n2. | |
252 | ||
253 | If unsure, say N. | |
254 | ||
255 | config C101 | |
256 | tristate "Moxa C101 support" | |
257 | depends on HDLC && ISA | |
258 | help | |
259 | Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd. | |
260 | ||
261 | If you have such a card, say Y here and see | |
262 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
263 | ||
264 | To compile this driver as a module, choose M here: the | |
265 | module will be called c101. | |
266 | ||
267 | If unsure, say N. | |
268 | ||
269 | config FARSYNC | |
270 | tristate "FarSync T-Series support" | |
271 | depends on HDLC && PCI | |
272 | ---help--- | |
273 | Support for the FarSync T-Series X.21 (and V.35/V.24) cards by | |
274 | FarSite Communications Ltd. | |
275 | ||
276 | Synchronous communication is supported on all ports at speeds up to | |
277 | 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC, | |
278 | Frame Relay or X.25/LAPB. | |
279 | ||
280 | If you want the module to be automatically loaded when the interface | |
281 | is referenced then you should add "alias hdlcX farsync" to | |
282 | /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or | |
283 | simply use "alias hdlc* farsync" to indicate all of them. | |
284 | ||
285 | To compile this driver as a module, choose M here: the | |
286 | module will be called farsync. | |
287 | ||
b690bdef KH |
288 | config DSCC4 |
289 | tristate "Etinc PCISYNC serial board support" | |
290 | depends on HDLC && PCI && m | |
291 | help | |
292 | Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens) | |
293 | DSCC4 chipset. | |
294 | ||
295 | This is supposed to work with the four port card. Take a look at | |
296 | <http://www.cogenit.fr/dscc4/> for further information about the | |
297 | driver. | |
298 | ||
299 | To compile this driver as a module, choose M here: the | |
300 | module will be called dscc4. | |
301 | ||
302 | config DSCC4_PCISYNC | |
303 | bool "Etinc PCISYNC features" | |
304 | depends on DSCC4 | |
305 | help | |
306 | Due to Etinc's design choice for its PCISYNC cards, some operations | |
307 | are only allowed on specific ports of the DSCC4. This option is the | |
308 | only way for the driver to know that it shouldn't return a success | |
309 | code for these operations. | |
310 | ||
311 | Please say Y if your card is an Etinc's PCISYNC. | |
312 | ||
313 | config DSCC4_PCI_RST | |
314 | bool "Hard reset support" | |
315 | depends on DSCC4 | |
316 | help | |
317 | Various DSCC4 bugs forbid any reliable software reset of the ASIC. | |
318 | As a replacement, some vendors provide a way to assert the PCI #RST | |
319 | pin of DSCC4 through the GPIO port of the card. If you choose Y, | |
320 | the driver will make use of this feature before module removal | |
321 | (i.e. rmmod). The feature is known to be available on Commtech's | |
322 | cards. Contact your manufacturer for details. | |
323 | ||
324 | Say Y if your card supports this feature. | |
325 | ||
1da177e4 LT |
326 | config DLCI |
327 | tristate "Frame Relay DLCI support" | |
328 | depends on WAN | |
329 | ---help--- | |
330 | Support for the Frame Relay protocol. | |
331 | ||
332 | Frame Relay is a fast low-cost way to connect to a remote Internet | |
333 | access provider or to form a private wide area network. The one | |
334 | physical line from your box to the local "switch" (i.e. the entry | |
335 | point to the Frame Relay network, usually at the phone company) can | |
336 | carry several logical point-to-point connections to other computers | |
337 | connected to the Frame Relay network. For a general explanation of | |
338 | the protocol, check out <http://www.mplsforum.org/>. | |
339 | ||
340 | To use frame relay, you need supporting hardware (called FRAD) and | |
341 | certain programs from the net-tools package as explained in | |
342 | <file:Documentation/networking/framerelay.txt>. | |
343 | ||
344 | To compile this driver as a module, choose M here: the | |
345 | module will be called dlci. | |
346 | ||
347 | config DLCI_COUNT | |
348 | int "Max open DLCI" | |
349 | depends on DLCI | |
350 | default "24" | |
351 | help | |
352 | Maximal number of logical point-to-point frame relay connections | |
353 | (the identifiers of which are called DCLIs) that the driver can | |
354 | handle. | |
355 | ||
356 | The default is probably fine. | |
357 | ||
358 | config DLCI_MAX | |
359 | int "Max DLCI per device" | |
360 | depends on DLCI | |
361 | default "8" | |
362 | help | |
363 | How many logical point-to-point frame relay connections (the | |
364 | identifiers of which are called DCLIs) should be handled by each | |
365 | of your hardware frame relay access devices. | |
366 | ||
367 | Go with the default. | |
368 | ||
369 | config SDLA | |
370 | tristate "SDLA (Sangoma S502/S508) support" | |
371 | depends on DLCI && ISA | |
372 | help | |
373 | Driver for the Sangoma S502A, S502E, and S508 Frame Relay Access | |
374 | Devices. | |
375 | ||
376 | These are multi-protocol cards, but only Frame Relay is supported | |
377 | by the driver at this time. Please read | |
378 | <file:Documentation/networking/framerelay.txt>. | |
379 | ||
380 | To compile this driver as a module, choose M here: the | |
381 | module will be called sdla. | |
382 | ||
383 | # Wan router core. | |
384 | config WAN_ROUTER_DRIVERS | |
ed407717 | 385 | tristate "WAN router drivers" |
1da177e4 LT |
386 | depends on WAN && WAN_ROUTER |
387 | ---help--- | |
388 | Connect LAN to WAN via Linux box. | |
389 | ||
390 | Select driver your card and remember to say Y to "Wan Router." | |
391 | You will need the wan-tools package which is available from | |
392 | <ftp://ftp.sangoma.com/>. For more information read: | |
393 | <file:Documentation/networking/wan-router.txt>. | |
394 | ||
395 | Note that the answer to this question won't directly affect the | |
ed407717 RD |
396 | kernel except for how subordinate drivers may be built: |
397 | saying N will just cause the configurator to skip all | |
1da177e4 LT |
398 | the questions about WAN router drivers. |
399 | ||
400 | If unsure, say N. | |
401 | ||
1da177e4 LT |
402 | config CYCLADES_SYNC |
403 | tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)" | |
404 | depends on WAN_ROUTER_DRIVERS && (PCI || ISA) | |
405 | ---help--- | |
406 | Cyclom 2X from Cyclades Corporation <http://www.cyclades.com/> is an | |
407 | intelligent multiprotocol WAN adapter with data transfer rates up to | |
408 | 512 Kbps. These cards support the X.25 and SNA related protocols. | |
409 | ||
410 | While no documentation is available at this time please grab the | |
411 | wanconfig tarball in | |
412 | <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes | |
413 | to make it compile with the current wanrouter include files; efforts | |
414 | are being made to use the original package available at | |
415 | <ftp://ftp.sangoma.com/>). | |
416 | ||
417 | Feel free to contact me or the cycsyn-devel mailing list at | |
418 | <acme@conectiva.com.br> and <cycsyn-devel@bazar.conectiva.com.br> for | |
419 | additional details, I hope to have documentation available as soon as | |
420 | possible. (Cyclades Brazil is writing the Documentation). | |
421 | ||
422 | The next questions will ask you about the protocols you want the | |
423 | driver to support (for now only X.25 is supported). | |
424 | ||
425 | If you have one or more of these cards, say Y to this option. | |
426 | ||
427 | To compile this driver as a module, choose M here: the | |
428 | module will be called cyclomx. | |
429 | ||
430 | config CYCLOMX_X25 | |
431 | bool "Cyclom 2X X.25 support (EXPERIMENTAL)" | |
432 | depends on CYCLADES_SYNC | |
433 | help | |
434 | Connect a Cyclom 2X card to an X.25 network. | |
435 | ||
436 | Enabling X.25 support will enlarge your kernel by about 11 kB. | |
437 | ||
438 | # X.25 network drivers | |
439 | config LAPBETHER | |
440 | tristate "LAPB over Ethernet driver (EXPERIMENTAL)" | |
441 | depends on WAN && LAPB && X25 | |
442 | ---help--- | |
443 | Driver for a pseudo device (typically called /dev/lapb0) which allows | |
444 | you to open an LAPB point-to-point connection to some other computer | |
445 | on your Ethernet network. | |
446 | ||
447 | In order to do this, you need to say Y or M to the driver for your | |
448 | Ethernet card as well as to "LAPB Data Link Driver". | |
449 | ||
450 | To compile this driver as a module, choose M here: the | |
451 | module will be called lapbether. | |
452 | ||
453 | If unsure, say N. | |
454 | ||
455 | config X25_ASY | |
456 | tristate "X.25 async driver (EXPERIMENTAL)" | |
457 | depends on WAN && LAPB && X25 | |
458 | ---help--- | |
459 | Send and receive X.25 frames over regular asynchronous serial | |
460 | lines such as telephone lines equipped with ordinary modems. | |
461 | ||
462 | Experts should note that this driver doesn't currently comply with | |
463 | the asynchronous HDLS framing protocols in CCITT recommendation X.25. | |
464 | ||
465 | To compile this driver as a module, choose M here: the | |
466 | module will be called x25_asy. | |
467 | ||
468 | If unsure, say N. | |
469 | ||
470 | config SBNI | |
471 | tristate "Granch SBNI12 Leased Line adapter support" | |
472 | depends on WAN && X86 | |
473 | ---help--- | |
474 | Driver for ISA SBNI12-xx cards which are low cost alternatives to | |
475 | leased line modems. | |
476 | ||
477 | You can find more information and last versions of drivers and | |
478 | utilities at <http://www.granch.ru/>. If you have any question you | |
479 | can send email to <sbni@granch.ru>. | |
480 | ||
481 | To compile this driver as a module, choose M here: the | |
482 | module will be called sbni. | |
483 | ||
484 | If unsure, say N. | |
485 | ||
486 | config SBNI_MULTILINE | |
487 | bool "Multiple line feature support" | |
488 | depends on SBNI | |
489 | help | |
490 | Schedule traffic for some parallel lines, via SBNI12 adapters. | |
491 | ||
492 | If you have two computers connected with two parallel lines it's | |
493 | possible to increase transfer rate nearly twice. You should have | |
494 | a program named 'sbniconfig' to configure adapters. | |
495 | ||
496 | If unsure, say N. | |
497 | ||
498 | endmenu | |
499 |