Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Interfaces - change help text to reflect reality. closes #7339
For dhcp type interfaces, gateways are being pushed by the server and we automatically assume these are "external". For static ones you can configure similar behavior, but only explicit. When selecting a gateway, both reply-to and source nat rules are affected. When nothing is chosen (now default, earlier "auto-detect"), normal routing rules apply and nothing special happens.
- Loading branch information
1 parent
fd35aee
commit ff1991c
Showing
1 changed file
with
6 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now we’ve gone from “none” to “auto-detect” to “default”. The static case “default” still implies something else but wording really eludes the implemented behaviour. For static the wording “none” was pretty good actually. But not for anything else. And all just because outbound NAT generation is tied to this at the same time. 🤷♂️
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fichtner I'm ok with none as well, auto-detect doesn't make any sense as no logic is being applied here, but I kind of assumed that was a leftover from the past (below version 22.1):
core/src/www/interfaces.php
Line 2037 in 6786b6e
core/src/www/interfaces.php
Line 2570 in 6786b6e
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-detect attempted to refer to the way the gateway is chosen. “None” indicated none but that wasn’t the case. As I said double meaning for one setting is problematic.
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm probably lost, but the gateway setting on the interface has no role in gateway selection and is only visible for static items. The multi purpose (reply-to, source nat) is annoying, but also not solvable. But again, I don't mind if you rename it to None
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does at the very least affect default route creation. Leaving the gateway unselected will still use it when created. Hence “auto-detect”. But then there is 3 separate uses for this one setting. ;)
ff1991c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's discuss this when you're around, according to our own documentation it does not affect default route creation for static entries (https://docs.opnsense.org/manual/gateways.html)