Skip to content
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.

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

Adapt to changing network environments better #4

Closed
danderson opened this issue Feb 10, 2020 · 1 comment
Closed

Adapt to changing network environments better #4

danderson opened this issue Feb 10, 2020 · 1 comment

Comments

@danderson
Copy link
Member

danderson commented Feb 10, 2020

Overall tracking bug for network change reactivity.

When the network environment changes (e.g. switch from LTE to wifi, NAT gateway reboots and loses all its mappings), nodes should reestablish connectivity gracefully.

We currently adapt in some cases, but not others. We should always notice changes to connectivity, and adapt gracefully to them.

@bradfitz
Copy link
Member

Bug scrub.

What remains here, @danderson, @crawshaw?

clairew added a commit that referenced this issue Mar 13, 2024
# This is the 1st commit message:

cmd/tailscale, ipn/ipnlocal: add suggest exit node CLI option
wip

# The commit message #2 will be skipped:

# wip

# The commit message #3 will be skipped:

# wip

# The commit message #4 will be skipped:

# wip
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants