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 - AlpAne

#1
26.7 Series / Re: os-upnp plugin not working?
September 30, 2026, 03:41:58 PM
Quote from: nero355 on September 25, 2026, 10:56:40 PM
Quote from: AlpAne on September 25, 2026, 12:07:07 PMHave anyone actually verified that this solution works for multiple PC/Xbox clients connecting through UPnP at the same time.
Like I said before in this topic : Forget OPEN NAT and keep things simple at a nice and comfortable Moderate NAT level with STRICT-PORT Enabled for your Gaming Clients :)

Could you please write a simple step by step guide how to do this?

Thank you in advance!
#2
26.7 Series / Re: os-upnp plugin not working?
September 25, 2026, 12:07:07 PM
Have anyone actually verified that this solution works for multiple PC/Xbox clients connecting through UPnP at the same time.

I have followed the steps described in this thread to get Xbox to show Open NAT and one PC running Call of Duty BO7/Warzone to show sometimes Moderate NAT and sometimes Open NAT but when second PC tries to connect it gets network error in Call of Duty, as soon as the first PC closes Call of Duty the second PC can connect.
#3
26.7 Series / Re: os-upnp plugin not working?
August 29, 2026, 01:45:13 PM
Quote from: BondiBlueBalls on August 28, 2026, 03:18:08 PMUPnP is working and displaying the internal IP again following the 26.7.3_x update. 🎉

You cannot view this attachment.

Can you please tell us wich NAT-settings and firewall rules you have set up to get it working except installing the UPnP-plugin. Can you verify that you get "Open NAT"?
#4
26.7 Series / Re: os-upnp plugin not working?
August 26, 2026, 03:37:36 PM
Quote from: franco on August 26, 2026, 03:03:18 PMWow, nice find!  Took the liberty to fold this into the ports tree for tomorrow's 26.7.3:

https://github.com/opnsense/ports/commit/2616876aaa


Cheers,
Franco

Will this solve the original problem with UPnP plugin with 26.7 or do we still need to manually configure the NAT mode from automatic to hybrid and add a source NAT rule as described as a fix earlier in this thread?
#5
26.7 Series / Re: Thank you Opnsense Team
August 12, 2026, 09:37:19 PM
I couldn't agree more to previous posters! Keep up the good work OPNsense-Team!
#6
Quote from: dseven on October 24, 2024, 06:31:16 PM
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?
#7
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?
#8
Quote from: franco on May 29, 2024, 07:25:35 PM
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.
#9
Quote from: franco on May 29, 2024, 05:59:26 PM
# 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?
#10
@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?
#11
@franco, is it not possible to have the new version of miniupnp as a Hotfix as a temporary solution?
#12
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?
#13
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?
#14
Is it in OPNsense or miniupnp the rewriting needs to be done? Is there any preliminary time plan when this can be implemented?
#15
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.