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