CONFIG_UML_NET_MCAST: Multicast transport (obsolete)

General informations

The Linux kernel configuration item CONFIG_UML_NET_MCAST has multiple definitions:

Multicast transport (obsolete) found in arch/um/drivers/Kconfig

The configuration item CONFIG_UML_NET_MCAST:

• prompt: Multicast transport (obsolete)
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/drivers/Kconfig
• found in Linux kernels: 5.6–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

This Multicast User-Mode Linux network transport allows multiple UMLs (even ones running on different host machines!) to talk to each other over a virtual ethernet network. However, it requires at least one UML with one of the other transports to act as a bridge if any of them need to be able to talk to their hosts or any other IP machines.

To use this, your host kernel(s) must support IP Multicasting.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html That site has examples of the UML command line to use to enable Multicast networking, and notes about the security of this approach.

NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please migrate to UML_NET_VECTOR.

If unsure, say N.

Multicast transport found in arch/um/drivers/Kconfig

The configuration item CONFIG_UML_NET_MCAST:

• prompt: Multicast transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/drivers/Kconfig
• found in Linux kernels: 4.19–4.20, 5.0–5.5

Help text

This Multicast User-Mode Linux network transport allows multiple UMLs (even ones running on different host machines!) to talk to each other over a virtual ethernet network. However, it requires at least one UML with one of the other transports to act as a bridge if any of them need to be able to talk to their hosts or any other IP machines.

To use this, your host kernel(s) must support IP Multicasting.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html That site has examples of the UML command line to use to enable Multicast networking, and notes about the security of this approach.

If you need UMLs on multiple physical hosts to communicate as if they shared an Ethernet network, say Y. If you need to communicate with other IP machines, make sure you select one of the other transports (possibly in addition to Multicast; they're not exclusive). If you don't need to network UMLs say N to each of the transports.

Multicast transport found in arch/um/Kconfig.net

The configuration item CONFIG_UML_NET_MCAST:

• prompt: Multicast transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/Kconfig.net
• found in Linux kernels: 2.6.14–2.6.39, 3.0–3.19, 4.0–4.18

Help text

This Multicast User-Mode Linux network transport allows multiple UMLs (even ones running on different host machines!) to talk to each other over a virtual ethernet network. However, it requires at least one UML with one of the other transports to act as a bridge if any of them need to be able to talk to their hosts or any other IP machines.

To use this, your host kernel(s) must support IP Multicasting.

For more information, see http://user-mode-linux.sourceforge.net/old/networking.html That site has examples of the UML command line to use to enable Multicast networking, and notes about the security of this approach.

If you need UMLs on multiple physical hosts to communicate as if they shared an Ethernet network, say Y. If you need to communicate with other IP machines, make sure you select one of the other transports (possibly in addition to Multicast; they're not exclusive). If you don't need to network UMLs say N to each of the transports.

Multicast transport found in arch/um/Kconfig_net

The configuration item CONFIG_UML_NET_MCAST:

• prompt: Multicast transport
• type: bool
• depends on: CONFIG_UML_NET
• defined in arch/um/Kconfig_net
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.13

Help text

This Multicast User-Mode Linux network transport allows multiple UMLs (even ones running on different host machines!) to talk to each other over a virtual ethernet network. However, it requires at least one UML with one of the other transports to act as a bridge if any of them need to be able to talk to their hosts or any other IP machines.

To use this, your host kernel(s) must support IP Multicasting.

For more information, see http://user-mode-linux.sourceforge.net/networking.html That site has examples of the UML command line to use to enable Multicast networking, and notes about the security of this approach.

If you need UMLs on multiple physical hosts to communicate as if they shared an Ethernet network, say Y. If you need to communicate with other IP machines, make sure you select one of the other transports (possibly in addition to Multicast; they're not exclusive). If you don't need to network UMLs say N to each of the transports.

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: