€•‡pŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”ŒA/translations/zh_CN/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/zh_TW/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/it_IT/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/ja_JP/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/ko_KR/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/pt_BR/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”ŒA/translations/sp_SP/networking/device_drivers/ethernet/intel/e100”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ!SPDX-License-Identifier: GPL-2.0+”h]”hŒ!SPDX-License-Identifier: GPL-2.0+”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hµhhh²hh³Œ[/var/lib/git/docbuild/linux/Documentation/networking/device_drivers/ethernet/intel/e100.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ=Linux Base Driver for the Intel(R) PRO/100 Family of Adapters”h]”hŒ=Linux Base Driver for the Intel(R) PRO/100 Family of Adapters”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ paragraph”“”)”}”(hŒ June 1, 2018”h]”hŒ June 1, 2018”…””}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒContents”h]”hŒContents”…””}”(hhðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhíh²hh³hÇh´K ubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒIn This Release”h]”hÞ)”}”(hjh]”hŒIn This Release”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒIdentifying Your Adapter”h]”hÞ)”}”(hjh]”hŒIdentifying Your Adapter”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒBuilding and Installation”h]”hÞ)”}”(hj5h]”hŒBuilding and Installation”…””}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj3ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒDriver Configuration Parameters”h]”hÞ)”}”(hjLh]”hŒDriver Configuration Parameters”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjJubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒAdditional Configurations”h]”hÞ)”}”(hjch]”hŒAdditional Configurations”…””}”(hjeh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjaubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒ Known Issues”h]”hÞ)”}”(hjzh]”hŒ Known Issues”…””}”(hj|h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjxubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)”}”(hŒ Support ”h]”hÞ)”}”(hŒSupport”h]”hŒSupport”…””}”(hj“h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hþh³hÇh´K hhíh²hubeh}”(h]”Œcontents”ah ]”h"]”Œcontents”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K ubhÉ)”}”(hhh]”(hÎ)”}”(hŒIn This Release”h]”hŒIn This Release”…””}”(hjºh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj·h²hh³hÇh´KubhÞ)”}”(hŒ’This file describes the Linux Base Driver for the Intel(R) PRO/100 Family of Adapters. This driver includes support for Itanium(R)2-based systems.”h]”hŒ’This file describes the Linux Base Driver for the Intel(R) PRO/100 Family of Adapters. This driver includes support for Itanium(R)2-based systems.”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj·h²hubhÞ)”}”(hŒtFor questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/100 adapter.”h]”hŒtFor questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/100 adapter.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj·h²hubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒqThe following features are now available in supported kernels: - Native VLANs - Channel Bonding (teaming) - SNMP ”h]”(hŒterm”“”)”}”(hŒ>The following features are now available in supported kernels:”h]”hŒ>The following features are now available in supported kernels:”…””}”(hjñh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïh³hÇh´K!hjëubhŒ definition”“”)”}”(hhh]”hÿ)”}”(hhh]”(j)”}”(hŒ Native VLANs”h]”hÞ)”}”(hj h]”hŒ Native VLANs”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒChannel Bonding (teaming)”h]”hÞ)”}”(hj h]”hŒChannel Bonding (teaming)”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒSNMP ”h]”hÞ)”}”(hŒSNMP”h]”hŒSNMP”…””}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K!hj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”j­j®uh1hþh³hÇh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jÿhjëubeh}”(h]”h ]”h"]”h$]”h&]”uh1jéh³hÇh´K!hjæubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj·h²hh³Nh´NubhÞ)”}”(hŒlChannel Bonding documentation can be found in the Linux kernel source: /Documentation/networking/bonding.rst”h]”hŒlChannel Bonding documentation can be found in the Linux kernel source: /Documentation/networking/bonding.rst”…””}”(hjeh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K#hj·h²hubeh}”(h]”Œin-this-release”ah ]”h"]”Œin this release”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒIdentifying Your Adapter”h]”hŒIdentifying Your Adapter”…””}”(hj~h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj{h²hh³hÇh´K(ubhÞ)”}”(hŒœFor information on how to identify your adapter, and for the latest Intel network drivers, refer to the Intel Support website: https://www.intel.com/support”h]”(hŒFor information on how to identify your adapter, and for the latest Intel network drivers, refer to the Intel Support website: ”…””}”(hjŒh²hh³Nh´NubhŒ reference”“”)”}”(hŒhttps://www.intel.com/support”h]”hŒhttps://www.intel.com/support”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j˜uh1j”hjŒubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K*hj{h²hubeh}”(h]”Œidentifying-your-adapter”ah ]”h"]”Œidentifying your adapter”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K(ubhÉ)”}”(hhh]”(hÎ)”}”(hŒDriver Configuration Parameters”h]”hŒDriver Configuration Parameters”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj³h²hh³hÇh´K/ubhÞ)”}”(hŒbThe default value for each parameter is generally the recommended setting, unless otherwise noted.”h]”hŒbThe default value for each parameter is generally the recommended setting, unless otherwise noted.”…””}”(hjÄh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K1hj³h²hubjå)”}”(hhh]”(jê)”}”(hXåRx Descriptors: Number of receive descriptors. A receive descriptor is a data structure that describes a receive buffer and its attributes to the network controller. The data in the descriptor is used by the controller to write data from the controller to host memory. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 256. This parameter can be changed using the command:: ethtool -G eth? rx n Where n is the number of desired Rx descriptors. ”h]”(jð)”}”(hŒRx Descriptors:”h]”hŒRx Descriptors:”…””}”(hjÙh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïh³hÇh´K>hjÕubj)”}”(hhh]”(hÞ)”}”(hXŠNumber of receive descriptors. A receive descriptor is a data structure that describes a receive buffer and its attributes to the network controller. The data in the descriptor is used by the controller to write data from the controller to host memory. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 256. This parameter can be changed using the command::”h]”hX‰Number of receive descriptors. A receive descriptor is a data structure that describes a receive buffer and its attributes to the network controller. The data in the descriptor is used by the controller to write data from the controller to host memory. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 256. This parameter can be changed using the command:”…””}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K5hjçubhŒ literal_block”“”)”}”(hŒethtool -G eth? rx n”h]”hŒethtool -G eth? rx n”…””}”hjúsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´Khjçubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÿhjÕubeh}”(h]”h ]”h"]”h$]”h&]”uh1jéh³hÇh´K>hjÒubjê)”}”(hXëTx Descriptors: Number of transmit descriptors. A transmit descriptor is a data structure that describes a transmit buffer and its attributes to the network controller. The data in the descriptor is used by the controller to read data from the host memory to the controller. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 128. This parameter can be changed using the command:: ethtool -G eth? tx n Where n is the number of desired Tx descriptors. ”h]”(jð)”}”(hŒTx Descriptors:”h]”hŒTx Descriptors:”…””}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïh³hÇh´KJhj"ubj)”}”(hhh]”(hÞ)”}”(hXNumber of transmit descriptors. A transmit descriptor is a data structure that describes a transmit buffer and its attributes to the network controller. The data in the descriptor is used by the controller to read data from the host memory to the controller. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 128. This parameter can be changed using the command::”h]”hXNumber of transmit descriptors. A transmit descriptor is a data structure that describes a transmit buffer and its attributes to the network controller. The data in the descriptor is used by the controller to read data from the host memory to the controller. In the 3.x.x driver the valid range for this parameter is 64-256. The default value is 128. This parameter can be changed using the command:”…””}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KAhj4ubjù)”}”(hŒethtool -G eth? tx n”h]”hŒethtool -G eth? tx n”…””}”hjEsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´KHhj4ubhÞ)”}”(hŒ0Where n is the number of desired Tx descriptors.”h]”hŒ0Where n is the number of desired Tx descriptors.”…””}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KJhj4ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÿhj"ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jéh³hÇh´KJhjÒh²hubjê)”}”(hX/Speed/Duplex: The driver auto-negotiates the link speed and duplex settings by default. The ethtool utility can be used as follows to force speed/duplex.:: ethtool -s eth? autoneg off speed {10|100} duplex {full|half} NOTE: setting the speed/duplex to incorrect values will cause the link to fail. ”h]”(jð)”}”(hŒ Speed/Duplex:”h]”hŒ Speed/Duplex:”…””}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïh³hÇh´KShjmubj)”}”(hhh]”(hÞ)”}”(hŒThe driver auto-negotiates the link speed and duplex settings by default. The ethtool utility can be used as follows to force speed/duplex.::”h]”hŒŒThe driver auto-negotiates the link speed and duplex settings by default. The ethtool utility can be used as follows to force speed/duplex.:”…””}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KMhjubjù)”}”(hŒ>ethtool -s eth? autoneg off speed {10|100} duplex {full|half}”h]”hŒ>ethtool -s eth? autoneg off speed {10|100} duplex {full|half}”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´KPhjubhÞ)”}”(hŒONOTE: setting the speed/duplex to incorrect values will cause the link to fail.”h]”hŒONOTE: setting the speed/duplex to incorrect values will cause the link to fail.”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KRhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÿhjmubeh}”(h]”h ]”h"]”h$]”h&]”uh1jéh³hÇh´KShjÒh²hubjê)”}”(hŒÏEvent Log Message Level: The driver uses the message level flag to log events to syslog. The message level can be set at driver load time. It can also be set using the command:: ethtool -s eth? msglvl n ”h]”(jð)”}”(hŒEvent Log Message Level:”h]”hŒEvent Log Message Level:”…””}”(hj¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïh³hÇh´K[hj¸ubj)”}”(hhh]”(hÞ)”}”(hŒ˜The driver uses the message level flag to log events to syslog. The message level can be set at driver load time. It can also be set using the command::”h]”hŒ—The driver uses the message level flag to log events to syslog. The message level can be set at driver load time. It can also be set using the command:”…””}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KVhjÊubjù)”}”(hŒethtool -s eth? msglvl n”h]”hŒethtool -s eth? msglvl n”…””}”hjÛsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´KZhjÊubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÿhj¸ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jéh³hÇh´K[hjÒh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jähj³h²hh³hÇh´Nubeh}”(h]”Œdriver-configuration-parameters”ah ]”h"]”Œdriver configuration parameters”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K/ubhÉ)”}”(hhh]”(hÎ)”}”(hŒAdditional Configurations”h]”hŒAdditional Configurations”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´K^ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ1Configuring the Driver on Different Distributions”h]”hŒ1Configuring the Driver on Different Distributions”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´KaubhÞ)”}”(hXlConfiguring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to `/etc/modprobe.d/*.conf` as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Intel PRO/100 Family of Adapters is e100.”h]”(hŒ«Configuring a network driver to load properly when the system is started is distribution dependent. Typically, the configuration process involves adding an alias line to ”…””}”(hj%h²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒ`/etc/modprobe.d/*.conf`”h]”hŒ/etc/modprobe.d/*.conf”…””}”(hj/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j-hj%ubhX© as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Intel PRO/100 Family of Adapters is e100.”…””}”(hj%h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kchjh²hubhÞ)”}”(hŒ—As an example, if you install the e100 driver for two PRO/100 adapters (eth0 and eth1), add the following to a configuration file in /etc/modprobe.d/::”h]”hŒ–As an example, if you install the e100 driver for two PRO/100 adapters (eth0 and eth1), add the following to a configuration file in /etc/modprobe.d/:”…””}”(hjGh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kmhjh²hubjù)”}”(hŒalias eth0 e100 alias eth1 e100”h]”hŒalias eth0 e100 alias eth1 e100”…””}”hjUsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´Kqhjh²hubeh}”(h]”Œ1configuring-the-driver-on-different-distributions”ah ]”h"]”Œ1configuring the driver on different distributions”ah$]”h&]”uh1hÈhjh²hh³hÇh´KaubhÉ)”}”(hhh]”(hÎ)”}”(hŒViewing Link Messages”h]”hŒViewing Link Messages”…””}”(hjnh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjkh²hh³hÇh´KuubhÞ)”}”(hŒÚIn order to see link messages and other Intel driver information on your console, you must set the dmesg level up to six. This can be done by entering the following on the command line before loading the e100 driver::”h]”hŒÙIn order to see link messages and other Intel driver information on your console, you must set the dmesg level up to six. This can be done by entering the following on the command line before loading the e100 driver:”…””}”(hj|h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kwhjkh²hubjù)”}”(hŒ dmesg -n 6”h]”hŒ dmesg -n 6”…””}”hjŠsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´K|hjkh²hubhÞ)”}”(hŒmIf you wish to see all messages issued by the driver, including debug messages, set the dmesg level to eight.”h]”hŒmIf you wish to see all messages issued by the driver, including debug messages, set the dmesg level to eight.”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K~hjkh²hubhÞ)”}”(hŒ/NOTE: This setting is not saved across reboots.”h]”hŒ/NOTE: This setting is not saved across reboots.”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjkh²hubeh}”(h]”Œviewing-link-messages”ah ]”h"]”Œviewing link messages”ah$]”h&]”uh1hÈhjh²hh³hÇh´KuubhÉ)”}”(hhh]”(hÎ)”}”(hŒethtool”h]”hŒethtool”…””}”(hj¿h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj¼h²hh³hÇh´K„ubhÞ)”}”(hŒÈThe driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. The ethtool version 1.6 or later is required for this functionality.”h]”hŒÈThe driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. The ethtool version 1.6 or later is required for this functionality.”…””}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K†hj¼h²hubhÞ)”}”(hŒdThe latest release of ethtool can be found from https://www.kernel.org/pub/software/network/ethtool/”h]”(hŒ0The latest release of ethtool can be found from ”…””}”(hjÛh²hh³Nh´Nubj•)”}”(hŒ4https://www.kernel.org/pub/software/network/ethtool/”h]”hŒ4https://www.kernel.org/pub/software/network/ethtool/”…””}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jåuh1j”hjÛubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KŠhj¼h²hubeh}”(h]”Œethtool”ah ]”h"]”Œethtool”ah$]”h&]”uh1hÈhjh²hh³hÇh´K„ubhÉ)”}”(hhh]”(hÎ)”}”(hŒEnabling Wake on LAN (WoL)”h]”hŒEnabling Wake on LAN (WoL)”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´KŽubhÞ)”}”(hX@WoL is provided through the ethtool utility. For instructions on enabling WoL with ethtool, refer to the ethtool man page. WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e100 driver must be loaded when shutting down or rebooting the system.”h]”hX@WoL is provided through the ethtool utility. For instructions on enabling WoL with ethtool, refer to the ethtool man page. WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e100 driver must be loaded when shutting down or rebooting the system.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjh²hubeh}”(h]”Œenabling-wake-on-lan-wol”ah ]”h"]”Œenabling wake on lan (wol)”ah$]”h&]”uh1hÈhjh²hh³hÇh´KŽubhÉ)”}”(hhh]”(hÎ)”}”(hŒNAPI”h]”hŒNAPI”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj'h²hh³hÇh´K–ubhÞ)”}”(hŒ7NAPI (Rx polling mode) is supported in the e100 driver.”h]”hŒ7NAPI (Rx polling mode) is supported in the e100 driver.”…””}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K˜hj'h²hubhÞ)”}”(hŒISee :ref:`Documentation/networking/napi.rst ` for more information.”h]”(hŒSee ”…””}”(hjFh²hh³Nh´Nubh)”}”(hŒ/:ref:`Documentation/networking/napi.rst `”h]”hŒinline”“”)”}”(hjPh]”hŒ!Documentation/networking/napi.rst”…””}”(hjTh²hh³Nh´Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jRhjNubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œ-networking/device_drivers/ethernet/intel/e100”Œ refdomain”j_Œreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆŒ reftarget”Œnapi”uh1hh³hÇh´KšhjFubhŒ for more information.”…””}”(hjFh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kšhj'h²hubeh}”(h]”Œnapi”ah ]”h"]”Œnapi”ah$]”h&]”uh1hÈhjh²hh³hÇh´K–ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ6Multiple Interfaces on Same Ethernet Broadcast Network”h]”hŒ6Multiple Interfaces on Same Ethernet Broadcast Network”…””}”(hjˆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj…h²hh³hÇh´KubhÞ)”}”(hX@Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.”h]”hX@Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic.”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KŸhj…h²hubhÞ)”}”(hŒLIf you have multiple interfaces in a server, either turn on ARP filtering by”h]”hŒLIf you have multiple interfaces in a server, either turn on ARP filtering by”…””}”(hj¤h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¥hj…h²hubhŒenumerated_list”“”)”}”(hhh]”(j)”}”(hŒ…entering:: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter (this only works if your kernel's version is higher than 2.4.5), or ”h]”(hÞ)”}”(hŒ entering::”h]”hŒ entering:”…””}”(hj»h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¨hj·ubjù)”}”(hŒ/echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter”h]”hŒ/echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter”…””}”hjÉsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jøh³hÇh´Kªhj·ubhÞ)”}”(hŒC(this only works if your kernel's version is higher than 2.4.5), or”h]”hŒE(this only works if your kernel’s version is higher than 2.4.5), or”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¬hj·ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj´h²hh³hÇh´Nubj)”}”(hŒ}installing the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs). ”h]”hÞ)”}”(hŒ{installing the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).”h]”hŒ{installing the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs).”…””}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K®hjëubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj´h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”Œ(”Œsuffix”Œ)”uh1j²hj…h²hh³hÇh´K¨ubeh}”(h]”Œ6multiple-interfaces-on-same-ethernet-broadcast-network”ah ]”h"]”Œ6multiple interfaces on same ethernet broadcast network”ah$]”h&]”uh1hÈhjh²hh³hÇh´Kubeh}”(h]”Œadditional-configurations”ah ]”h"]”Œadditional configurations”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K^ubhÉ)”}”(hhh]”(hÎ)”}”(hŒSupport”h]”hŒSupport”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´K³ubhÞ)”}”(hŒ[For general information, go to the Intel support website at: https://www.intel.com/support/”h]”(hŒ=For general information, go to the Intel support website at: ”…””}”(hj0h²hh³Nh´Nubj•)”}”(hŒhttps://www.intel.com/support/”h]”hŒhttps://www.intel.com/support/”…””}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j:uh1j”hj0ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K´hjh²hubhÞ)”}”(hŒÀIf an issue is identified with the released source code on a supported kernel with a supported adapter, email the specific information related to the issue to intel-wired-lan@lists.osuosl.org.”h]”(hŒŸIf an issue is identified with the released source code on a supported kernel with a supported adapter, email the specific information related to the issue to ”…””}”(hjMh²hh³Nh´Nubj•)”}”(hŒ intel-wired-lan@lists.osuosl.org”h]”hŒ intel-wired-lan@lists.osuosl.org”…””}”(hjUh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ'mailto:intel-wired-lan@lists.osuosl.org”uh1j”hjMubhŒ.”…””}”(hjMh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K·hjh²hubeh}”(h]”Œsupport”ah ]”h"]”Œsupport”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K³ubeh}”(h]”Œ