SNMP sent locally despite proxy_required

[AiyionPrime]

Following my attempts in #1413, I'd like to showcase the same problem in code I have not touched before :)

A network_power_port like this:

Acquired resource 'NetworkPowerPort' (ma-firmware-integrationtest-01/example-group/NetworkPowerPort/NetworkPowerPort):

{'acquired': 'example-place',
 'avail': True,
 'cls': 'NetworkPowerPort',
 'params': {'extra': {'proxy': 'ma-firmware-integrationtest-01',
                      'proxy_required': True},
            'host': '192.168.0.2',
            'index': 0,
            'model': 'poe_mib'}}

Sends the SNMP requests from my local machine, instead of the exporter host, despite proxy_required.

LG_PROXY=ma-firmware-integrationtest labgrid-client --coordinator 10.120.4.251:22408 -p example-place power off

I can see the SNMP packet being sent from my local host via wireshark.

I'd expect the client to pick up on 'proxy_required': True.
Am I missing something?

If not, I'd start debugging this tomorrow.

[Emantor]

SNMP uses UDP and we can only proxy forward TCP connections over SSH. So we would probably need an agent interface that should be used on the remote host?

[AiyionPrime]

Good catch.
But at that point we'd be at just using pdudaemon, right?

[AiyionPrime]

Nice, you two apparently had a similar thought a few weeks ago.
pdudaemon/pdudaemon@738c554

[AiyionPrime]

Pdudaemon works pretty well for me.

Should labgrid emit a warning, if proxy required is set, but the driver does not support it?

[Emantor]

Do you have an implementation idea? My immediate idea is to annotate every power backend and driver that is not supported with a proxy_unsupported flag and checking against that.