blob: 92f2ec46fd2248a11b1b2591ad1c69fb0682b7d8 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# DECnet configuration
3#
Sam Ravnborg6a2e9b72005-07-11 21:13:56 -07004config DECNET
5 tristate "DECnet Support"
6 ---help---
7 The DECnet networking protocol was used in many products made by
8 Digital (now Compaq). It provides reliable stream and sequenced
9 packet communications over which run a variety of services similar
10 to those which run over TCP/IP.
11
12 To find some tools to use with the kernel layer support, please
13 look at Patrick Caulfield's web site:
14 <http://linux-decnet.sourceforge.net/>.
15
16 More detailed documentation is available in
17 <file:Documentation/networking/decnet.txt>.
18
19 Be sure to say Y to "/proc file system support" and "Sysctl support"
20 below when using DECnet, since you will need sysctl support to aid
21 in configuration at run time.
22
23 The DECnet code is also available as a module ( = code which can be
24 inserted in and removed from the running kernel whenever you want).
25 The module is called decnet.
26
Linus Torvalds1da177e2005-04-16 15:20:36 -070027config DECNET_ROUTER
28 bool "DECnet: router support (EXPERIMENTAL)"
29 depends on DECNET && EXPERIMENTAL
30 ---help---
31 Add support for turning your DECnet Endnode into a level 1 or 2
32 router. This is an experimental, but functional option. If you
33 do say Y here, then make sure that you also say Y to "Kernel/User
34 network link driver", "Routing messages" and "Network packet
35 filtering". The first two are required to allow configuration via
36 rtnetlink (you will need Alexey Kuznetsov's iproute2 package
37 from <ftp://ftp.tux.org/pub/net/ip-routing/>). The "Network packet
38 filtering" option will be required for the forthcoming routing daemon
39 to work.
40
41 See <file:Documentation/networking/decnet.txt> for more information.
42
43config DECNET_ROUTE_FWMARK
44 bool "DECnet: use FWMARK value as routing key (EXPERIMENTAL)"
45 depends on DECNET_ROUTER && NETFILTER
46 help
47 If you say Y here, you will be able to specify different routes for
48 packets with different FWMARK ("firewalling mark") values
49 (see ipchains(8), "-m" argument).
50