Messages

A "pin" sounds like a way to keep it flexible for everyone!

Quick question on how that would work: will it remember its pinned state even after closing and reopening the GUI?

Alternatively, how about adding a simple toggle under "System: Settings: Administration" instead? That might be even easier to implement and keeps the GUI clean without needing an extra icon.

Let me know what you think!

I really appreciate the new Favorites menu; it is a great addition to the interface.

However, I noticed that in several scenarios, accessing an item via the Favorites menu requires the same number of clicks as the original navigation route, which reduces its efficiency.

To optimize this, would it be possible to make two small adjustments?
First, have the Favorites menu open by default.
Second, keep it expanded after an item is selected instead of automatically collapsing it.
Saving those extra clicks would significantly improve the workflow and speed up the quick access objective ;-)

I'd love to know if this is something that could be considered for a future update.

Just a for the record.... ISC DHCPv4 and DHCPv6 are still available in OPNsense 24.1.6.

@KeithRBrown with "A feature which I currently use on ISC DHCPv4 is the ability to override the DNS Server setting in a Static Mapping." do you mean the ability to configure a different DNS server for the entire DHCP subnet instead of pointing to the address of the OPNsense instance itself? For instance OPNsense runs with 192.168.1.1 so DHCP clients for the 192.168 subnet get pointed to 192.168.1.1 but configure 192.168.1.200 as the alternative DNS server to be used? That is possible with Kea DHCP already by editing the defined subnet and remove the tick in the box for "Auto collect option data".

OR are you looking for an option to configure different DHCP settings for one or more individual MAC address entries to overrule the settings defined at the subnet level? That finer granularity is NOT available in Kea DHCP (yet?) at the individual client level. To workaround that I have created different subnets for DHCP clients so I can apply differences at that level. Which is something you cannot do with ISC DHCP as that appears to work at the interface level. While thinking about it now, I actually prefer the Kea DHCP approach I am using at the subnet level as I can apply those differences easier for multiple clients in one go.

[192.168.0.39,192.168.0.139]

Hello AhnHEL (Angel)!

I re-activated it and tried again and this time the clients do get the proper DNS servers configured.  8)

/usr/local/etc/kea/kea-dhcp4.conf
...
        "subnet4": [
            {
                "id": 1,
                "subnet": "192.168.0.0/17",
                "option-data": [
                    {
                        "name": "domain-name-servers",
                        "data": "192.168.0.39,192.168.0.139"
                    },
                    {
                        "name": "routers",
                        "data": "192.168.0.138"
                    },
                    {
                        "name": "ntp-servers",
                        "data": "192.168.0.138"
                    },
                    {
                        "name": "domain-name",
                        "data": "lan"
                    }
                ],
...

Windows client:

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (10) I219-V
   Physical Address. . . . . . . . . : 1C-69-7A-66-9A-6E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::44b5:b8db:adb1:a1d6%8(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.50(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.128.0
   Lease Obtained. . . . . . . . . . : vrijdag 19 april 2024 19:13:53
   Lease Expires . . . . . . . . . . : vrijdag 19 april 2024 20:20:33
   Default Gateway . . . . . . . . . : 192.168.0.138
   DHCP Server . . . . . . . . . . . : 192.168.0.138
   DHCPv6 IAID . . . . . . . . . . . : 605841786
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-6E-71-DF-0C-7A-15-87-40-1A
   DNS Servers . . . . . . . . . . . : 192.168.0.39
                                       192.168.0.139
   NetBIOS over Tcpip. . . . . . . . : Enabled


No idea why it did not work previously.   ::)
At least this is working now. I will keep it running with my current OPNsense 24.1.5_3 for a bit prior to upgrading to 24.1.6 to confirm it is stable enough to move to that version and possibly using my fallback option towards ISC DHCP...

Thanks for making me aware that it should work well.

I meanwhile found out that unchecking "Auto collect option data" on a defined subnet allows you to configure "Routers (gateway)", "DNS servers" etc.

Unfortunately after entering the DNS servers I would like the clients to receive within the "DNS servers" field,  saving this and restarting the "Kea DHCPv4" my clients do not receive my defined DNS servers when they receive the new lease  :'(

Moving back to ISC DHCPv4 again  >:(

I am also using that feature on ISC DHCPv4 and I definitely require it.

After I stopped ISC DHCPv4 and enabled KEA DHCPv4 I am unable to find an option to configure alternative DNS servers even though the docs at https://docs.opnsense.org/manual/dhcp.html#kea-dhcp mentions a settings option "Default DNS servers to offer to the client".  :'(

I am running "OPNsense 24.1.5_3-amd64" and was looking at the 24.1.6 release notes.

The notes confuse me a bit since it states:
===
"OPNsense 24.1.6 released
Today we are happy to announce another milestone regarding ISC DHCP removal: the arrival of a DHCRelay replacement based on code forked and maintained by OpenBSD.
==

Based upon that part I was guessing that ISC DHCP is removed. However, within the patch notes I am reading:
- isc-dhcp: fix log file location

Which sort of tells me that ISC DHCP is still available in 24.1.6...

So now I am wondering:
a) is ISC DHCP removed in 24.1.6 and is that milestone line just an indication that development is moving forward clearing the way for removal in a future release post 24.1.6?
b) is the "Default DNS servers to offer to the client" hidden somewhere in 24.1.5_3, only available with 24.1.6 or not available at all yet?

For now I reverted back to ISC DHCPv4 and stay put at 24.1.5_3.
Based upon answers for above questions I can reconsider.

Thoughts??

Experiencing the exact same problem using 23.7.8.  :'(

Even if I create a group that consists of the WAN interface (set to never) and a single VPN interface (set to tier1) the rules using this group name as the destination gateway to be used gets my traffic out of the door via the WAN interface instead of the VPN interface. Only way I was able to change that behavior is selecting a single (VPN) gateway within the firewall rules. Which defeats the purpose of groups entirely :-(