Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame^] | 1 | # |
| 2 | # IPX configuration |
| 3 | # |
| 4 | config IPX_INTERN |
| 5 | bool "IPX: Full internal IPX network" |
| 6 | depends on IPX |
| 7 | ---help--- |
| 8 | Every IPX network has an address that identifies it. Sometimes it is |
| 9 | useful to give an IPX "network" address to your Linux box as well |
| 10 | (for example if your box is acting as a file server for different |
| 11 | IPX networks: it will then be accessible from everywhere using the |
| 12 | same address). The way this is done is to create a virtual internal |
| 13 | "network" inside your box and to assign an IPX address to this |
| 14 | network. Say Y here if you want to do this; read the IPX-HOWTO at |
| 15 | <http://www.tldp.org/docs.html#howto> for details. |
| 16 | |
| 17 | The full internal IPX network enables you to allocate sockets on |
| 18 | different virtual nodes of the internal network. This is done by |
| 19 | evaluating the field sipx_node of the socket address given to the |
| 20 | bind call. So applications should always initialize the node field |
| 21 | to 0 when binding a socket on the primary network. In this case the |
| 22 | socket is assigned the default node that has been given to the |
| 23 | kernel when the internal network was created. By enabling the full |
| 24 | internal IPX network the cross-forwarding of packets targeted at |
| 25 | 'special' sockets to sockets listening on the primary network is |
| 26 | disabled. This might break existing applications, especially RIP/SAP |
| 27 | daemons. A RIP/SAP daemon that works well with the full internal net |
| 28 | can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>. |
| 29 | |
| 30 | If you don't know what you are doing, say N. |
| 31 | |