Kconfig 20 KB

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