Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

Run Autonat Service while in unknown connectivity mode #75

Merged
merged 1 commit into from
Apr 8, 2020

Conversation

willscott
Copy link
Contributor

This supports local LAN connectivity / discovery
fix #73

This supports local LAN connectivity / discovery
@willscott willscott requested a review from Stebalien April 7, 2020 17:56
@@ -297,7 +295,7 @@ func (as *AmbientAutoNAT) recordObservation(observation autoNATResult) {
as.status.Store(autoNATResult{network.ReachabilityUnknown, nil})
if currentStatus.Reachability != network.ReachabilityUnknown {
if as.service != nil {
as.service.Disable()
as.service.Enable()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we should flip back to enabled if we were private. But I guess this is symmetric. Up to you.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the simpler state machine seems nicer. i'll stick with this for now.

@willscott willscott merged commit 4b4c43c into master Apr 8, 2020
@willscott willscott deleted the feat/unknownservice branch April 8, 2020 17:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Turn on even if we might be behind a NAT
2 participants