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

Wireguard selective routing gateways loop detected #6993

Closed
2 tasks done
phoropter opened this issue Nov 7, 2023 · 4 comments
Closed
2 tasks done

Wireguard selective routing gateways loop detected #6993

phoropter opened this issue Nov 7, 2023 · 4 comments
Labels
help wanted Contributor missing / timeout upstream Third party issue

Comments

@phoropter
Copy link

phoropter commented Nov 7, 2023

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

Somewhat regularly, about once a day, one of the gateways I have set up for Mullvad will get 100% packet loss and General System Logs will show wgX: loop detected. If I manually disable then enable the gateways, things will be fine for a while.

I have created 3 tunnels to mullvad, put into a gateway group, following the mullvad roadwarrior and the selective routing guides to a tee.

To Reproduce

Steps to reproduce the behavior:

  1. Create multiple mullvad tunnels and set up selective routing
  2. Eventually one of the gateways will loop

Expected behavior

For the loops to not happen.

Describe alternatives you considered

Not sure of any viable alternatives.

Screenshots

Gateways if helpful:
image

Relevant log files

The logs show hundreds of lines of wgX: loop detected in the space of a few seconds. There are no consistent preceding events that I can find.

Additional context

I have opnsense sitting behind an AT&T fiber gateway in passthrough mode with the WAN gateway set to Far Gateway.

Separately, as a stopgap measure, is it possible to have monit restart the gateways? I was unable to find any commands that are capable of doing so.

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 23.7.7_3 (amd64, OpenSSL).
Intel i5-8600T 2.3Ghz 6 Core
Network Supermicro AOC-STGN-I2S

@fichtner
Copy link
Member

fichtner commented Nov 8, 2023

Same here https://forum.opnsense.org/index.php?topic=35919.0 ... since this pertains Mullvad and the kernel module I'm not entirely sure we can do anything here. Marking upstream for now.

@fichtner fichtner added the upstream Third party issue label Nov 8, 2023
@phoropter
Copy link
Author

Same here https://forum.opnsense.org/index.php?topic=35919.0 ... since this pertains Mullvad and the kernel module I'm not entirely sure we can do anything here. Marking upstream for now.

I guess that's not surprising. In the meantime, is it possible to have monit restart gateways when they go down? I have been unable to find any command to manipulate them.

@phoropter
Copy link
Author

I was following the docs for creating a site-to-site and noticed it has a normalization section in setting up firewall rules that doesn't exist for the mullvad & selective routing docs. After setting up the site-to-site I haven't had any issues.

@OPNsense-bot
Copy link

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

@OPNsense-bot OPNsense-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
@OPNsense-bot OPNsense-bot added the help wanted Contributor missing / timeout label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contributor missing / timeout upstream Third party issue
Development

No branches or pull requests

3 participants