Comment 0 for bug 2052834

Revision history for this message
Mark Cunningham (mdscunningham) wrote :

Customer has opened a case (00378390) indicating that when they use the lansdcape-api to get network info for client machines they do not get all interfaces returned by the API.

For their specific use case they need to get all MAC addresses from the machine to add those to their VPN for access. They indicate that their wifi interface shows up in the web UI, but not in the API output.

I was able to replicate this in 23.03+18 with my own laptop. Here are my results.

Actual interfaces on machine, there are four, which should all be visible in Landscape.

ip a | grep -E 'BROADCAST|ether|inet '

2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 38:f3:ab:41:dd:0d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.176/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s31f6

3: enx803f5d0918d6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 80:3f:5d:09:18:d6 brd ff:ff:ff:ff:ff:ff

4: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e0:2b:e9:bb:0f:6c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.143/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3

5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:e3:af:9a brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

From Web UI, I see three of four:

Network:
Model: Not available
MAC: 80:3f:5d:09:18:d6
IP: Not available

Model: Comet Lake PCH CNVi WiFi
MAC: e0:2b:e9:bb:0f:6c
IP: 192.168.1.143

Model: Ethernet Connection (11) I219-LM
MAC: 38:f3:ab:41:dd:0d
IP: 192.168.1.176

From API, I see a different three of four:

landscape-api get-computers --with-network --query <hostname>

  'network_devices': [{'broadcast_address': '192.168.1.255',
                       'duplex': True,
                       'interface': 'enp0s31f6',
                       'ip_address': '192.168.1.176',
                       'mac_address': '38:f3:ab:41:dd:0d',
                       'netmask': '255.255.255.0',
                       'speed': 1000},
                      {'broadcast_address': '192.168.122.255',
                       'duplex': False,
                       'interface': 'virbr0',
                       'ip_address': '192.168.122.1',
                       'mac_address': '52:54:00:e3:af:9a',
                       'netmask': '255.255.255.0',
                       'speed': 10000},
                      {'broadcast_address': '192.168.1.255',
                       'duplex': False,
                       'interface': 'wlp0s20f3',
                       'ip_address': '192.168.1.143',
                       'mac_address': 'e0:2b:e9:bb:0f:6c',
                       'netmask': '255.255.255.0',
                       'speed': -1}],

I would expect all four interfaces to be visible, and clearly Landscape is aware of all four because if we combine the outputs above you can see all four, but each view Web / API only returns a different three of the four.