^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0-only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) # Network device configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) menuconfig NETDEVICES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) default y if UML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) depends on NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) bool "Network device support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) You can say N here if you don't intend to connect your Linux box to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) any other computer at all.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) You'll have to say Y if your computer contains a network card that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) you want to use under Linux. If you are going to run SLIP or PPP over
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) telephone line or null modem cable you need say Y here. Connecting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) two machines with parallel ports using PLIP needs this, as well as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) AX.25/KISS for sending Internet traffic over amateur radio links.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) See also "The Linux Network Administrator's Guide" by Olaf Kirch and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) Terry Dawson. Available at <http://www.tldp.org/guides.html>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) # All the following symbols are dependent on NETDEVICES - do not repeat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) # that for each of the symbols.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) if NETDEVICES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) config MII
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) config NET_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) bool "Network core driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) You can say N here if you do not intend to use any of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) networking core drivers (i.e. VLAN, bridging, bonding, etc.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) if NET_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) config BONDING
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) tristate "Bonding driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) depends on IPV6 || IPV6=n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) Channels together. This is called 'Etherchannel' by Cisco,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) The driver supports multiple bonding modes to allow for both high
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) performance and high availability operation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) Refer to <file:Documentation/networking/bonding.rst> for more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) information.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) will be called bonding.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) config DUMMY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) tristate "Dummy net driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) This is essentially a bit-bucket device (i.e. traffic you send to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) this device is consigned into oblivion) with a configurable IP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) address. It is most commonly used in order to make your currently
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) inactive SLIP address seem like a real address for local programs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) If you use SLIP or PPP, you might want to say Y here. It won't
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) enlarge your kernel. What a deal. Read about it in the Network
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) Administrator's Guide, available from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) <http://www.tldp.org/docs.html#guide>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) will be called dummy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) config WIREGUARD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) tristate "WireGuard secure network tunnel"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) depends on NET && INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) depends on IPV6 || !IPV6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) select NET_UDP_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) select DST_CACHE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) select CRYPTO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) select CRYPTO_LIB_CURVE25519
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) select CRYPTO_LIB_CHACHA20POLY1305
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) select CRYPTO_LIB_BLAKE2S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) select CRYPTO_CHACHA20_X86_64 if X86 && 64BIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) select CRYPTO_POLY1305_X86_64 if X86 && 64BIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) select CRYPTO_BLAKE2S_X86 if X86 && 64BIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) select CRYPTO_CURVE25519_X86 if X86 && 64BIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) select ARM_CRYPTO if ARM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) select ARM64_CRYPTO if ARM64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) select CRYPTO_CHACHA20_NEON if ARM || (ARM64 && KERNEL_MODE_NEON)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) select CRYPTO_POLY1305_NEON if ARM64 && KERNEL_MODE_NEON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) select CRYPTO_POLY1305_ARM if ARM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) select CRYPTO_BLAKE2S_ARM if ARM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) select CRYPTO_POLY1305_MIPS if MIPS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) WireGuard is a secure, fast, and easy to use replacement for IPSec
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) that uses modern cryptography and clever networking tricks. It's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) designed to be fairly general purpose and abstract enough to fit most
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) use cases, while at the same time remaining extremely simple to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) configure. See www.wireguard.com for more info.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) It's safe to say Y or M here, as the driver is very lightweight and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) is only in use when an administrator chooses to add an interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) config WIREGUARD_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) bool "Debugging checks and verbose messages"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) depends on WIREGUARD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) This will write log messages for handshake and other events
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) that occur for a WireGuard interface. It will also perform some
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) extra validation checks and unit tests at various points. This is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) only useful for debugging.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) Say N here unless you know what you're doing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) config EQUALIZER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) tristate "EQL (serial line load balancing) support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) If you have two serial connections to some other computer (this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) usually requires two modems and two telephone lines) and you use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) SLIP (the protocol for sending Internet traffic over telephone
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) lines) or PPP (a better SLIP) on them, you can make them behave like
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) one double speed connection using this driver. Naturally, this has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) to be supported at the other end as well, either with a similar EQL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) Linux driver or with a Livingston Portmaster 2e.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) Say Y if you want this and read
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) <file:Documentation/networking/eql.rst>. You may also want to read
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) section 6.2 of the NET-3-HOWTO, available from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) <http://www.tldp.org/docs.html#howto>.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) will be called eql. If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) config NET_FC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) bool "Fibre Channel driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) depends on SCSI && PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) Fibre Channel is a high speed serial protocol mainly used to connect
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) large storage devices to the computer; it is compatible with and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) intended to replace SCSI.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) If you intend to use Fibre Channel, you need to have a Fibre channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) adaptor card in your computer; say Y here and to the driver for your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) adaptor below. You also should have said Y to "SCSI support" and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) "SCSI generic support".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) config IFB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) tristate "Intermediate Functional Block support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) depends on NET_ACT_MIRRED || NFT_FWD_NETDEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) select NET_REDIRECT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) This is an intermediate driver that allows sharing of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) resources.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) will be called ifb. If you want to use more than one ifb
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) device at a time, you need to compile this driver as a module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) Instead of 'ifb', the devices will then be called 'ifb0',
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 'ifb1' etc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) Look at the iproute2 documentation directory for usage etc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) source "drivers/net/team/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) config MACVLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) tristate "MAC-VLAN support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) This allows one to create virtual interfaces that map packets to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) or from specific MAC addresses to a particular interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) Macvlan devices can be added using the "ip" command from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) iproute2 package starting with the iproute2-2.6.23 release:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) will be called macvlan.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) config MACVTAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) tristate "MAC-VLAN based tap driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) depends on MACVLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) select TAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) This adds a specialized tap character device driver that is based
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) on the MAC-VLAN network interface, called macvtap. A macvtap device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) can be added in the same way as a macvlan device, using 'type
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) macvtap', and then be accessed through the tap user space interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) will be called macvtap.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) config IPVLAN_L3S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) depends on NETFILTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) depends on IPVLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) def_bool y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) select NET_L3_MASTER_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) config IPVLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) tristate "IP-VLAN support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) depends on IPV6 || !IPV6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) This allows one to create virtual devices off of a main interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) on packets. All interfaces (including the main interface) share L2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) making it transparent to the connected L2 switch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) Ipvlan devices can be added using the "ip" command from the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) iproute2 package starting with the iproute2-3.19 release:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) "ip link add link <main-dev> [ NAME ] type ipvlan"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) will be called ipvlan.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) config IPVTAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) tristate "IP-VLAN based tap driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) depends on IPVLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) select TAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) This adds a specialized tap character device driver that is based
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) on the IP-VLAN network interface, called ipvtap. An ipvtap device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) can be added in the same way as a ipvlan device, using 'type
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) ipvtap', and then be accessed through the tap user space interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) will be called ipvtap.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) config VXLAN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) tristate "Virtual eXtensible Local Area Network (VXLAN)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) select NET_UDP_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) select GRO_CELLS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) This allows one to create vxlan virtual interfaces that provide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) Layer 2 Networks over Layer 3 Networks. VXLAN is often used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) to tunnel virtual network infrastructure in virtualized environments.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) For more information see:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) will be called vxlan.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) config GENEVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) tristate "Generic Network Virtualization Encapsulation"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) depends on IPV6 || !IPV6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) select NET_UDP_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) select GRO_CELLS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) This allows one to create geneve virtual interfaces that provide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) Layer 2 Networks over Layer 3 Networks. GENEVE is often used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) to tunnel virtual network infrastructure in virtualized environments.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) For more information see:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) http://tools.ietf.org/html/draft-gross-geneve-02
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) will be called geneve.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) config BAREUDP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) tristate "Bare UDP Encapsulation"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) depends on IPV6 || !IPV6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) select NET_UDP_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) select GRO_CELLS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) This adds a bare UDP tunnel module for tunnelling different
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) will be called bareudp.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) config GTP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) tristate "GPRS Tunneling Protocol datapath (GTP-U)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) select NET_UDP_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) This allows one to create gtp virtual interfaces that provide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) is used to prevent subscribers from accessing mobile carrier core
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) network infrastructure. This driver requires a userspace software that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) implements the signaling protocol (GTP-C) to update its PDP context
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) base, such as OpenGGSN <http://git.osmocom.org/openggsn/). This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) tunneling protocol is implemented according to the GSM TS 09.60 and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) 3GPP TS 29.060 standards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) To compile this drivers as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291) wil be called gtp.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) config MACSEC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) select CRYPTO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) select CRYPTO_AES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) select CRYPTO_GCM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) select GRO_CELLS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) MACsec is an encryption standard for Ethernet.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) config NETCONSOLE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) tristate "Network console logging support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) If you want to log kernel messages over the network, enable this.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) See <file:Documentation/networking/netconsole.rst> for details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) config NETCONSOLE_DYNAMIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) bool "Dynamic reconfiguration of logging targets"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) !(NETCONSOLE=y && CONFIGFS_FS=m)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) This option enables the ability to dynamically reconfigure target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) parameters (interface, IP addresses, port numbers, MAC addresses)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) at runtime through a userspace interface exported using configfs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) See <file:Documentation/networking/netconsole.rst> for details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) config NETPOLL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) def_bool NETCONSOLE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) select SRCU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) config NET_POLL_CONTROLLER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) def_bool NETPOLL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) config NTB_NETDEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) tristate "Virtual Ethernet over NTB Transport"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) depends on NTB_TRANSPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) config RIONET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) tristate "RapidIO Ethernet over messaging driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) depends on RAPIDIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) config RIONET_TX_SIZE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) int "Number of outbound queue entries"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) depends on RIONET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) default "128"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) config RIONET_RX_SIZE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) int "Number of inbound queue entries"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340) depends on RIONET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) default "128"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343) config TUN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) tristate "Universal TUN/TAP device driver support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) select CRC32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) TUN/TAP provides packet reception and transmission for user space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) programs. It can be viewed as a simple Point-to-Point or Ethernet
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) device, which instead of receiving packets from a physical media,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) receives them from user space program and instead of sending packets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352) via physical media writes them to the user space program.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) When a program opens /dev/net/tun, driver creates and registers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355) corresponding net device tunX or tapX. After a program closed above
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) devices, driver will automatically delete tunXX or tapXX device and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) all routes corresponding to it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) Please read <file:Documentation/networking/tuntap.rst> for more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) information.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) will be called tun.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) If you don't know what to use this for, you don't need it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367) config TAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) This option is selected by any driver implementing tap user space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) interface for a virtual interface to re-use core tap functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) config TUN_VNET_CROSS_LE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) bool "Support for cross-endian vnet headers on little-endian kernels"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) This option allows TUN/TAP and MACVTAP device drivers in a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) little-endian kernel to parse vnet headers that come from a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) big-endian legacy virtio device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) Userspace programs can control the feature using the TUNSETVNETBE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) and TUNGETVNETBE ioctls.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) Unless you have a little-endian system hosting a big-endian virtual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) machine with a legacy virtio NIC, you should say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) config VETH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) tristate "Virtual ethernet pair device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) This device is a local ethernet tunnel. Devices are created in pairs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) When one end receives the packet it appears on its pair and vice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) versa.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) config VIRTIO_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) tristate "Virtio network driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396) depends on VIRTIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) select NET_FAILOVER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) This is the virtual network driver for virtio. It can be used with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) QEMU based VMMs (like KVM or Xen). Say Y or M.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402) config NLMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) tristate "Virtual netlink monitoring device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) This option enables a monitoring net device for netlink skbs. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406) purpose of this is to analyze netlink messages with packet sockets.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) Thus applications like tcpdump will be able to see local netlink
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) messages if they tap into the netlink device, record pcaps for further
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) diagnostics, etc. This is mostly intended for developers or support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) to debug netlink issues. If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) config NET_VRF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) tristate "Virtual Routing and Forwarding (Lite)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) depends on IP_MULTIPLE_TABLES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) depends on NET_L3_MASTER_DEV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) depends on IPV6 || IPV6=n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) depends on IPV6_MULTIPLE_TABLES || IPV6=n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) This option enables the support for mapping interfaces into VRF's. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) support enables VRF devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) config VSOCKMON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) tristate "Virtual vsock monitoring device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) depends on VHOST_VSOCK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) This option enables a monitoring net device for vsock sockets. It is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427) mostly intended for developers or support to debug vsock issues. If
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) endif # NET_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) config SUNGEM_PHY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) source "drivers/net/arcnet/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) source "drivers/atm/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) source "drivers/net/caif/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441) source "drivers/net/dsa/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) source "drivers/net/ethernet/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) source "drivers/net/fddi/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) source "drivers/net/hippi/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) source "drivers/net/ipa/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451) config NET_SB1000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) tristate "General Instruments Surfboard 1000"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) depends on PNP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) This is a driver for the General Instrument (also known as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) NextLevel) SURFboard 1000 internal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457) cable modem. This is an ISA card which is used by a number of cable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458) TV companies to provide cable modem access. It's a one-way
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) downstream-only cable modem, meaning that your upstream net link is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) provided by your regular phone modem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) At present this driver only compiles as a module, so say M here if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) you have this card. The module will be called sb1000. Then read
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) <file:Documentation/networking/device_drivers/cable/sb1000.rst> for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) information on how to use this module, as it needs special ppp
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) scripts for establishing a connection. Further documentation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467) and the necessary scripts can be found at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469) <http://www.jacksonville.net/~fventuri/>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470) <http://home.adelphia.net/~siglercm/sb1000.html>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471) <http://linuxpower.cx/~cable/>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) If you don't have this card, of course say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475) source "drivers/net/phy/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477) source "drivers/net/mdio/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479) source "drivers/net/pcs/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) source "drivers/net/plip/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483) source "drivers/net/ppp/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485) source "drivers/net/slip/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487) source "drivers/s390/net/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) source "drivers/net/usb/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491) source "drivers/net/wireless/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493) source "drivers/net/wimax/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495) source "drivers/net/wan/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497) source "drivers/net/ieee802154/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499) config XEN_NETDEV_FRONTEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500) tristate "Xen network device frontend driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501) depends on XEN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502) select XEN_XENBUS_FRONTEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503) select PAGE_POOL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) This driver provides support for Xen paravirtual network
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507) devices exported by a Xen network driver domain (often
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508) domain 0).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510) The corresponding Linux backend driver is enabled by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511) CONFIG_XEN_NETDEV_BACKEND option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513) If you are compiling a kernel for use as Xen guest, you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 514) should say Y here. To compile this driver as a module, chose
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 515) M here: the module will be called xen-netfront.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 516)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 517) config XEN_NETDEV_BACKEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 518) tristate "Xen backend network device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 519) depends on XEN_BACKEND
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 520) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 521) This driver allows the kernel to act as a Xen network driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 522) domain which exports paravirtual network devices to other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 523) Xen domains. These devices can be accessed by any operating
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 524) system that implements a compatible front end.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 525)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 526) The corresponding Linux frontend driver is enabled by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 527) CONFIG_XEN_NETDEV_FRONTEND configuration option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 528)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 529) The backend driver presents a standard network device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 530) endpoint for each paravirtual network device to the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 531) domain network stack. These can then be bridged or routed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 532) etc in order to provide full network connectivity.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 533)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 534) If you are compiling a kernel to run in a Xen network driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 535) domain (often this is domain 0) you should say Y here. To
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 536) compile this driver as a module, chose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 537) will be called xen-netback.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 538)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 539) config VMXNET3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 540) tristate "VMware VMXNET3 ethernet driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 541) depends on PCI && INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 542) depends on !(PAGE_SIZE_64KB || ARM64_64K_PAGES || \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 543) IA64_PAGE_SIZE_64KB || MICROBLAZE_64K_PAGES || \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 544) PARISC_PAGE_SIZE_64KB || PPC_64K_PAGES)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 545) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 546) This driver supports VMware's vmxnet3 virtual ethernet NIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 547) To compile this driver as a module, choose M here: the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 548) module will be called vmxnet3.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 549)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 550) config FUJITSU_ES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 551) tristate "FUJITSU Extended Socket Network Device driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 552) depends on ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 553) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 554) This driver provides support for Extended Socket network device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 555) on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 556)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 557) config USB4_NET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 558) tristate "Networking over USB4 and Thunderbolt cables"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 559) depends on USB4 && INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 560) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 561) Select this if you want to create network between two computers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 562) over a USB4 and Thunderbolt cables. The driver supports Apple
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 563) ThunderboltIP protocol and allows communication with any host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 564) supporting the same protocol including Windows and macOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 565)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 566) To compile this driver a module, choose M here. The module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 567) called thunderbolt-net.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 568)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 569) source "drivers/net/hyperv/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 570)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 571) config NETDEVSIM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 572) tristate "Simulated networking device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 573) depends on DEBUG_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 574) depends on INET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 575) depends on IPV6 || IPV6=n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 576) select NET_DEVLINK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 577) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 578) This driver is a developer testing tool and software model that can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 579) be used to test various control path networking APIs, especially
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 580) HW-offload related.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 581)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 582) To compile this driver as a module, choose M here: the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 583) will be called netdevsim.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 584)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 585) config NET_FAILOVER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 586) tristate "Failover driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 587) select FAILOVER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 588) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 589) This provides an automated failover mechanism via APIs to create
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 590) and destroy a failover master netdev and manages a primary and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 591) standby slave netdevs that get registered via the generic failover
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 592) infrastructure. This can be used by paravirtual drivers to enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 593) an alternate low latency datapath. It also enables live migration of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 594) a VM with direct attached VF by failing over to the paravirtual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 595) datapath when the VF is unplugged.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 596)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 597) endif # NETDEVICES
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags