- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- network-scripts/ifcfg-eth# and ifconfig output are...
Operating System - Linux
1819500
Members
3130
Online
109603
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 11:04 AM
12-16-2010 11:04 AM
network-scripts/ifcfg-eth# and ifconfig output are different
Hi
My ifconfig displays these nics:
_tmp83838383838 - buzilla bug 224662 & 9
Has a hwaddress.
eth0 - primary - up
eth1 - no ifgcfg-eth1
eth2 - no ifgcfg-eth2
sit0 - not in network-scripts
lo0 - N/A
/proc/net/dev matches up with ifconfig as it should.
/etc/modprobe.conf displays:
alias eth0 e1000
alias eth1 e1000
alias eth2 tg3
alias eth3 tg3
a) looking for patch to _tmp83838 bug 224662 & 9
b) Why doesn't ifconfig match up with network-scripts?
Followup to :
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1459973
My ifconfig displays these nics:
_tmp83838383838 - buzilla bug 224662 & 9
Has a hwaddress.
eth0 - primary - up
eth1 - no ifgcfg-eth1
eth2 - no ifgcfg-eth2
sit0 - not in network-scripts
lo0 - N/A
/proc/net/dev matches up with ifconfig as it should.
/etc/modprobe.conf displays:
alias eth0 e1000
alias eth1 e1000
alias eth2 tg3
alias eth3 tg3
a) looking for patch to _tmp83838 bug 224662 & 9
b) Why doesn't ifconfig match up with network-scripts?
Followup to :
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1459973
Support Fatherhood - Stop Family Law
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2010 12:35 AM
12-17-2010 12:35 AM
Re: network-scripts/ifcfg-eth# and ifconfig output are different
> eth1 - no ifgcfg-eth1
> eth2 - no ifgcfg-eth2
I guess you've probably disabled kudzu, then. (It would auto-generate those files when seeing unconfigured NICs.)
Create ifcfg- files for _all_ your 4 Ethernet NICs, even if their content will be only:
DEVICE=
BOOTPROTO=none
ONBOOT=no
HWADDR=
Also make sure the interface name in the filename matches the name declared in the DEVICE variable. When the system executes /etc/init.d/network start, all the ifcfg files will be read, and if the current interface MAC addresses don't match the configured ones, the ifup scripts will attempt to rename the interfaces to correct order.
But if you have specified only some of the interfaces, you'll get temporary names.
For example: assume you have two NICs, both using the same driver.
When the driver starts up, it finds the devices in such an order that eth0 gets MAC B, and eth1 gets MAC A.
But if ifcfg-eth0 specifies the HWADDR as MAC A, then the script sees it must rename eth1 to eth0. But there's already an eth0 (MAC B) in the way, so the script makes up a temporary name and renames the NIC with MAC B to temporary name.
Now, if the corresponding ifcfg-eth1 does not exist, or does not specify that eth1 should have MAC B, the network start-up script assumes its job is done, and the NIC with MAC B will remain assigned to a temporary name.
(If ifcfg-eth1 exists but does not contain the HWADDR= line, the script will attempt to use a NIC named "eth1". But because of the previous rename operation, no NIC with that name exists.)
"sit0" is a IPv6-in-IPv4 tunnel device; it doesn't need an ifcfg file unless you're going to use it.
MK
> eth2 - no ifgcfg-eth2
I guess you've probably disabled kudzu, then. (It would auto-generate those files when seeing unconfigured NICs.)
Create ifcfg-
DEVICE=
BOOTPROTO=none
ONBOOT=no
HWADDR=
Also make sure the interface name in the filename matches the name declared in the DEVICE variable. When the system executes /etc/init.d/network start, all the ifcfg files will be read, and if the current interface MAC addresses don't match the configured ones, the ifup scripts will attempt to rename the interfaces to correct order.
But if you have specified only some of the interfaces, you'll get temporary names.
For example: assume you have two NICs, both using the same driver.
When the driver starts up, it finds the devices in such an order that eth0 gets MAC B, and eth1 gets MAC A.
But if ifcfg-eth0 specifies the HWADDR as MAC A, then the script sees it must rename eth1 to eth0. But there's already an eth0 (MAC B) in the way, so the script makes up a temporary name and renames the NIC with MAC B to temporary name.
Now, if the corresponding ifcfg-eth1 does not exist, or does not specify that eth1 should have MAC B, the network start-up script assumes its job is done, and the NIC with MAC B will remain assigned to a temporary name.
(If ifcfg-eth1 exists but does not contain the HWADDR=
"sit0" is a IPv6-in-IPv4 tunnel device; it doesn't need an ifcfg file unless you're going to use it.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP