"Recent posts
#21
25.7, 25.10 Series / Re: in dnsmasq dhcp: leases: b...
Last post by franco - January 15, 2026, 09:18:01 PMThe best course of action would be asking over at Dnsmasq for a canonical way to delete a single lease on FreeBSD?
Cheers,
Franco
Cheers,
Franco
#22
25.7, 25.10 Series / Re: in dnsmasq dhcp: leases: b...
Last post by pseudonym3k - January 15, 2026, 09:14:22 PMAs I mentioned I did read in github and others that the delete button is not coming (I am not the OP of this thread).
It's not about micromanaging... that's unfair and rather harsh. There are many uses for specific IP assignment and getting it all set up in one go, instead of breaking the task up because a lease won't expire for some times. Yes the client should be doing the release but not all devices do it.
I'm unclear why other DHCP products and even at least some past DNSMasq products were able to help here, but this one won't.
It's not about micromanaging... that's unfair and rather harsh. There are many uses for specific IP assignment and getting it all set up in one go, instead of breaking the task up because a lease won't expire for some times. Yes the client should be doing the release but not all devices do it.
I'm unclear why other DHCP products and even at least some past DNSMasq products were able to help here, but this one won't.
#23
General Discussion / Re: Forward local port to WAN...
Last post by viragomann - January 15, 2026, 08:43:36 PMThis is not, what I suggested.
Your rule translates the source address to the modems IP (192.168.33.1) and the source port to 80?
Just obey the suggestion and access the device by its IP then.
Your rule translates the source address to the modems IP (192.168.33.1) and the source port to 80?
Quote from: teclab on January 15, 2026, 08:37:33 PMBut getting a timeout when opening http://opensense:88So this is expected.
Just obey the suggestion and access the device by its IP then.
#24
General Discussion / Re: Forward local port to WAN...
Last post by teclab - January 15, 2026, 08:37:33 PMConfigured it:
But getting a timeout when opening http://opensense:88
Code Select
Interface Source Source Port Destination Destination Port NAT Address NAT Port Static Port Description
WAN LAN1 net tcp/ * This Firewall tcp/ 88 192.168.33.1/32 80 NO
But getting a timeout when opening http://opensense:88
#25
25.7, 25.10 Series / Re: Dnsmasq stops occasionaly
Last post by Monviech (Cedrik) - January 15, 2026, 08:12:02 PMNo problem it would be really helpful if you can find something. Thanks for testing :)
#26
25.7, 25.10 Series / Re: Dnsmasq stops occasionaly
Last post by ligand - January 15, 2026, 08:05:38 PMMy bad... Thank you for reorienting me. I'm testing again.
#27
25.7, 25.10 Series / Re: Any dates as to when 26.1 ...
Last post by franco - January 15, 2026, 07:31:58 PMPS: not seeing the upcoming release name here at all...
#28
25.7, 25.10 Series / Re: Any dates as to when 26.1 ...
Last post by franco - January 15, 2026, 07:30:55 PM #29
General Discussion / Re: Forward local port to WAN...
Last post by viragomann - January 15, 2026, 06:39:54 PMYou only need an outbound NAT rule on the WAN interface:
destination: 192.168.33.1/32
translation: virtual WAN IP
destination: 192.168.33.1/32
translation: virtual WAN IP
#30
25.7, 25.10 Series / Re: in dnsmasq dhcp: leases: b...
Last post by Monviech (Cedrik) - January 15, 2026, 05:56:18 PMDnsmasq will not get a lease delete button.
Adjust your workflow around that fact, maybe stop to micromanage DHCP leases and just turn them into reservations without changing the IP address?
For Dnsmasq it doesnt matter if the lease is inside the range, it will be reserved unlike in ISC.
Reference, we tried but decided against it ultimately: https://github.com/opnsense/core/pull/8899
DHCP is a contract between client and server that for as long as the lease time is valid, the IP is allowed to be used ONLY by the client and unique. There is no control protocol that can update the fact that the server deleted the lease to the client. Only the client can send a DHCPRELEASE to tell the server to delete the lease. Deleting leases on the server is always unexpected for clients and not a good workflow.
Adjust your workflow around that fact, maybe stop to micromanage DHCP leases and just turn them into reservations without changing the IP address?
For Dnsmasq it doesnt matter if the lease is inside the range, it will be reserved unlike in ISC.
Reference, we tried but decided against it ultimately: https://github.com/opnsense/core/pull/8899
DHCP is a contract between client and server that for as long as the lease time is valid, the IP is allowed to be used ONLY by the client and unique. There is no control protocol that can update the fact that the server deleted the lease to the client. Only the client can send a DHCPRELEASE to tell the server to delete the lease. Deleting leases on the server is always unexpected for clients and not a good workflow.
