Skip to content

mesh_interface's waitForAckNak uses the default Timeout() class timeout, making multiple hop remote administration difficult. #838

@horrible-knots

Description

@horrible-knots

waitForAckNack in mesh_interface uses a default instance of Timeout(), which defaults to 20 seconds. It's called directly by node.py and _main_.py.

It looks like it's set properly in node.py, and passed to mesh_interface.py, but ultimately doesn't change the _timeout instance in mesh_interface.

I think it might be the cause of #827 and the cause of my local mesh being unable to do remote node administration over many hops. Everything works, it's just not waiting long enough to get the reply (ie: it can be seen coming through another node a few seconds after the cli gives up). I don't have logs because I'm a third party.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions