Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # IPX configuration |
| 3 | # |
Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame^] | 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 | <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from |
| 13 | within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, |
| 14 | available from <http://www.tldp.org/docs.html#howto>). 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. There is also experimental support for SPX in |
| 20 | Linux (see "SPX networking", below). |
| 21 | |
| 22 | To turn your Linux box into a fully featured NetWare file server and |
| 23 | IPX router, say Y here and fetch either lwared from |
| 24 | <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or |
| 25 | mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more |
| 26 | information, read the IPX-HOWTO available from |
| 27 | <http://www.tldp.org/docs.html#howto>. |
| 28 | |
| 29 | General information about how to connect Linux, Windows machines and |
| 30 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. |
| 31 | |
| 32 | The IPX driver would enlarge your kernel by about 16 KB. To compile |
| 33 | this driver as a module, choose M here: the module will be called ipx. |
| 34 | Unless you want to integrate your Linux box with a local Novell |
| 35 | network, say N. |
| 36 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 37 | config IPX_INTERN |
| 38 | bool "IPX: Full internal IPX network" |
| 39 | depends on IPX |
| 40 | ---help--- |
| 41 | Every IPX network has an address that identifies it. Sometimes it is |
| 42 | useful to give an IPX "network" address to your Linux box as well |
| 43 | (for example if your box is acting as a file server for different |
| 44 | IPX networks: it will then be accessible from everywhere using the |
| 45 | same address). The way this is done is to create a virtual internal |
| 46 | "network" inside your box and to assign an IPX address to this |
| 47 | network. Say Y here if you want to do this; read the IPX-HOWTO at |
| 48 | <http://www.tldp.org/docs.html#howto> for details. |
| 49 | |
| 50 | The full internal IPX network enables you to allocate sockets on |
| 51 | different virtual nodes of the internal network. This is done by |
| 52 | evaluating the field sipx_node of the socket address given to the |
| 53 | bind call. So applications should always initialize the node field |
| 54 | to 0 when binding a socket on the primary network. In this case the |
| 55 | socket is assigned the default node that has been given to the |
| 56 | kernel when the internal network was created. By enabling the full |
| 57 | internal IPX network the cross-forwarding of packets targeted at |
| 58 | 'special' sockets to sockets listening on the primary network is |
| 59 | disabled. This might break existing applications, especially RIP/SAP |
| 60 | daemons. A RIP/SAP daemon that works well with the full internal net |
| 61 | can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>. |
| 62 | |
| 63 | If you don't know what you are doing, say N. |
| 64 | |