1
24.7 Production Series / Re: upgrade to 24.7.4 worked perfectly
« on: September 14, 2024, 06:44:48 pm »
+1. Smooth.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
24.7 Production Series / Re: 24.7.3 - Interface Statistics Widget
« on: September 01, 2024, 02:42:44 pm »
Ohh it does... 
Silly me
Silly me
3
24.7 Production Series / [SOLVED] 24.7.3_1 - Interface Statistics Widget
« on: September 01, 2024, 02:08:16 pm »
Hi all,
First of all, thanks for everything and keeping OPNsense going strong.
Just wanted to float a suggestion, idea... Before upgrading to 24.7 I really like the tabular format of the widget "Interface Statistics". The new piechart, imho, has less single look clarity, i.e. I believe the tabular format is much better.
Is it possible to het the tabular format back, perhaps as an option?
First of all, thanks for everything and keeping OPNsense going strong.
Just wanted to float a suggestion, idea... Before upgrading to 24.7 I really like the tabular format of the widget "Interface Statistics". The new piechart, imho, has less single look clarity, i.e. I believe the tabular format is much better.
Is it possible to het the tabular format back, perhaps as an option?
4
24.7 Production Series / Re: [SOLVED] IGMP proxy not releasing streams after upgrading to 24.7
« on: July 30, 2024, 04:40:56 pm »24.7.1 kernel will have it, for now on 24.7_x use the test kernel.
Copy all, thanks. I'l just wait then. I can install a testkernel, but when stuff goes south I am too noob to dive in and fix on the commandline.
5
24.7 Production Series / Re: IGMP proxy not releasing streams after upgrading to 24.7
« on: July 30, 2024, 04:04:31 pm »I've added these two commits for 24.7.1 (which are in 24.7_9 as tested):
So, just to conform the aforementioned sentence --> Has this fix been included in the standard (now released) 24.7_9 or will they only be released in 24.7.1 and are they only in the test kernel for now?
I am waiting with my upgrade for this fix as I am also a KPN fiber user in NLD...
6
22.7 Legacy Series / Re: LAN DNS resolution fails through OpenVPN when Adguard is enabled
« on: October 26, 2022, 09:13:26 pm »
Problem solved. The problem was caused by two mistakes I made in the configuration.
1) I forgot to activate the “DNS local domain” setting in the OpenVPN server setting and enter the local domain name in that settling. This makes sure that local names get trailed by the local domain for proper resolution
2) I initially entered the local LAN ip for the local DNS server (192.168.10.254) in the OpenVPN server settings to pass to connected clients as DNS to use. This actually needs to be the (unassigned) interface address of the ovpns interface that hosts the tunnel network. In my case this is 192.168.20.1, which is automatically set when configuring the tunnel network as 192.168.20.0/24.
These two changes solved the problem. In Adguard settings I noticed that Adguard also listens on 192.168.20.1 next to 192.168.10.254. While I am unsure why it does work properly with 192.168.10.254 set in OpenVPN server as client DNS without Adguard installed (DNS local domain needs to be set in both cases) I guess it has something to do with routing between the two networks. As mentioned in my previous post the DNS request comes in, is forwarded to the local DNS (192.168.10.254:5353), a correct reply is received by Adguard, but somehow the reply is not sent back from 192.168.10.254 to the client at 192.168.20.x/24. While this does work without AdGuard….. Maybe an Adguard application issue..?
1) I forgot to activate the “DNS local domain” setting in the OpenVPN server setting and enter the local domain name in that settling. This makes sure that local names get trailed by the local domain for proper resolution
2) I initially entered the local LAN ip for the local DNS server (192.168.10.254) in the OpenVPN server settings to pass to connected clients as DNS to use. This actually needs to be the (unassigned) interface address of the ovpns interface that hosts the tunnel network. In my case this is 192.168.20.1, which is automatically set when configuring the tunnel network as 192.168.20.0/24.
These two changes solved the problem. In Adguard settings I noticed that Adguard also listens on 192.168.20.1 next to 192.168.10.254. While I am unsure why it does work properly with 192.168.10.254 set in OpenVPN server as client DNS without Adguard installed (DNS local domain needs to be set in both cases) I guess it has something to do with routing between the two networks. As mentioned in my previous post the DNS request comes in, is forwarded to the local DNS (192.168.10.254:5353), a correct reply is received by Adguard, but somehow the reply is not sent back from 192.168.10.254 to the client at 192.168.20.x/24. While this does work without AdGuard….. Maybe an Adguard application issue..?
7
22.7 Legacy Series / Re: LAN DNS resolution fails through OpenVPN when Adguard is enabled
« on: October 26, 2022, 07:13:27 pm »
I have exactly the same issue. Switching off Adguard plugin, setting unbound back to port 53 (from 5353) and reconnecting to the OpenVPN server solves the issue.
The log from Adguard does show DNS requests from the connected OpenVPN client ip (from the openVPN client ip range). Apparently the reply does not arrive back at the client for some reason. I am unable to track where it is blocked.
The log from Adguard does show DNS requests from the connected OpenVPN client ip (from the openVPN client ip range). Apparently the reply does not arrive back at the client for some reason. I am unable to track where it is blocked.
Pages: [1]