1 |
62 |
marcus.erl |
#
|
2 |
|
|
# IPX configuration
|
3 |
|
|
#
|
4 |
|
|
config IPX
|
5 |
|
|
tristate "The IPX protocol"
|
6 |
|
|
select LLC
|
7 |
|
|
---help---
|
8 |
|
|
This is support for the Novell networking protocol, IPX, commonly
|
9 |
|
|
used for local networks of Windows machines. You need it if you
|
10 |
|
|
want to access Novell NetWare file or print servers using the Linux
|
11 |
|
|
Novell client ncpfs (available from
|
12 |
|
|
) or from
|
13 |
|
|
within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
|
14 |
|
|
available from ). In order
|
15 |
|
|
to do the former, you'll also have to say Y to "NCP file system
|
16 |
|
|
support", below.
|
17 |
|
|
|
18 |
|
|
IPX is similar in scope to IP, while SPX, which runs on top of IPX,
|
19 |
|
|
is similar to TCP.
|
20 |
|
|
|
21 |
|
|
To turn your Linux box into a fully featured NetWare file server and
|
22 |
|
|
IPX router, say Y here and fetch either lwared from
|
23 |
|
|
or
|
24 |
|
|
mars_nwe from . For more
|
25 |
|
|
information, read the IPX-HOWTO available from
|
26 |
|
|
.
|
27 |
|
|
|
28 |
|
|
The IPX driver would enlarge your kernel by about 16 KB. To compile
|
29 |
|
|
this driver as a module, choose M here: the module will be called ipx.
|
30 |
|
|
Unless you want to integrate your Linux box with a local Novell
|
31 |
|
|
network, say N.
|
32 |
|
|
|
33 |
|
|
config IPX_INTERN
|
34 |
|
|
bool "IPX: Full internal IPX network"
|
35 |
|
|
depends on IPX
|
36 |
|
|
---help---
|
37 |
|
|
Every IPX network has an address that identifies it. Sometimes it is
|
38 |
|
|
useful to give an IPX "network" address to your Linux box as well
|
39 |
|
|
(for example if your box is acting as a file server for different
|
40 |
|
|
IPX networks: it will then be accessible from everywhere using the
|
41 |
|
|
same address). The way this is done is to create a virtual internal
|
42 |
|
|
"network" inside your box and to assign an IPX address to this
|
43 |
|
|
network. Say Y here if you want to do this; read the IPX-HOWTO at
|
44 |
|
|
for details.
|
45 |
|
|
|
46 |
|
|
The full internal IPX network enables you to allocate sockets on
|
47 |
|
|
different virtual nodes of the internal network. This is done by
|
48 |
|
|
evaluating the field sipx_node of the socket address given to the
|
49 |
|
|
bind call. So applications should always initialize the node field
|
50 |
|
|
to 0 when binding a socket on the primary network. In this case the
|
51 |
|
|
socket is assigned the default node that has been given to the
|
52 |
|
|
kernel when the internal network was created. By enabling the full
|
53 |
|
|
internal IPX network the cross-forwarding of packets targeted at
|
54 |
|
|
'special' sockets to sockets listening on the primary network is
|
55 |
|
|
disabled. This might break existing applications, especially RIP/SAP
|
56 |
|
|
daemons. A RIP/SAP daemon that works well with the full internal net
|
57 |
|
|
can be found on .
|
58 |
|
|
|
59 |
|
|
If you don't know what you are doing, say N.
|
60 |
|
|
|