Red Hat Bugzilla – Bug 697063
Service Network Adapter on Windows not related to physical world
Last modified: 2011-10-12 10:47:42 EDT
Description of problem:
The network adapters discoverd on my Windows XP are called "lo" and "en1-x". This is a totally unnatural naming convention, and even the index is in my case not related with the platoforms native index number (as can be seen with router.exe print).
The adapters description as seen from windows is not represented in any of the traits of the interface (especially not in the description where I would expect it)
The index number of the adapter does not correlate with the windows interface index (see below), and the description does not contain the adapters description as specified by windows (which is rather crucial if there are virtual tunnel adapters).
Version-Release number of selected component (if applicable):
Scan a Windows XP host and compare the found network adapter (services) with the output of "route.exe print"
Name: eth2 Type: Network Adapter (Platforms)
Version: none Description: 00:FF:B8:AA:18:FC Resource Key: eth2
Expected results: (or similiar)
Name: LAN Office 0x2
Description: 00:0f:1f:91:c4:xx - Intel(R) PRO/1000 MTW Network Connection
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 1f 91 c4 xx ...... Intel(R) PRO/1000 MTW Network Connection - Paket
0x3 ...08 00 27 00 8c 43 ...... VirtualBox Host-Only Ethernet Adapter - Paketpla
0x4 ...00 ff b8 aa 18 fc ...... Juniper Network Connect Virtual Adapter - Paketp
Verbindungsspezifisches DNS-Suffix: xxx.de
Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MTW Network Connec
Physikalische Adresse . . . . . . : 00-0F-1F-91-C4-xx
I do also miss the most interesting ehternet statistics like the error rate output by netstat -e.
PS: sorry in case "Plugins" is not the right component
(In reply to comment #0)
> I do also miss the most interesting ehternet statistics like the error rate
> output by netstat -e.
Forget that part, the measurements are just not enabled by default, found it in the schedules section.