-
Notifications
You must be signed in to change notification settings - Fork 767
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
GUI value of GRE tunnel config does not match the configured value #8161
Comments
Not sure how to prove your theory: we don’t know the actual configured config.xml value and your interface names plus internal identifiers (which should match the config.xml value in the GRE). Cheers, |
I recognized the same behaviour while creating a GIF tunnel yesterday. Maybe these values from config.xml are helping to proof this?
The local interface name would be
|
Is WAN_VF the first one in the list? |
Thanks, I can reproduce. |
This should help, but I need to discuss with @AdSchellevis
|
Do not use internalValue since it is only the default.
Do not use internalValue since it is only the default.
Do not use internalValue since it is only the default.
Do not use internalValue since it is only the default.
Do not use internalValue since it is only the default.
Done but won't ship in 24.7.x anymore. |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
I have two GRE tunnels on my multi-WAN machine. The GUI shows the primary WAN as "local address" but for both tunnels the secondary WAN has been configured. Looks like being just a display issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The really configured value is being shown.
Screenshots
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.7.11_2-amd64
FreeBSD 14.1-RELEASE-p6
OpenSSL 3.0.15
The text was updated successfully, but these errors were encountered: