Menu

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.

Show posts Menu

Messages - longtom

#1
Thanks a lot for the quick patch!  :)
#2
My Unbound DNS over TLS is NOK with 24.7.10.
When i disable DNS over TLS it is OK again.

Edit: With todays version 24.7.10!
#3
Thanks for your Thread, i have the same issue with NAT and DHCP server over 3rd Party Wireguard tunnel.
Is there any report to opnsense?
#4
General Discussion / Re: Wireguard and NAT rules
May 21, 2024, 08:00:18 AM
Thanks a lot for ataching, helped a lot!
#5
Thanks for this detailed installation way!
I just used this easy install (in german)https://hoerli.net/opnsense-adguardhome-werbefrei-trackerfrei-und-hinter-einer-guten-firewall/.
#6
When i use the DHCP Server in opnsense how do i use the different ranges?
e.g. 192.168.1.0/24 2 DHCP ranges (100-149, 150-159).
I want that only some clients with a specific vendor ID gets the 150-159 address.

Is there any way to do that?
If not, how can i assign users in the additional range of 150-159?
I don't understand the logic when this address-range is taken.
#7
Working now, don't know why...  ::)
#8
The hostname of my opnsense (opnsense) does not resolve itself.
(Static Adresss)
What do i have to check that it is fine?
OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
OpenSSL 1.1.1i 8 Dec 2020

Using Unbound DNS