-
-
Notifications
You must be signed in to change notification settings - Fork 440
Closed
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I have been checking any type of configuration - also the basic config in this example - on a single host where the fix does not apply and I'm not able to ping the wireguard gateway with multiple networks.
Does this "fix" still apply as I have seen this working before.
Removing the nics create a default route on eth0 to the host again what makes it possible to use the VPN and ping the gateway.
I'm refering to #170
I hope someone can clear this out.
Expected Behavior
No response
Steps To Reproduce
See #170
Environment
CPU architecture
x86-64
Docker creation
See https://github.com/linuxserver/docker-wireguard/pull/170Container logs
See https://github.com/linuxserver/docker-wireguard/pull/170Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done