CONFIG_ETHERTAP: Ethertap network tap

General informations

The Linux kernel configuration item CONFIG_ETHERTAP has multiple definitions:

Ethertap network tap found in drivers/net/Kconfig

The configuration item CONFIG_ETHERTAP:

• prompt: Ethertap network tap
• type: tristate
• depends on: CONFIG_NETDEVICES && CONFIG_EXPERIMENTAL && CONFIG_NETLINK_DEV
• defined in drivers/net/Kconfig
• found in Linux kernels: 2.6.0–2.6.11
• modules built: ethertap, ethertap, ethertap

Help text

If you say Y here (and have said Y to "Kernel/User network link driver", above) and create a character special file /dev/tap0 with major number 36 and minor number 16 using mknod ("man mknod"), you will be able to have a user space program read and write raw Ethernet frames from/to that special file. tap0 can be configured with ifconfig and route like any other Ethernet device but it is not connected to any physical LAN; everything written by the user to /dev/tap0 is treated by the kernel as if it had come in from a LAN to the device tap0; everything the kernel wants to send out over the device tap0 can instead be read by the user from /dev/tap0: the user mode program replaces the LAN that would be attached to an ordinary Ethernet device. Please read the file Documentation/networking/ethertap.txt for more information.

To compile this driver as a module, choose M here: the module will be called ethertap.

If you don't know what to use this for, you don't need it.

Ethertap network tap (OBSOLETE) found in arch/um/Kconfig_net

The configuration item CONFIG_ETHERTAP:

• prompt: Ethertap network tap (OBSOLETE)
• type: tristate
• depends on: CONFIG_EXPERIMENTAL && CONFIG_NETLINK
• defined in arch/um/Kconfig_net
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.8
• modules built: ethertap, ethertap, ethertap

Help text

(none)

Ethertap network tap (OBSOLETE) found in drivers/net/Kconfig

The configuration item CONFIG_ETHERTAP:

• prompt: Ethertap network tap (OBSOLETE)
• type: tristate
• depends on: CONFIG_NETDEVICES && CONFIG_EXPERIMENTAL
• defined in drivers/net/Kconfig
• found in Linux kernels: 2.5.45–2.5.75
• modules built: ethertap, ethertap, ethertap

Help text

If you say Y here (and have said Y to "Kernel/User network link driver", above) and create a character special file /dev/tap0 with major number 36 and minor number 16 using mknod ("man mknod"), you will be able to have a user space program read and write raw Ethernet frames from/to that special file. tap0 can be configured with ifconfig and route like any other Ethernet device but it is not connected to any physical LAN; everything written by the user to /dev/tap0 is treated by the kernel as if it had come in from a LAN to the device tap0; everything the kernel wants to send out over the device tap0 can instead be read by the user from /dev/tap0: the user mode program replaces the LAN that would be attached to an ordinary Ethernet device. Please read the file Documentation/networking/ethertap.txt for more information.

This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ethertap. If you want to compile it as a module, say M here and read Documentation/modules.txt.

If you don't know what to use this for, you don't need it.

Ethertap network tap (OBSOLETE) found in arch/sparc/Kconfig

The configuration item CONFIG_ETHERTAP:

• prompt: Ethertap network tap (OBSOLETE)
• type: tristate
• depends on: CONFIG_NETDEVICES && CONFIG_EXPERIMENTAL && CONFIG_NETLINK
• defined in arch/sparc/Kconfig
• found in Linux kernels: 2.5.45–2.5.54
• modules built: ethertap, ethertap, ethertap

Help text

If you say Y here (and have said Y to "Kernel/User network link driver", above) and create a character special file /dev/tap0 with major number 36 and minor number 16 using mknod ("man mknod"), you will be able to have a user space program read and write raw Ethernet frames from/to that special file. tap0 can be configured with ifconfig and route like any other Ethernet device but it is not connected to any physical LAN; everything written by the user to /dev/tap0 is treated by the kernel as if it had come in from a LAN to the device tap0; everything the kernel wants to send out over the device tap0 can instead be read by the user from /dev/tap0: the user mode program replaces the LAN that would be attached to an ordinary Ethernet device. Please read the file Documentation/networking/ethertap.txt for more information.

This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ethertap.o. If you want to compile it as a module, say M here and read Documentation/modules.txt.

If you don't know what to use this for, you don't need it.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module ethertap CONFIG_ETHERTAP : arch/sparc/Kconfig : "Ethertap network tap (OBSOLETE)" # in 2.5.45–2.5.54
• lkddb module ethertap CONFIG_ETHERTAP : arch/um/Kconfig_net : "Ethertap network tap (OBSOLETE)" # in 2.5.45–2.5.75, 2.6.0–2.6.8
• lkddb module ethertap CONFIG_ETHERTAP : drivers/net/Kconfig : "Ethertap network tap" # in 2.5.45–2.5.75, 2.6.0–2.6.11

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: