showing NIC as dev609 and not as eth1
On 21 Aug 2005 21:27:24 -0700, Harshal staggered into the Black Sun and said:
I am using a 3rd party kernel module that has some glaring deficiencies, but I don't really have enough experience to...
This is a post from an intermediate level Linux user, who is in his final year of Computer Engineering.*** Name : Ksheerasagar Akella Location : Mumbai, India Distros : Mandrake and Slackware Greetings to the Open Source...
That's just the ifconfig output. What about the other things I asked for? The ifconfig output is not enough information to solve anything--just confirm that there's something weird going on.
Look at this. Something is very weird here, and it's not just the strange name for eth0. Both devices have the same MAC address--that should never happen, but it can with NICs produced by the lowest bidder. Both devices are on different subnets, but they have the same broadcast address. That shouldn't happen since they're on different subnets. The RX and TX bytes are exactly the same for both devices. That's *possible*, it's just... weird for your typical gateway-firewall machine. Finally, the IRQ and I-O reported for both devices is the same. The only way that should ever happen is if you have a dual-port NIC.
So... what's really going on here? And follow up with the output from lspci, lsmod, and the parts of dmesg that are relevant.
-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL