Bug 697063 - Service Network Adapter on Windows not related to physical world
Service Network Adapter on Windows not related to physical world
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
4.0.0.Beta1
i386 Windows
low Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-15 13:46 EDT by Bernd Eckenfels
Modified: 2011-10-12 10:47 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Bernd Eckenfels 2011-04-15 13:46:19 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):
4.0.0.Beta1

How reproducible:
Scan a Windows XP host and compare the found network adapter (services) with the output of "route.exe print"

  
Actual results:
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
Key: eth-00:0f:1f:91:c4:xx

based on:

C:\>route print
===========================================================================
Schnittstellenliste
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 1f 91 c4 xx ...... Intel(R) PRO/1000 MTW Network Connection - Paket
planer-Miniport
0x3 ...08 00 27 00 8c 43 ...... VirtualBox Host-Only Ethernet Adapter - Paketpla
ner-Miniport
0x4 ...00 ff b8 aa 18 fc ...... Juniper Network Connect Virtual Adapter - Paketp
laner-Miniport
...
C:\>ipconfig /all
Ethernetadapter LAN-Office:

        Verbindungsspezifisches DNS-Suffix: xxx.de
        Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MTW Network Connec
tion
        Physikalische Adresse . . . . . . : 00-0F-1F-91-C4-xx

Additional info:
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
Comment 1 Bernd Eckenfels 2011-04-15 14:43:57 EDT
(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.

Note You need to log in before you can comment on or make changes to this bug.