Fedora Linux Support Community & Resources Center

Home Forums Posting Rules Linux Help Fedora Set-Up Guides Ask Fedora Fedora Project
Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
Reload this Page Quad Nic Interface/ifconfig problem?
FedoraForum Search
Forgot Password? Join Us!
Register All Albums FAQ Search Today's Posts Mark Forums Read

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 13th May 2011, 01:47 AM
burnyd Offline
Registered User
  
Join Date: Jan 2005
Posts: 9
windows_xp_2003chrome
Quad Nic Interface/ifconfig problem?
I have 3 quad nics in a server I built for Dynamips/Dynagen its for ccie studies but I cant seem to understand why Fedora is making interfaces like eth7-9... its confusing. All I am trying to figure out is what interface is which MAC address.. which it tells me in the ifconfig but some of them are the same and some overlap with each other???

If anyone can help me with this that would be great, I asked the senior unix engineer I worked with and he had no idea haha??

Thanks,

Dan



[burnyd@dynamips ~]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:67:AA:37:23
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::230:67ff:feaa:3723/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16369 errors:0 dropped:0 overruns:0 frame:0
TX packets:7848 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7657704 (7.3 MiB) TX bytes:1129160 (1.0 MiB)
Interrupt:44 Base address:0x8000

eth1 Link encap:Ethernet HWaddr 08:00:20A:7E:5C
inet6 addr: fe80::a00:20ff:feca:7e5c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:21 Base address:0x5000

eth2 Link encap:Ethernet HWaddr 08:00:20A:7E:5D
inet6 addr: fe80::a00:20ff:feca:7e5d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:22 Base address:0x7000

eth3 Link encap:Ethernet HWaddr 08:00:20A:7E:5E
inet6 addr: fe80::a00:20ff:feca:7e5e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:23 Base address:0x9000

eth4 Link encap:Ethernet HWaddr 08:00:20A:7E:5F
inet6 addr: fe80::a00:20ff:feca:7e5f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:20 Base address:0xb000

eth5-eth7 Link encap:Ethernet HWaddr 00:03:BA:6D:76:AA
inet6 addr: fe80::203:baff:fe6d:76aa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:22 Base address:0xd000

eth6-eth7 Link encap:Ethernet HWaddr 00:03:BA:6D:76:AA
inet6 addr: fe80::203:baff:fe6d:76aa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:23 Base address:0xf000

eth7 Link encap:Ethernet HWaddr 00:03:BA:6D:76:AA
inet6 addr: fe80::203:baff:fe6d:76aa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:20 Base address:0x1000

eth8-eth7 Link encap:Ethernet HWaddr 00:03:BA:6D:76:AA
inet6 addr: fe80::203:baff:fe6d:76aa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:21 Base address:0x3000

eth9 Link encap:Ethernet HWaddr 08:00:20:E9:FD:68
inet6 addr: fe80::a00:20ff:fee9:fd68/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:20 Base address:0x5000

eth10-eth9 Link encap:Ethernet HWaddr 08:00:20:E9:FD:68
inet6 addr: fe80::a00:20ff:fee9:fd68/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:21 Base address:0x7000

eth11-eth9 Link encap:Ethernet HWaddr 08:00:20:E9:FD:68
inet6 addr: fe80::a00:20ff:fee9:fd68/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:22 Base address:0x9000

eth12-eth9 Link encap:Ethernet HWaddr 08:00:20:E9:FD:68
inet6 addr: fe80::a00:20ff:fee9:fd68/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:23 Base address:0xb000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7246 errors:0 dropped:0 overruns:0 frame:0
TX packets:7246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:615716 (601.2 KiB) TX bytes:615716 (601.2 KiB)

virbr0 Link encap:Ethernet HWaddr 1E:B4:E1:74:04:E8
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:8650 (8.4 KiB)

[burnyd@dynamips ~]$ lspci | grep Sun
04:00.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
04:00.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
04:01.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
04:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
04:02.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
04:02.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
04:03.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
04:03.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
05:00.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
05:00.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
05:01.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
05:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
05:02.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
05:02.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
05:03.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
05:03.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
06:00.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
06:00.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
06:01.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
06:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
06:02.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
06:02.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
06:03.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01)
06:03.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme] (rev 01)
Reply With Quote
  #2  
Old 13th May 2011, 02:27 AM
diamond_ramsey's Avatar
diamond_ramsey Offline
Registered User
  
Join Date: Aug 2009
Posts: 752
linuxfedorafirefox
Re: Quad Nic Interface/ifconfig problem?
A trick which I do to see which ports are what, is to use the ethtool utility.

* For example, ethtool -p eth0 5 would blink the LED on the interface for five seconds-without interrupting network traffic.
==========================
* Could this be like a separate network plug? For example, built-in or something like that?

eth0

* Has inet and different HW Address entries.
==========================
One Card -

eth1
eth2
eth3
eth4

* Above four do have different HWAddr. This is good.
==========================
Another Card -

eth5-eth7
eth6-eth7
eth7
eth8-eth7

* Above four do not have different HWAddr. This is confuses me. May / will confuse the system, too.
==========================
Another Card -

eth9
eth10-eth9
eth11-eth9
eth12-eth9

* Above four do not have different HWAddr. This is confuses me. May / will confuse the system, too.
==========================
lo - loopback
virbr0 - virtual bridge?
==========================
May be more ideas / questions will arrive.

Hope this helps.
__________________
2 dual cores, 11 GB RAM, F14 Laughlin - 2.6.35.14-106.fc14.x86_64 & 2.6.35.14-106.fc14.i686.PAE
2 dual cores, 11 GB RAM, F15 Lovelock - 2.6.43.8-2.fc15.x86_64 & 2.6.43.8-2.fc15.i686
3 dual cores, 19 GB RAM, F16 Verne - 3.6.2-1.fc16.x86_64 & 3.6.2-1.fc16.i686
2 dual cores, 11 GB RAM, F17 Beefy Miracle - 3.6.2-4.fc17.x86_64 / .i686
16 x86_64 computing cores,80 GB RAM & 8 SATA Seagate 7200.12 500 GB harddisks
Reply With Quote
  #3  
Old 15th May 2011, 08:26 PM
burnyd Offline
Registered User
  
Join Date: Jan 2005
Posts: 9
windows_vistachrome
Re: Quad Nic Interface/ifconfig problem?
well this is interesting..


[root@dynamips ~]# vi /etc/udev/rules.d/70-persistent-net.rules

[root@dynamips ~]# vi /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:ca:7e:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:ca:7e:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:ca:7e:5c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:e9:fd:68", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth10"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:e9:fd:68", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth11"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:20:e9:fd:68", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth9"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:03:ba:6d:76:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:03:ba:6d:76:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth8"

# PCI device 0x108e:0x1001 (hme) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:03:ba:6d:76:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth7"
Reply With Quote
Reply

Tags
interface or ifconfig, nic, problem, quad

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What's this virbr0 interface in ifconfig? Thetargos Servers & Networking 4 1st December 2011 06:05 PM
ifconfig problem chris.tkd Servers & Networking 4 2nd March 2008 02:39 PM
ifconfig problem! darkdragon Servers & Networking 2 6th February 2007 07:29 AM
ifup [interface] = ifconfig [interface] up ? nyinge Servers & Networking 1 5th April 2006 10:21 PM
ifconfig problem ATIR350 Servers & Networking 5 22nd May 2005 08:58 PM


Current GMT-time: 12:08 (Monday, 20-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

 FedoraForum is Powered by RedHat