Packets not forwarded to Helium console, and warning in logs

[jpmeijers]

I have gateway-rs running using this docker setup. When my device does an OTAA join, on the Helium console I do not see my gateway's name appear, only a couple of other gateways. My gateway is the closest one. It looks like data (or at least join requests) are not forwarded to the Helium console.

In the gateway-rs logs I see many warnings like this:

WARN failed to connect state channel: Service(Rpc(Status { code: Unavailable, message: "error trying to connect: tcp connect error: Connection refused (os error 111)", source: Some(tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))) })), oui: 1, uri: http://68.82.33.41:8080/, pubkey: 112qB3YaH5bZkCnKA5uRH7tBtGNv2Y5B4smv1jsmvGUzgKT71QpE, module: router

Should I rather file this upstream at Helium gateway-rs repo?

[jpmeijers]

This issue belongs in the gateway-rs repo.

But after discussion we believe nothing is wrong. I do not see packets from my gateway on the console, as other full hotspots around delivers the messages faster than my gateway -> gateway-rs setup.

[jpmeijers]

I can reproduce no uplinks are forwarded when only my gateway is in reach.

Issue filed on gateway-rs repo:
helium/gateway-rs#166