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

[Bug] Dev branch - Covenant doesn't start if the listener interface is no longer available #348

Open
seckek opened this issue Jan 12, 2022 · 2 comments
Assignees

Comments

@seckek
Copy link

seckek commented Jan 12, 2022

Feature Request or Bug
Bug

Describe the feature request or bug
If a listener is configured for an interface that no longer exists (eg. tun0) Covenant is unable to start.

To Reproduce
Steps to reproduce the behavior:

  1. Create a listener in covenant
  2. Disable the interface the listener was using (eg. by using "ifconfig eth0 down")
  3. Restart covenant
  4. Observe the "Cannot assign requested address" error.

Expected behavior
Covenant should start without the affected listener.

Screenshots
Setting up the listener:
Cov1
Removing the interface and restarting Covenant:
Cov2

seckek added a commit to seckek/Covenant that referenced this issue Jan 15, 2022
seckek added a commit to seckek/Covenant that referenced this issue Jan 15, 2022
@xiaoheiccc
Copy link

BindAddress should be 0.0.0.0

@seckek
Copy link
Author

seckek commented Feb 11, 2022

Wouldn't 0.0.0.0 listen on all interfaces which is different to using only one interface? I don't think that the intention is for users to always use 0.0.0.0, otherwise why have the option to change the BindAddress

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

No branches or pull requests

3 participants