You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, there currently is no mechanism to ensure that the firewall is kept open for the duration of the connection between the peers. This leads to firewall/s timing out the opened port and the connection between two peers dropping, if there is no traffic between the peers (for ufw this seems to happen after ~10mins or so).
Similar to the heartbeat that is sent to the rolodex, to ensure the NAT mapping stays open
meshboi currently has some logic to ensure that the peer's firewall is open for inbound connection from other meshboi peers:
meshboi/peer_connector.go
Line 137 in c5f221b
However, there currently is no mechanism to ensure that the firewall is kept open for the duration of the connection between the peers. This leads to firewall/s timing out the opened port and the connection between two peers dropping, if there is no traffic between the peers (for
ufw
this seems to happen after ~10mins or so).Similar to the heartbeat that is sent to the rolodex, to ensure the NAT mapping stays open
meshboi/rolodex_client.go
Line 82 in c5f221b
The text was updated successfully, but these errors were encountered: