diff options
author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
commit | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch) | |
tree | 0bba044c4ce775e45a88a51686b5d9f90697ea9d /drivers/net/wan/Kconfig |
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!
Diffstat (limited to 'drivers/net/wan/Kconfig')
-rw-r--r-- | drivers/net/wan/Kconfig | 607 |
1 files changed, 607 insertions, 0 deletions
diff --git a/drivers/net/wan/Kconfig b/drivers/net/wan/Kconfig new file mode 100644 index 000000000000..35791934a602 --- /dev/null +++ b/drivers/net/wan/Kconfig | |||
@@ -0,0 +1,607 @@ | |||
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" | ||
29 | depends on WAN && ISA && m | ||
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" | ||
41 | depends on WAN && ISA && m | ||
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" | ||
130 | depends on WAN && ISA && m | ||
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 | |||
137 | config SYNCLINK_SYNCPPP | ||
138 | tristate "SyncLink HDLC/SYNCPPP support" | ||
139 | depends on WAN | ||
140 | help | ||
141 | Enables HDLC/SYNCPPP support for the SyncLink WAN driver. | ||
142 | |||
143 | Normally the SyncLink WAN driver works with the main PPP driver | ||
144 | <file:drivers/net/ppp_generic.c> and pppd program. | ||
145 | HDLC/SYNCPPP support allows use of the Cisco HDLC/PPP driver | ||
146 | <file:drivers/net/wan/syncppp.c>. The SyncLink WAN driver (in | ||
147 | character devices) must also be enabled. | ||
148 | |||
149 | # Generic HDLC | ||
150 | config HDLC | ||
151 | tristate "Generic HDLC layer" | ||
152 | depends on WAN | ||
153 | help | ||
154 | Say Y to this option if your Linux box contains a WAN (Wide Area | ||
155 | Network) card supported by this driver and you are planning to | ||
156 | connect the box to a WAN. | ||
157 | |||
158 | You will need supporting software from | ||
159 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | ||
160 | Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame | ||
161 | Relay, synchronous Point-to-Point Protocol (PPP) and X.25. | ||
162 | |||
163 | To compile this driver as a module, choose M here: the | ||
164 | module will be called hdlc. | ||
165 | |||
166 | If unsure, say N. | ||
167 | |||
168 | config HDLC_RAW | ||
169 | bool "Raw HDLC support" | ||
170 | depends on HDLC | ||
171 | help | ||
172 | Generic HDLC driver supporting raw HDLC over WAN connections. | ||
173 | |||
174 | If unsure, say N. | ||
175 | |||
176 | config HDLC_RAW_ETH | ||
177 | bool "Raw HDLC Ethernet device support" | ||
178 | depends on HDLC | ||
179 | help | ||
180 | Generic HDLC driver supporting raw HDLC Ethernet device emulation | ||
181 | over WAN connections. | ||
182 | |||
183 | You will need it for Ethernet over HDLC bridges. | ||
184 | |||
185 | If unsure, say N. | ||
186 | |||
187 | config HDLC_CISCO | ||
188 | bool "Cisco HDLC support" | ||
189 | depends on HDLC | ||
190 | help | ||
191 | Generic HDLC driver supporting Cisco HDLC over WAN connections. | ||
192 | |||
193 | If unsure, say N. | ||
194 | |||
195 | config HDLC_FR | ||
196 | bool "Frame Relay support" | ||
197 | depends on HDLC | ||
198 | help | ||
199 | Generic HDLC driver supporting Frame Relay over WAN connections. | ||
200 | |||
201 | If unsure, say N. | ||
202 | |||
203 | config HDLC_PPP | ||
204 | bool "Synchronous Point-to-Point Protocol (PPP) support" | ||
205 | depends on HDLC | ||
206 | help | ||
207 | Generic HDLC driver supporting PPP over WAN connections. | ||
208 | |||
209 | If unsure, say N. | ||
210 | |||
211 | config HDLC_X25 | ||
212 | bool "X.25 protocol support" | ||
213 | depends on HDLC && (LAPB=m && HDLC=m || LAPB=y) | ||
214 | help | ||
215 | Generic HDLC driver supporting X.25 over WAN connections. | ||
216 | |||
217 | If unsure, say N. | ||
218 | |||
219 | comment "X.25/LAPB support is disabled" | ||
220 | depends on WAN && HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y | ||
221 | |||
222 | config PCI200SYN | ||
223 | tristate "Goramo PCI200SYN support" | ||
224 | depends on HDLC && PCI | ||
225 | help | ||
226 | Driver for PCI200SYN cards by Goramo sp. j. | ||
227 | |||
228 | If you have such a card, say Y here and see | ||
229 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | ||
230 | |||
231 | To compile this as a module, choose M here: the | ||
232 | module will be called pci200syn. | ||
233 | |||
234 | If unsure, say N. | ||
235 | |||
236 | config WANXL | ||
237 | tristate "SBE Inc. wanXL support" | ||
238 | depends on HDLC && PCI | ||
239 | help | ||
240 | Driver for wanXL PCI cards by SBE Inc. | ||
241 | |||
242 | If you have such a card, say Y here and see | ||
243 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | ||
244 | |||
245 | To compile this as a module, choose M here: the | ||
246 | module will be called wanxl. | ||
247 | |||
248 | If unsure, say N. | ||
249 | |||
250 | config WANXL_BUILD_FIRMWARE | ||
251 | bool "rebuild wanXL firmware" | ||
252 | depends on WANXL && !PREVENT_FIRMWARE_BUILD | ||
253 | help | ||
254 | Allows you to rebuild firmware run by the QUICC processor. | ||
255 | It requires as68k, ld68k and hexdump programs. | ||
256 | |||
257 | You should never need this option, say N. | ||
258 | |||
259 | config PC300 | ||
260 | tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)" | ||
261 | depends on HDLC && PCI | ||
262 | ---help--- | ||
263 | Driver for the Cyclades-PC300 synchronous communication boards. | ||
264 | |||
265 | These boards provide synchronous serial interfaces to your | ||
266 | Linux box (interfaces currently available are RS-232/V.35, X.21 and | ||
267 | T1/E1). If you wish to support Multilink PPP, please select the | ||
268 | option later and read the file README.mlppp provided by PC300 | ||
269 | package. | ||
270 | |||
271 | To compile this as a module, choose M here: the module | ||
272 | will be called pc300. | ||
273 | |||
274 | If unsure, say N. | ||
275 | |||
276 | config PC300_MLPPP | ||
277 | bool "Cyclades-PC300 MLPPP support" | ||
278 | depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP | ||
279 | help | ||
280 | Multilink PPP over the PC300 synchronous communication boards. | ||
281 | |||
282 | comment "Cyclades-PC300 MLPPP support is disabled." | ||
283 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | ||
284 | |||
285 | comment "Refer to the file README.mlppp, provided by PC300 package." | ||
286 | depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP) | ||
287 | |||
288 | config N2 | ||
289 | tristate "SDL RISCom/N2 support" | ||
290 | depends on HDLC && ISA | ||
291 | help | ||
292 | Driver for RISCom/N2 single or dual channel ISA cards by | ||
293 | SDL Communications Inc. | ||
294 | |||
295 | If you have such a card, say Y here and see | ||
296 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | ||
297 | |||
298 | Note that N2csu and N2dds cards are not supported by this driver. | ||
299 | |||
300 | To compile this driver as a module, choose M here: the module | ||
301 | will be called n2. | ||
302 | |||
303 | If unsure, say N. | ||
304 | |||
305 | config C101 | ||
306 | tristate "Moxa C101 support" | ||
307 | depends on HDLC && ISA | ||
308 | help | ||
309 | Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd. | ||
310 | |||
311 | If you have such a card, say Y here and see | ||
312 | <http://www.kernel.org/pub/linux/utils/net/hdlc/>. | ||
313 | |||
314 | To compile this driver as a module, choose M here: the | ||
315 | module will be called c101. | ||
316 | |||
317 | If unsure, say N. | ||
318 | |||
319 | config FARSYNC | ||
320 | tristate "FarSync T-Series support" | ||
321 | depends on HDLC && PCI | ||
322 | ---help--- | ||
323 | Support for the FarSync T-Series X.21 (and V.35/V.24) cards by | ||
324 | FarSite Communications Ltd. | ||
325 | |||
326 | Synchronous communication is supported on all ports at speeds up to | ||
327 | 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC, | ||
328 | Frame Relay or X.25/LAPB. | ||
329 | |||
330 | If you want the module to be automatically loaded when the interface | ||
331 | is referenced then you should add "alias hdlcX farsync" to | ||
332 | /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or | ||
333 | simply use "alias hdlc* farsync" to indicate all of them. | ||
334 | |||
335 | To compile this driver as a module, choose M here: the | ||
336 | module will be called farsync. | ||
337 | |||
338 | config DLCI | ||
339 | tristate "Frame Relay DLCI support" | ||
340 | depends on WAN | ||
341 | ---help--- | ||
342 | Support for the Frame Relay protocol. | ||
343 | |||
344 | Frame Relay is a fast low-cost way to connect to a remote Internet | ||
345 | access provider or to form a private wide area network. The one | ||
346 | physical line from your box to the local "switch" (i.e. the entry | ||
347 | point to the Frame Relay network, usually at the phone company) can | ||
348 | carry several logical point-to-point connections to other computers | ||
349 | connected to the Frame Relay network. For a general explanation of | ||
350 | the protocol, check out <http://www.mplsforum.org/>. | ||
351 | |||
352 | To use frame relay, you need supporting hardware (called FRAD) and | ||
353 | certain programs from the net-tools package as explained in | ||
354 | <file:Documentation/networking/framerelay.txt>. | ||
355 | |||
356 | To compile this driver as a module, choose M here: the | ||
357 | module will be called dlci. | ||
358 | |||
359 | config DLCI_COUNT | ||
360 | int "Max open DLCI" | ||
361 | depends on DLCI | ||
362 | default "24" | ||
363 | help | ||
364 | Maximal number of logical point-to-point frame relay connections | ||
365 | (the identifiers of which are called DCLIs) that the driver can | ||
366 | handle. | ||
367 | |||
368 | The default is probably fine. | ||
369 | |||
370 | config DLCI_MAX | ||
371 | int "Max DLCI per device" | ||
372 | depends on DLCI | ||
373 | default "8" | ||
374 | help | ||
375 | How many logical point-to-point frame relay connections (the | ||
376 | identifiers of which are called DCLIs) should be handled by each | ||
377 | of your hardware frame relay access devices. | ||
378 | |||
379 | Go with the default. | ||
380 | |||
381 | config SDLA | ||
382 | tristate "SDLA (Sangoma S502/S508) support" | ||
383 | depends on DLCI && ISA | ||
384 | help | ||
385 | Driver for the Sangoma S502A, S502E, and S508 Frame Relay Access | ||
386 | Devices. | ||
387 | |||
388 | These are multi-protocol cards, but only Frame Relay is supported | ||
389 | by the driver at this time. Please read | ||
390 | <file:Documentation/networking/framerelay.txt>. | ||
391 | |||
392 | To compile this driver as a module, choose M here: the | ||
393 | module will be called sdla. | ||
394 | |||
395 | # Wan router core. | ||
396 | config WAN_ROUTER_DRIVERS | ||
397 | bool "WAN router drivers" | ||
398 | depends on WAN && WAN_ROUTER | ||
399 | ---help--- | ||
400 | Connect LAN to WAN via Linux box. | ||
401 | |||
402 | Select driver your card and remember to say Y to "Wan Router." | ||
403 | You will need the wan-tools package which is available from | ||
404 | <ftp://ftp.sangoma.com/>. For more information read: | ||
405 | <file:Documentation/networking/wan-router.txt>. | ||
406 | |||
407 | Note that the answer to this question won't directly affect the | ||
408 | kernel: saying N will just cause the configurator to skip all | ||
409 | the questions about WAN router drivers. | ||
410 | |||
411 | If unsure, say N. | ||
412 | |||
413 | config VENDOR_SANGOMA | ||
414 | tristate "Sangoma WANPIPE(tm) multiprotocol cards" | ||
415 | depends on WAN_ROUTER_DRIVERS && WAN_ROUTER && (PCI || ISA) && BROKEN | ||
416 | ---help--- | ||
417 | Driver for S514-PCI/ISA Synchronous Data Link Adapters (SDLA). | ||
418 | |||
419 | WANPIPE from Sangoma Technologies Inc. <http://www.sangoma.com/> | ||
420 | is a family of intelligent multiprotocol WAN adapters with data | ||
421 | transfer rates up to 4Mbps. Cards support: | ||
422 | |||
423 | - X.25, Frame Relay, PPP, Cisco HDLC protocols. | ||
424 | |||
425 | - API for protocols like HDLC (LAPB), HDLC Streaming, X.25, | ||
426 | Frame Relay and BiSync. | ||
427 | |||
428 | - Ethernet Bridging over Frame Relay protocol. | ||
429 | |||
430 | - MULTILINK PPP | ||
431 | |||
432 | - Async PPP (Modem Dialup) | ||
433 | |||
434 | The next questions will ask you about the protocols you want | ||
435 | the driver to support. | ||
436 | |||
437 | If you have one or more of these cards, say M to this option; | ||
438 | and read <file:Documentation/networking/wanpipe.txt>. | ||
439 | |||
440 | To compile this driver as a module, choose M here: the | ||
441 | module will be called wanpipe. | ||
442 | |||
443 | config WANPIPE_CHDLC | ||
444 | bool "WANPIPE Cisco HDLC support" | ||
445 | depends on VENDOR_SANGOMA | ||
446 | ---help--- | ||
447 | Connect a WANPIPE card to a leased line using the Cisco HDLC. | ||
448 | |||
449 | - Supports Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards | ||
450 | which allows user to build applications using the HDLC streaming API. | ||
451 | |||
452 | - CHDLC Streaming MULTILINK PPP that can bind multiple WANPIPE T1 | ||
453 | cards into a single logical channel. | ||
454 | |||
455 | Say Y and the Cisco HDLC support, HDLC streaming API and | ||
456 | MULTILINK PPP will be included in the driver. | ||
457 | |||
458 | config WANPIPE_FR | ||
459 | bool "WANPIPE Frame Relay support" | ||
460 | depends on VENDOR_SANGOMA | ||
461 | help | ||
462 | Connect a WANPIPE card to a Frame Relay network, or use Frame Felay | ||
463 | API to develop custom applications. | ||
464 | |||
465 | Contains the Ethernet Bridging over Frame Relay feature, where | ||
466 | a WANPIPE frame relay link can be directly connected to the Linux | ||
467 | kernel bridge. The Frame Relay option is supported on S514-PCI | ||
468 | and S508-ISA cards. | ||
469 | |||
470 | Say Y and the Frame Relay support will be included in the driver. | ||
471 | |||
472 | config WANPIPE_X25 | ||
473 | bool "WANPIPE X.25 support" | ||
474 | depends on VENDOR_SANGOMA | ||
475 | help | ||
476 | Connect a WANPIPE card to an X.25 network. | ||
477 | |||
478 | Includes the X.25 API support for custom applications over the | ||
479 | X.25 protocol. The X.25 option is supported on S514-PCI and | ||
480 | S508-ISA cards. | ||
481 | |||
482 | Say Y and the X.25 support will be included in the driver. | ||
483 | |||
484 | config WANPIPE_PPP | ||
485 | bool "WANPIPE PPP support" | ||
486 | depends on VENDOR_SANGOMA | ||
487 | help | ||
488 | Connect a WANPIPE card to a leased line using Point-to-Point | ||
489 | Protocol (PPP). | ||
490 | |||
491 | The PPP option is supported on S514-PCI/S508-ISA cards. | ||
492 | |||
493 | Say Y and the PPP support will be included in the driver. | ||
494 | |||
495 | config WANPIPE_MULTPPP | ||
496 | bool "WANPIPE Multi-Port PPP support" | ||
497 | depends on VENDOR_SANGOMA | ||
498 | help | ||
499 | Connect a WANPIPE card to a leased line using Point-to-Point | ||
500 | Protocol (PPP). | ||
501 | |||
502 | Uses in-kernel SyncPPP protocol over the Sangoma HDLC Streaming | ||
503 | adapter. In this case each Sangoma adapter port can support an | ||
504 | independent PPP connection. For example, a single Quad-Port PCI | ||
505 | adapter can support up to four independent PPP links. The PPP | ||
506 | option is supported on S514-PCI/S508-ISA cards. | ||
507 | |||
508 | Say Y and the Multi-Port PPP support will be included in the driver. | ||
509 | |||
510 | config CYCLADES_SYNC | ||
511 | tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)" | ||
512 | depends on WAN_ROUTER_DRIVERS && (PCI || ISA) | ||
513 | ---help--- | ||
514 | Cyclom 2X from Cyclades Corporation <http://www.cyclades.com/> is an | ||
515 | intelligent multiprotocol WAN adapter with data transfer rates up to | ||
516 | 512 Kbps. These cards support the X.25 and SNA related protocols. | ||
517 | |||
518 | While no documentation is available at this time please grab the | ||
519 | wanconfig tarball in | ||
520 | <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes | ||
521 | to make it compile with the current wanrouter include files; efforts | ||
522 | are being made to use the original package available at | ||
523 | <ftp://ftp.sangoma.com/>). | ||
524 | |||
525 | Feel free to contact me or the cycsyn-devel mailing list at | ||
526 | <acme@conectiva.com.br> and <cycsyn-devel@bazar.conectiva.com.br> for | ||
527 | additional details, I hope to have documentation available as soon as | ||
528 | possible. (Cyclades Brazil is writing the Documentation). | ||
529 | |||
530 | The next questions will ask you about the protocols you want the | ||
531 | driver to support (for now only X.25 is supported). | ||
532 | |||
533 | If you have one or more of these cards, say Y to this option. | ||
534 | |||
535 | To compile this driver as a module, choose M here: the | ||
536 | module will be called cyclomx. | ||
537 | |||
538 | config CYCLOMX_X25 | ||
539 | bool "Cyclom 2X X.25 support (EXPERIMENTAL)" | ||
540 | depends on CYCLADES_SYNC | ||
541 | help | ||
542 | Connect a Cyclom 2X card to an X.25 network. | ||
543 | |||
544 | Enabling X.25 support will enlarge your kernel by about 11 kB. | ||
545 | |||
546 | # X.25 network drivers | ||
547 | config LAPBETHER | ||
548 | tristate "LAPB over Ethernet driver (EXPERIMENTAL)" | ||
549 | depends on WAN && LAPB && X25 | ||
550 | ---help--- | ||
551 | Driver for a pseudo device (typically called /dev/lapb0) which allows | ||
552 | you to open an LAPB point-to-point connection to some other computer | ||
553 | on your Ethernet network. | ||
554 | |||
555 | In order to do this, you need to say Y or M to the driver for your | ||
556 | Ethernet card as well as to "LAPB Data Link Driver". | ||
557 | |||
558 | To compile this driver as a module, choose M here: the | ||
559 | module will be called lapbether. | ||
560 | |||
561 | If unsure, say N. | ||
562 | |||
563 | config X25_ASY | ||
564 | tristate "X.25 async driver (EXPERIMENTAL)" | ||
565 | depends on WAN && LAPB && X25 | ||
566 | ---help--- | ||
567 | Send and receive X.25 frames over regular asynchronous serial | ||
568 | lines such as telephone lines equipped with ordinary modems. | ||
569 | |||
570 | Experts should note that this driver doesn't currently comply with | ||
571 | the asynchronous HDLS framing protocols in CCITT recommendation X.25. | ||
572 | |||
573 | To compile this driver as a module, choose M here: the | ||
574 | module will be called x25_asy. | ||
575 | |||
576 | If unsure, say N. | ||
577 | |||
578 | config SBNI | ||
579 | tristate "Granch SBNI12 Leased Line adapter support" | ||
580 | depends on WAN && X86 | ||
581 | ---help--- | ||
582 | Driver for ISA SBNI12-xx cards which are low cost alternatives to | ||
583 | leased line modems. | ||
584 | |||
585 | You can find more information and last versions of drivers and | ||
586 | utilities at <http://www.granch.ru/>. If you have any question you | ||
587 | can send email to <sbni@granch.ru>. | ||
588 | |||
589 | To compile this driver as a module, choose M here: the | ||
590 | module will be called sbni. | ||
591 | |||
592 | If unsure, say N. | ||
593 | |||
594 | config SBNI_MULTILINE | ||
595 | bool "Multiple line feature support" | ||
596 | depends on SBNI | ||
597 | help | ||
598 | Schedule traffic for some parallel lines, via SBNI12 adapters. | ||
599 | |||
600 | If you have two computers connected with two parallel lines it's | ||
601 | possible to increase transfer rate nearly twice. You should have | ||
602 | a program named 'sbniconfig' to configure adapters. | ||
603 | |||
604 | If unsure, say N. | ||
605 | |||
606 | endmenu | ||
607 | |||