Closed Rylan12 closed 3 years ago
Thanks for the report @Rylan12
We are trying to rework a portion of the state channels and packet handling protocol in blockchain-core#602 that would in theory make sending packets more robust. Although I should mention that dialing p2p streams over the internet is inherently a little finicky, there are multiple reasons why a dial may fail (and these are beyond our control). However, the work being done to address some of it in blockchain-core should make it more consistent :crossed_fingers:
Please take a look at that PR and check if things make sense, we'd appreciate any help!
Going to close this as stale. It's something that we're working on, but there isn't a single actionable thing to do here.
Description
I'm using a DIY gateway with a miner hosted in an AWS EC2 instance to try to send data to the Helium network. Some packets are being dropped in between the miner and reaching the Helium console (I'd estimate that 1 out of every ~5-10 packets is dropped). I have tracked several dropped packets and they appear to move successfully from the sensor, through the packet forwarder, and to the miner, where it is dropped with the error messages
failed to dial "/p2p/112qB3YaH5bZkCnKA5uRH7tBtGNv2Y5B4smv1jsmvGUzgKT71QpE"
andfailed to dial 1: failed dropping 2 packets
.I've included the logs from the miner during a dropped packet below. The payload being sent is 3 bytes (not including the Helium header) and is being sent every 2 minutes (for testing purposes). The issue also happens at higher intervals between packets (I know that I've seen the issue at 5 minute intervals as well).
It appears that the miner is trying to connect to a p2p address but the connection is failing. Instead of trying again with a different peer (as I would expect), the miner "gives up" and drops the packet.
Info
miner-amd64_2020.07.31.0_GA