Skip to content

Agent continues to attempt to peer with tailnet Clients indefinitely #7960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
spikecurtis opened this issue Jun 12, 2023 · 1 comment
Closed

Agent continues to attempt to peer with tailnet Clients indefinitely #7960

spikecurtis opened this issue Jun 12, 2023 · 1 comment
Labels
networking Area: networking s4 Internal bugs (e.g. test flakes), extreme edge cases, and bug risks

Comments

@spikecurtis
Copy link
Contributor

Coder Agent is informed of tailnet Clients to peer with, but when Clients are finished with their tailnet tunnel, the Agent is never informed.

This leads to the Agent continuing to attempt to peer with them including one or more of

  • maintaining a connection to their DERP home
  • tailscale discovery (disco) pings
  • wireguard handshakes

This leads to undesired network traffic and log spam as the agent retries and fails to peer.

When end users contact us and complain about undesired disconnects, if they send us agent logs, we have no way to distinguish between peer disconnections that were and not legit.
@spikecurtis
Copy link
Contributor Author

There is some desire to enable to coordinator to terminate tunnels when a user is suspended/deleted. Informing the agent of a revoked connection is a prerequisite for this.

@spikecurtis spikecurtis mentioned this issue Jun 15, 2023
Merged
10 tasks
@spikecurtis spikecurtis mentioned this issue Jul 14, 2023
Closed
@bpmct bpmct added the s3 Bugs that confuse, annoy, or are purely cosmetic label Aug 7, 2023
@matifali matifali added s4 Internal bugs (e.g. test flakes), extreme edge cases, and bug risks and removed s3 Bugs that confuse, annoy, or are purely cosmetic labels Aug 24, 2023
@spikecurtis spikecurtis added the networking Area: networking label Sep 26, 2023
@spikecurtis spikecurtis mentioned this issue Nov 21, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
networking Area: networking s4 Internal bugs (e.g. test flakes), extreme edge cases, and bug risks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@spikecurtis @matifali @bpmct