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 | ||
60 | config DSCC4 | |
61 | tristate "Etinc PCISYNC serial board support" | |
62 | depends on WAN && PCI && m | |
63 | help | |
64 | Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens) | |
65 | DSCC4 chipset. | |
66 | ||
67 | This is supposed to work with the four port card. Take a look at | |
68 | <http://www.cogenit.fr/dscc4/> for further information about the | |
69 | driver. | |
70 | ||
71 | To compile this driver as a module, choose M here: the | |
72 | module will be called dscc4. | |
73 | ||
74 | config DSCC4_PCISYNC | |
75 | bool "Etinc PCISYNC features" | |
76 | depends on DSCC4 | |
77 | help | |
78 | Due to Etinc's design choice for its PCISYNC cards, some operations | |
79 | are only allowed on specific ports of the DSCC4. This option is the | |
80 | only way for the driver to know that it shouldn't return a success | |
81 | code for these operations. | |
82 | ||
83 | Please say Y if your card is an Etinc's PCISYNC. | |
84 | ||
85 | config DSCC4_PCI_RST | |
86 | bool "Hard reset support" | |
87 | depends on DSCC4 | |
88 | help | |
89 | Various DSCC4 bugs forbid any reliable software reset of the ASIC. | |
90 | As a replacement, some vendors provide a way to assert the PCI #RST | |
91 | pin of DSCC4 through the GPIO port of the card. If you choose Y, | |
92 | the driver will make use of this feature before module removal | |
93 | (i.e. rmmod). The feature is known to be available on Commtech's | |
94 | cards. Contact your manufacturer for details. | |
95 | ||
96 | Say Y if your card supports this feature. | |
97 | ||
98 | # | |
99 | # Lan Media's board. Currently 1000, 1200, 5200, 5245 | |
100 | # | |
101 | config LANMEDIA | |
102 | tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards" | |
103 | depends on WAN && PCI | |
104 | ---help--- | |
105 | Driver for the following Lan Media family of serial boards: | |
106 | ||
107 | - LMC 1000 board allows you to connect synchronous serial devices | |
108 | (for example base-band modems, or any other device with the X.21, | |
109 | V.24, V.35 or V.36 interface) to your Linux box. | |
110 | ||
111 | - LMC 1200 with on board DSU board allows you to connect your Linux | |
112 | box directly to a T1 or E1 circuit. | |
113 | ||
114 | - LMC 5200 board provides a HSSI interface capable of running up to | |
115 | 52 Mbits per second. | |
116 | ||
117 | - LMC 5245 board connects directly to a T3 circuit saving the | |
118 | additional external hardware. | |
119 | ||
120 | To change setting such as syncPPP vs Cisco HDLC or clock source you | |
121 | will need lmcctl. It is available at <ftp://ftp.lanmedia.com/> | |
122 | (broken link). | |
123 | ||
124 | To compile this driver as a module, choose M here: the | |
125 | module will be called lmc. | |
126 | ||
127 | # There is no way to detect a Sealevel board. Force it modular | |
128 | config SEALEVEL_4021 | |
129 | tristate "Sealevel Systems 4021 support" | |
d458fd82 | 130 | depends on WAN && ISA && m && ISA_DMA_API && INET |
1da177e4 LT |
131 | help |
132 | This is a driver for the Sealevel Systems ACB 56 serial I/O adapter. | |
133 | ||
134 | The driver will be compiled as a module: the | |
135 | module will be called sealevel. | |
136 | ||
1da177e4 LT |
137 | # Generic HDLC |
138 | config HDLC | |
139 | tristate "Generic HDLC layer" | |
140 | depends on WAN | |
141 | help | |
142 | Say Y to this option if your Linux box contains a WAN (Wide Area | |
143 | Network) card supported by this driver and you are planning to | |
144 | connect the box to a WAN. | |
145 | ||
146 | You will need supporting software from | |
147 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
148 | Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame | |
149 | Relay, synchronous Point-to-Point Protocol (PPP) and X.25. | |
150 | ||
151 | To compile this driver as a module, choose M here: the | |
152 | module will be called hdlc. | |
153 | ||
154 | If unsure, say N. | |
155 | ||
156 | config HDLC_RAW | |
eb2a2fd9 | 157 | tristate "Raw HDLC support" |
1da177e4 LT |
158 | depends on HDLC |
159 | help | |
160 | Generic HDLC driver supporting raw HDLC over WAN connections. | |
161 | ||
162 | If unsure, say N. | |
163 | ||
164 | config HDLC_RAW_ETH | |
eb2a2fd9 | 165 | tristate "Raw HDLC Ethernet device support" |
1da177e4 LT |
166 | depends on HDLC |
167 | help | |
168 | Generic HDLC driver supporting raw HDLC Ethernet device emulation | |
169 | over WAN connections. | |
170 | ||
171 | You will need it for Ethernet over HDLC bridges. | |
172 | ||
173 | If unsure, say N. | |
174 | ||
175 | config HDLC_CISCO | |
eb2a2fd9 | 176 | tristate "Cisco HDLC support" |
1da177e4 LT |
177 | depends on HDLC |
178 | help | |
179 | Generic HDLC driver supporting Cisco HDLC over WAN connections. | |
180 | ||
181 | If unsure, say N. | |
182 | ||
183 | config HDLC_FR | |
eb2a2fd9 | 184 | tristate "Frame Relay support" |
1da177e4 LT |
185 | depends on HDLC |
186 | help | |
187 | Generic HDLC driver supporting Frame Relay over WAN connections. | |
188 | ||
189 | If unsure, say N. | |
190 | ||
191 | config HDLC_PPP | |
eb2a2fd9 | 192 | tristate "Synchronous Point-to-Point Protocol (PPP) support" |
1da177e4 LT |
193 | depends on HDLC |
194 | help | |
195 | Generic HDLC driver supporting PPP over WAN connections. | |
196 | ||
197 | If unsure, say N. | |
198 | ||
199 | config HDLC_X25 | |
eb2a2fd9 | 200 | tristate "X.25 protocol support" |
1da177e4 LT |
201 | depends on HDLC && (LAPB=m && HDLC=m || LAPB=y) |
202 | help | |
203 | Generic HDLC driver supporting X.25 over WAN connections. | |
204 | ||
205 | If unsure, say N. | |
206 | ||
207 | comment "X.25/LAPB support is disabled" | |
208 | depends on WAN && HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y | |
209 | ||
210 | config PCI200SYN | |
211 | tristate "Goramo PCI200SYN support" | |
212 | depends on HDLC && PCI | |
213 | help | |
214 | Driver for PCI200SYN cards by Goramo sp. j. | |
215 | ||
216 | If you have such a card, say Y here and see | |
217 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
218 | ||
219 | To compile this as a module, choose M here: the | |
220 | module will be called pci200syn. | |
221 | ||
222 | If unsure, say N. | |
223 | ||
224 | config WANXL | |
225 | tristate "SBE Inc. wanXL support" | |
226 | depends on HDLC && PCI | |
227 | help | |
228 | Driver for wanXL PCI cards by SBE Inc. | |
229 | ||
230 | If you have such a card, say Y here and see | |
231 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
232 | ||
233 | To compile this as a module, choose M here: the | |
234 | module will be called wanxl. | |
235 | ||
236 | If unsure, say N. | |
237 | ||
238 | config WANXL_BUILD_FIRMWARE | |
239 | bool "rebuild wanXL firmware" | |
240 | depends on WANXL && !PREVENT_FIRMWARE_BUILD | |
241 | help | |
242 | Allows you to rebuild firmware run by the QUICC processor. | |
243 | It requires as68k, ld68k and hexdump programs. | |
244 | ||
245 | You should never need this option, say N. | |
246 | ||
247 | config PC300 | |
248 | tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)" | |
249 | depends on HDLC && PCI | |
250 | ---help--- | |
251 | Driver for the Cyclades-PC300 synchronous communication boards. | |
252 | ||
253 | These boards provide synchronous serial interfaces to your | |
254 | Linux box (interfaces currently available are RS-232/V.35, X.21 and | |
255 | T1/E1). If you wish to support Multilink PPP, please select the | |
256 | option later and read the file README.mlppp provided by PC300 | |
257 | package. | |
258 | ||
259 | To compile this as a module, choose M here: the module | |
260 | will be called pc300. | |
261 | ||
262 | If unsure, say N. | |
263 | ||
264 | config PC300_MLPPP | |
265 | bool "Cyclades-PC300 MLPPP support" | |
266 | depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP | |
267 | help | |
268 | Multilink PPP over the PC300 synchronous communication boards. | |
269 | ||
270 | comment "Cyclades-PC300 MLPPP support is disabled." | |
271 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | |
272 | ||
273 | comment "Refer to the file README.mlppp, provided by PC300 package." | |
274 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | |
275 | ||
276 | config N2 | |
277 | tristate "SDL RISCom/N2 support" | |
278 | depends on HDLC && ISA | |
279 | help | |
280 | Driver for RISCom/N2 single or dual channel ISA cards by | |
281 | SDL Communications Inc. | |
282 | ||
283 | If you have such a card, say Y here and see | |
284 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
285 | ||
286 | Note that N2csu and N2dds cards are not supported by this driver. | |
287 | ||
288 | To compile this driver as a module, choose M here: the module | |
289 | will be called n2. | |
290 | ||
291 | If unsure, say N. | |
292 | ||
293 | config C101 | |
294 | tristate "Moxa C101 support" | |
295 | depends on HDLC && ISA | |
296 | help | |
297 | Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd. | |
298 | ||
299 | If you have such a card, say Y here and see | |
300 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | |
301 | ||
302 | To compile this driver as a module, choose M here: the | |
303 | module will be called c101. | |
304 | ||
305 | If unsure, say N. | |
306 | ||
307 | config FARSYNC | |
308 | tristate "FarSync T-Series support" | |
309 | depends on HDLC && PCI | |
310 | ---help--- | |
311 | Support for the FarSync T-Series X.21 (and V.35/V.24) cards by | |
312 | FarSite Communications Ltd. | |
313 | ||
314 | Synchronous communication is supported on all ports at speeds up to | |
315 | 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC, | |
316 | Frame Relay or X.25/LAPB. | |
317 | ||
318 | If you want the module to be automatically loaded when the interface | |
319 | is referenced then you should add "alias hdlcX farsync" to | |
320 | /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or | |
321 | simply use "alias hdlc* farsync" to indicate all of them. | |
322 | ||
323 | To compile this driver as a module, choose M here: the | |
324 | module will be called farsync. | |
325 | ||
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 | |
385 | bool "WAN router drivers" | |
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 | |
396 | kernel: saying N will just cause the configurator to skip all | |
397 | the questions about WAN router drivers. | |
398 | ||
399 | If unsure, say N. | |
400 | ||
1da177e4 LT |
401 | config CYCLADES_SYNC |
402 | tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)" | |
403 | depends on WAN_ROUTER_DRIVERS && (PCI || ISA) | |
404 | ---help--- | |
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. | |
408 | ||
409 | While no documentation is available at this time please grab the | |
410 | wanconfig tarball in | |
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/>). | |
415 | ||
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). | |
420 | ||
421 | The next questions will ask you about the protocols you want the | |
422 | driver to support (for now only X.25 is supported). | |
423 | ||
424 | If you have one or more of these cards, say Y to this option. | |
425 | ||
426 | To compile this driver as a module, choose M here: the | |
427 | module will be called cyclomx. | |
428 | ||
429 | config CYCLOMX_X25 | |
430 | bool "Cyclom 2X X.25 support (EXPERIMENTAL)" | |
431 | depends on CYCLADES_SYNC | |
432 | help | |
433 | Connect a Cyclom 2X card to an X.25 network. | |
434 | ||
435 | Enabling X.25 support will enlarge your kernel by about 11 kB. | |
436 | ||
437 | # X.25 network drivers | |
438 | config LAPBETHER | |
439 | tristate "LAPB over Ethernet driver (EXPERIMENTAL)" | |
440 | depends on WAN && LAPB && X25 | |
441 | ---help--- | |
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. | |
445 | ||
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". | |
448 | ||
449 | To compile this driver as a module, choose M here: the | |
450 | module will be called lapbether. | |
451 | ||
452 | If unsure, say N. | |
453 | ||
454 | config X25_ASY | |
455 | tristate "X.25 async driver (EXPERIMENTAL)" | |
456 | depends on WAN && LAPB && X25 | |
457 | ---help--- | |
458 | Send and receive X.25 frames over regular asynchronous serial | |
459 | lines such as telephone lines equipped with ordinary modems. | |
460 | ||
461 | Experts should note that this driver doesn't currently comply with | |
462 | the asynchronous HDLS framing protocols in CCITT recommendation X.25. | |
463 | ||
464 | To compile this driver as a module, choose M here: the | |
465 | module will be called x25_asy. | |
466 | ||
467 | If unsure, say N. | |
468 | ||
469 | config SBNI | |
470 | tristate "Granch SBNI12 Leased Line adapter support" | |
471 | depends on WAN && X86 | |
472 | ---help--- | |
473 | Driver for ISA SBNI12-xx cards which are low cost alternatives to | |
474 | leased line modems. | |
475 | ||
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>. | |
479 | ||
480 | To compile this driver as a module, choose M here: the | |
481 | module will be called sbni. | |
482 | ||
483 | If unsure, say N. | |
484 | ||
485 | config SBNI_MULTILINE | |
486 | bool "Multiple line feature support" | |
487 | depends on SBNI | |
488 | help | |
489 | Schedule traffic for some parallel lines, via SBNI12 adapters. | |
490 | ||
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. | |
494 | ||
495 | If unsure, say N. | |
496 | ||
497 | endmenu | |
498 |