Defguard Gateway service not registered on opnsense in 1.6.3#278
Merged
moubctez merged 1 commit intoDefGuard:mainfrom Feb 23, 2026
Merged
Defguard Gateway service not registered on opnsense in 1.6.3#278moubctez merged 1 commit intoDefGuard:mainfrom
moubctez merged 1 commit intoDefGuard:mainfrom
Conversation
…s is because of a mismatch between field name case. OPNsense's MVC framework stores XML model field names exactly as defined. The model defines <Enabled> with a capital E, and that's how it appears in the $config array at runtime. In our config we have half the cases looking for 'enabled' and the other looking for 'Enabled'. Making it consistent.
moubctez
approved these changes
Feb 23, 2026
filipslezaklab
approved these changes
Feb 23, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📖 Description
In 1.6.3 the Defguard Gateway service is not being registered. This is because of a mismatch between the field name and case. OPNsense's MVC framework stores XML model field names exactly as defined. The model defines with a capital E, and that's how it appears in the $config array at runtime.
In our config, half the cases look for 'enabled' and the other half look for 'Enabled'. Making it consistent.
🛠️ Dev Branch Merge Checklist:
Documentation
Testing
Deployment
🏚️ Main Branch Merge Checklist:
Testing
Documentation