Messages

Reservations generally should be *outside* the range ("pool") of addresses that are "up for grabs". Kea DHCP supposedly allows for in-pool reservations, but I'm not sure that OPNsense leverages that properly. AFAIK, ISC DHCP doesn't support in-pool reservations at all.

Thank you for the answer!

Anyone else who can confirm how this works for OPNsense?

I have a DHCP Static Mapping of 10.3.33.133 within my DHCP range of 10.3.33.100-199. Even though 133 is leased to the correct MAC-address in first place it seems other clients gets 133 as well and I get duplicate clients with 133.

Is it not possible to reserve a DHCP Static Mapping IP address within a DHCP range or is this a bug?

Yes, opnsense-revert will give you the latest snapshot in this case. One caveat applies: your firmware mirror needs to sync the latest snapshots or use the main mirror as a workaround.


Cheers,
Franco

The results of my testing so far seems to be good  :)

A big thank you to all involved sorting this out, I wish I had more knowledge and comeptence to contribute.

# opnsense-revert -z miniupnpd

Final confirmation would be good. Obviously thanks to all involved in making this happen.

Does this mean we have a working version for OPNsense now???  ;D ;D ;D

"# opnsense-revert -z miniupnpd", is this the command to update miniupnpd without waiting for next OPNsense patch?

@franco, to be honest it's really hard to understand who is responsible for what??  :o

Who should we try to put some pressure on to get this mess sorted?

@franco, is it not possible to have the new version of miniupnp as a Hotfix as a temporary solution?

Seems like the same problem to me but I could be wrong? If it's fixed in pfSense why can't it be fixed in OPNsense?

I have also bumped this issue at the FreeBSD bugzilla. Is there anything else we can do to push to get this issue resolved as soon as possible?

Is it in OPNsense or miniupnp the rewriting needs to be done? Is there any preliminary time plan when this can be implemented?

Hey guys,

I'm quite new to OPNsense and my setup with three PC:s and two Xbox consoles depends on UPNP to work, especially Call of Duty: Warzone.

Why can't the new version 2.3.6 that resolves the problem introduced with OPNsense 24.1 be included in easily so we can update the plugin and get a working UPNP-function again? I believe I don't understand the dependencies between FreeBSD versions, miniupnd versions and how they are implemented within OPNsense?

Please try to oversee my lack of knowledge on the internals and try to give a easy to understand explanation.