-
Notifications
You must be signed in to change notification settings - Fork 759
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
Unbound is not binded to OpenVPN interface #3342
Comments
|
And "Network Interfaces" under Unbound has your OpenVPN selected? |
|
Try a74ae3a: |
|
Works! 👍 |
|
small oversight in the explicit network interface listening. thanks for reporting. should be in 19.1.5 I think. did you also notice the ACL subnet for OpenVPN servers is now correct automatically? ;) |
|
Yes, I have seen it and I rejoiced :-) |
|
Okay, it's queued up for 19.1.5 although that will be 1-2 weeks from now. |
|
You applied the patch and removed it with the second invoke ;) |
|
That's what I thought and why I removed my message, but I just did it again just the once this time and it still isn't working. |
|
Need proof with ifconfig and /var/unbound/access_lists.conf output and make sure you don't have os-cache plugin active... |
|
You have your interfaces set to "all" ? |
|
Set to "all" where? I don't have os-cache installed/active |
|
Assumptions:
|
|
Btw, this looks ok to me? |
|
Yes that's my manual entry to get it working when "All (recommended" is set. If I set the interfaces manually and choose them all I get: |
|
Okay, I know what to do... but not exactly how to approach it. For reference, can you try to go to interfaces: assignments and assign your OpenVPN as a temporary interface? That should fix it too if the theory is correct. |
|
I assigned it, it was named OPT2, I then set Unbound to "All" and it still didn't appear. |
|
There's a lot of fishy stuff in unbound_acls_subnets() but I can reproduce now, thanks. |
|
Cool, let me know if you need anything more or for me to test another patch. |
|
With #3355 out of the way I should be able to fix this tomorrow. But we can't release this too quickly (as in 19.1.5) as it changes a few other spots along the way. |
|
@Taomyn works now but please don't try to patch this as there are a number of patches out there that are all required... when 19.1.5 please ask for a clean patch on top of that |
|
Thanks @fichtner, won't do anything more until 19.1.5, but should I remove the previous patch or just leave it? |
|
keep it, doesn't matter in your case (no interfaces selected) |
|
@fichtner: Since the patch I've no IDS/IPS logs anymore. Could this have to do with it? |
|
@JasMan78 rather unlikely, but revert + try doesn't hurt as an extra data point |
|
@fichtner Oh, sorry. I didn't think about this easy way to check if the patch is the problem. |
|
@fichtner I'm on 19.1.15 now, and I assume as my VPN subnet is not showing still that I still need a patch to fix this? |
|
Yes, hold on, I'll prepare the proper backport in a minute and post it here. |
(herewith queued up for 19.1.6 inclusion) |
|
Thanks, applied and tested working for me. |
|
👍 |

Describe the bug
Unbound is not binded to OpenVPN interface. Therefore OpenVPN clients are not able to resolve DNS names.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
VPN client should be able to resolve internal and external DNS names with Unbound.
Worked with OPNsense 18.7.1_3-amd64.
Relevant log files
/var/unbound/access_lists.conf
/var/unbound/unbound.conf
Additional context
As you can see access_lists.conf contains the VPN interface 10.0.11.0/24, but not unbound.conf under the binded interfaces . The sockets list shows the same (no socket for 10.0.11.1:53).
I've added a second VPN server to verify that's not an problem with my main OpenVPN server.
I've also reproduced the issue in a VM with OPNsense 19.1.4.
Environment
OPNsense 19.1.4-amd64
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores)
OnBoard Realtek
2 x Realtek GbE OnBoard LAN chips (10/100/1000 Mbit)
The text was updated successfully, but these errors were encountered: