| Kyle Swenson | 8d8f654 | 2021-03-15 11:02:55 -0600 | [diff] [blame] | 1 | # |
| 2 | # Asynchronous Transfer Mode (ATM) |
| 3 | # |
| 4 | |
| 5 | config ATM |
| 6 | tristate "Asynchronous Transfer Mode (ATM)" |
| 7 | ---help--- |
| 8 | ATM is a high-speed networking technology for Local Area Networks |
| 9 | and Wide Area Networks. It uses a fixed packet size and is |
| 10 | connection oriented, allowing for the negotiation of minimum |
| 11 | bandwidth requirements. |
| 12 | |
| 13 | In order to participate in an ATM network, your Linux box needs an |
| 14 | ATM networking card. If you have that, say Y here and to the driver |
| 15 | of your ATM card below. |
| 16 | |
| 17 | Note that you need a set of user-space programs to actually make use |
| 18 | of ATM. See the file <file:Documentation/networking/atm.txt> for |
| 19 | further details. |
| 20 | |
| 21 | config ATM_CLIP |
| 22 | tristate "Classical IP over ATM" |
| 23 | depends on ATM && INET |
| 24 | help |
| 25 | Classical IP over ATM for PVCs and SVCs, supporting InARP and |
| 26 | ATMARP. If you want to communication with other IP hosts on your ATM |
| 27 | network, you will typically either say Y here or to "LAN Emulation |
| 28 | (LANE)" below. |
| 29 | |
| 30 | config ATM_CLIP_NO_ICMP |
| 31 | bool "Do NOT send ICMP if no neighbour" |
| 32 | depends on ATM_CLIP |
| 33 | help |
| 34 | Normally, an "ICMP host unreachable" message is sent if a neighbour |
| 35 | cannot be reached because there is no VC to it in the kernel's |
| 36 | ATMARP table. This may cause problems when ATMARP table entries are |
| 37 | briefly removed during revalidation. If you say Y here, packets to |
| 38 | such neighbours are silently discarded instead. |
| 39 | |
| 40 | config ATM_LANE |
| 41 | tristate "LAN Emulation (LANE) support" |
| 42 | depends on ATM |
| 43 | help |
| 44 | LAN Emulation emulates services of existing LANs across an ATM |
| 45 | network. Besides operating as a normal ATM end station client, Linux |
| 46 | LANE client can also act as an proxy client bridging packets between |
| 47 | ELAN and Ethernet segments. You need LANE if you want to try MPOA. |
| 48 | |
| 49 | config ATM_MPOA |
| 50 | tristate "Multi-Protocol Over ATM (MPOA) support" |
| 51 | depends on ATM && INET && ATM_LANE!=n |
| 52 | help |
| 53 | Multi-Protocol Over ATM allows ATM edge devices such as routers, |
| 54 | bridges and ATM attached hosts establish direct ATM VCs across |
| 55 | subnetwork boundaries. These shortcut connections bypass routers |
| 56 | enhancing overall network performance. |
| 57 | |
| 58 | config ATM_BR2684 |
| 59 | tristate "RFC1483/2684 Bridged protocols" |
| 60 | depends on ATM && INET |
| 61 | help |
| 62 | ATM PVCs can carry ethernet PDUs according to RFC2684 (formerly 1483) |
| 63 | This device will act like an ethernet from the kernels point of view, |
| 64 | with the traffic being carried by ATM PVCs (currently 1 PVC/device). |
| 65 | This is sometimes used over DSL lines. If in doubt, say N. |
| 66 | |
| 67 | config ATM_BR2684_IPFILTER |
| 68 | bool "Per-VC IP filter kludge" |
| 69 | depends on ATM_BR2684 |
| 70 | help |
| 71 | This is an experimental mechanism for users who need to terminate a |
| 72 | large number of IP-only vcc's. Do not enable this unless you are sure |
| 73 | you know what you are doing. |