Difference between revisions of "Ethernet devices named tmpXXXXX"
From Notes_Wiki
m |
m |
||
| Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[System troubleshooting]] > [[Ethernet devices named __tmpXXXXX]] | |||
Ethernet devices are named __tmpXXXXX in Linux if corresponding ifcfg-eth<n> file is missing or HWADDR= is not present in the configuration file. Hence if one faces problem where ethernet devices have names like __TmpXXXXX and not eth<n> then creating network interface configuration file wtih proper HWADDR can solve the problem. You would have to do '<tt>service network restart</tt>' after creating the file to make name correction take effect. | Ethernet devices are named __tmpXXXXX in Linux if corresponding ifcfg-eth<n> file is missing or HWADDR= is not present in the configuration file. Hence if one faces problem where ethernet devices have names like __TmpXXXXX and not eth<n> then creating network interface configuration file wtih proper HWADDR can solve the problem. You would have to do '<tt>service network restart</tt>' after creating the file to make name correction take effect. | ||
| Line 8: | Line 7: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[System troubleshooting]] > [[Ethernet devices named __tmpXXXXX]] | |||
Latest revision as of 11:36, 28 July 2022
Home > CentOS > CentOS 6.x > System troubleshooting > Ethernet devices named __tmpXXXXX
Ethernet devices are named __tmpXXXXX in Linux if corresponding ifcfg-eth<n> file is missing or HWADDR= is not present in the configuration file. Hence if one faces problem where ethernet devices have names like __TmpXXXXX and not eth<n> then creating network interface configuration file wtih proper HWADDR can solve the problem. You would have to do 'service network restart' after creating the file to make name correction take effect.
Home > CentOS > CentOS 6.x > System troubleshooting > Ethernet devices named __tmpXXXXX
