Greg,
Gregory P. Ennis wrote:
<snip> >> Some additional information that may be useful. The TrendNet card is >> the second TrendNet card I have used. The first card had the same >> symptoms, and I deduced the card was bad, and purchased another one. >> The symptoms are the same with the second card. > <snip> Ah, but you should in your logs, or - if you're running 6.2 - possibly in /etc/udev/rules.d/70-persistant-net.rules.
too. Both the first and second cards did not appear to have any damage on the boxes or the card itself. Before I tried to get a third card
<snip>
In that case, sounds like the OEM had a q/c problem.
That's interesting. Here are the log entries for the previous card as well as the eth4 that is currently installed.
# PCI device 0x10ec:0x8168 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:b3:10:f6:81", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x10ec:0x8168 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:b3:10:fc:6e", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
Looks like addresses are close.
So-so; not *that* close. I have some servers with two on-board NIC's whose MAC addresses end in things like fe:ab, fe:ac, fe;36, fe:37. Still....
Actually, I missed the beginning of this thread. Are there no on-board NICs? I've not seen a m/b in a long time without that; even Rasberry Pi has one.
mark