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

Tune "Failed to decapsulate incoming packet" log #4872

Open
jamilbk opened this issue May 1, 2024 · 0 comments
Open

Tune "Failed to decapsulate incoming packet" log #4872

jamilbk opened this issue May 1, 2024 · 0 comments
Assignees
Labels
area/connlib Firezone's core connectivity library business_value/low Required by < 10% of our customer base

Comments

@jamilbk
Copy link
Member

jamilbk commented May 1, 2024

These are always WARN, but in some cases they're expected:

  • Client roams networks with an active DNS resource (e.g. GitHub.com). The Resource may continue sending packets to the Client but there is no valid IP mapping to receive them through and in most cases a new mapping has already been established
  • Client ICE agent expires or dies before it can send InvalidateCandidate Message to its peer.

Tech-savvy users will be confused by the WARN logs -- perhaps they should be DEBUG in certain cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connlib Firezone's core connectivity library business_value/low Required by < 10% of our customer base
Projects
None yet
Development

No branches or pull requests

2 participants