Feature #12636
closedAutomatically create DNS Resolver ACLs for OpenVPN CSO entries
100%
Description
DNS Resolver creates ACLs OpenVPN client/server IPv4/IPv6 tunnel networks entries,
but not for Client Specific Overrides
Related issues
Updated by Viktor Gurov almost 3 years ago
Updated by Jim Pingle almost 3 years ago
- Tracker changed from Bug to Feature
- Subject changed from DNS Resolver does not create ACLs for OpenVPN CSO entries to Automatically create DNS Resolver ACLs for OpenVPN CSO entries
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Priority changed from Normal to Low
- Target version set to CE-Next
- Plus Target Version set to 22.05
- Affected Version deleted (
2.5.2)
Updated by Viktor Gurov almost 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 9ca90ee8b52c350bb41cabb0b496e7793ace88d2.
Updated by Jim Pingle almost 3 years ago
- Target version changed from CE-Next to 2.7.0
Updated by Danilo Zrenjanin over 2 years ago
Tested on the:
2.7.0-DEVELOPMENT (amd64) built on Sat Mar 26 06:15:45 UTC 2022 FreeBSD 12.3-STABLE
The access_lists.conf file doesn't get updated automatically after creating a CSO entry. After the manual unbound restart, the CSO subnet was added.
The unbound service needs to be reloaded automatically after adding a new CSO. Please check.
Updated by Viktor Gurov over 2 years ago
- Status changed from Feedback to Resolved
Danilo Zrenjanin wrote in #note-5:
Tested on the:
[...]
The access_lists.conf file doesn't get updated automatically after creating a CSO entry. After the manual unbound restart, the CSO subnet was added.
The unbound service needs to be reloaded automatically after adding a new CSO. Please check.
The access_lists.conf file is also not updated when updating the OpenVPN Tunnel/Local/Remote Network.
A New redmine issue created: #12991
Updated by Viktor Gurov over 2 years ago
- Related to Bug #12991: DNS Resolver ACLs are not updated when OpenVPN networks change added