CONFIG_IPX_INTERN: IPX: Full internal IPX network

General informations

The Linux kernel configuration item CONFIG_IPX_INTERN has multiple definitions:

IPX: Full internal IPX network found in drivers/staging/ipx/Kconfig

The configuration item CONFIG_IPX_INTERN:

• prompt: IPX: Full internal IPX network
• type: bool
• depends on: CONFIG_IPX
• defined in drivers/staging/ipx/Kconfig
• found in Linux kernels: 4.16–4.17

Help text

Every IPX network has an address that identifies it. Sometimes it is useful to give an IPX "network" address to your Linux box as well (for example if your box is acting as a file server for different IPX networks: it will then be accessible from everywhere using the same address). The way this is done is to create a virtual internal "network" inside your box and to assign an IPX address to this network. Say Y here if you want to do this; read the IPX-HOWTO at http://www.tldp.org/docs.html#howto for details.

The full internal IPX network enables you to allocate sockets on different virtual nodes of the internal network. This is done by evaluating the field sipx_node of the socket address given to the bind call. So applications should always initialize the node field to 0 when binding a socket on the primary network. In this case the socket is assigned the default node that has been given to the kernel when the internal network was created. By enabling the full internal IPX network the cross-forwarding of packets targeted at 'special' sockets to sockets listening on the primary network is disabled. This might break existing applications, especially RIP/SAP daemons. A RIP/SAP daemon that works well with the full internal net can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.

If you don't know what you are doing, say N.

IPX: Full internal IPX network found in net/ipx/Kconfig

The configuration item CONFIG_IPX_INTERN:

• prompt: IPX: Full internal IPX network
• type: bool
• depends on: CONFIG_IPX
• defined in net/ipx/Kconfig
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.19, 4.0–4.15

Help text

Every IPX network has an address that identifies it. Sometimes it is useful to give an IPX "network" address to your Linux box as well (for example if your box is acting as a file server for different IPX networks: it will then be accessible from everywhere using the same address). The way this is done is to create a virtual internal "network" inside your box and to assign an IPX address to this network. Say Y here if you want to do this; read the IPX-HOWTO at http://www.tldp.org/docs.html#howto for details.

The full internal IPX network enables you to allocate sockets on different virtual nodes of the internal network. This is done by evaluating the field sipx_node of the socket address given to the bind call. So applications should always initialize the node field to 0 when binding a socket on the primary network. In this case the socket is assigned the default node that has been given to the kernel when the internal network was created. By enabling the full internal IPX network the cross-forwarding of packets targeted at 'special' sockets to sockets listening on the primary network is disabled. This might break existing applications, especially RIP/SAP daemons. A RIP/SAP daemon that works well with the full internal net can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.

If you don't know what you are doing, say N.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: