Kconfig 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. #
  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. <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. IPX is similar in scope to IP, while SPX, which runs on top of IPX,
  18. is similar to TCP. There is also experimental support for SPX in
  19. Linux (see "SPX networking", below).
  20. To turn your Linux box into a fully featured NetWare file server and
  21. IPX router, say Y here and fetch either lwared from
  22. <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
  23. mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
  24. information, read the IPX-HOWTO available from
  25. <http://www.tldp.org/docs.html#howto>.
  26. General information about how to connect Linux, Windows machines and
  27. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  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. config IPX_INTERN
  33. bool "IPX: Full internal IPX network"
  34. depends on IPX
  35. ---help---
  36. Every IPX network has an address that identifies it. Sometimes it is
  37. useful to give an IPX "network" address to your Linux box as well
  38. (for example if your box is acting as a file server for different
  39. IPX networks: it will then be accessible from everywhere using the
  40. same address). The way this is done is to create a virtual internal
  41. "network" inside your box and to assign an IPX address to this
  42. network. Say Y here if you want to do this; read the IPX-HOWTO at
  43. <http://www.tldp.org/docs.html#howto> for details.
  44. The full internal IPX network enables you to allocate sockets on
  45. different virtual nodes of the internal network. This is done by
  46. evaluating the field sipx_node of the socket address given to the
  47. bind call. So applications should always initialize the node field
  48. to 0 when binding a socket on the primary network. In this case the
  49. socket is assigned the default node that has been given to the
  50. kernel when the internal network was created. By enabling the full
  51. internal IPX network the cross-forwarding of packets targeted at
  52. 'special' sockets to sockets listening on the primary network is
  53. disabled. This might break existing applications, especially RIP/SAP
  54. daemons. A RIP/SAP daemon that works well with the full internal net
  55. can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
  56. If you don't know what you are doing, say N.