NetworkPowerPort in exporter yaml config

[wojciiii]

I defined the following in the exporter.yaml file used by the labgrid exporter.

  NetworkPowerPort:
    model: 'apc'
    host: 'IPv4Address'
    index: 1

On my client I used this:

targets:
  main:
    drivers:
    resources:
     ..
      - NetworkPowerDriver:
          name: "dut_power"
          delay: 5.0
          bindings:
            port: 'NetworkPowerPort'

I have set LG_PROXY to connect to the exporter using SSH and enabled isolation mode in the exporter.

I was expecting the client to use the configured NetworkPowerPort from the same host as the exporter.
I was expecting to see the SNMP packets from the same host as the exporter runs on.
Instead I see SNMP packets from the host the Labgrid client runs on which is on a different network from my test network.

How can I configure Labgrid for using a client which doesn't have direct access to HW such as a network power port?

[Emantor]

Proxy forwarding is currently not implemented for transports which use UDP (which inlcudes the apc driver since it uses SNMP in the background).
We support isolated exporters by opening an SSH tunnel from the client to the exporter and forwarding the TCP connection which is not as easily implemented for UDP.

[rfdonnelly]

@Emantor what are your thoughts on running snmpcmd on the exporter via ssh instead of on the localhost? For example, instead of:

labgrid/labgrid/driver/power/apc.py

Line 8 in 22f4b81

f"snmpget -v1 -c private -O qn {host} {oid}".split()

it would be something like:

ssh {exporter} snmpget -v1 -c private -O qn {host} {oid}

One problem with this is that the driver doesn't currently have the exporter information.

[jluebbe]

A simple solution would be to use PDUdaemon for this.

[rfdonnelly]

@jluebbe thank you! TIL. PDUDaemon looks promising. I'll try that.