Quote from: nero355 on July 22, 2026, 06:44:07 PMI mean, even on previous releases, if I didn't have the rule things would complain about strict NAT. With the rule all is fine. I've never gotten the UPNP plugin to give "open NAT" on OPNSense, pretty sure it's not possible in the current releases, but moderate is sufficient to get games to stop complaining so meh.Quote from: Warbreaker on July 22, 2026, 10:12:52 AMIt seems that way now, I didn't need it on 26.1 but the reason of why it was working is unknown to me, but now you do need it with 26.7IMHO you found a bug, because why would you need both of them when uPnP does more than a Source NAT Rule with Strict-port Enabled does : It completely opens the port like a Port Forward a.k.a. Destination NAT Rule would :)
Quote from: mbrogies on July 22, 2026, 10:00:14 PM[...]They are handled by the Layer3 Switch. Just routing, no firewalling, nothing...
Security is technically not existend with that setup.[...]
Quote from: teddybearnemo on July 22, 2026, 08:14:39 PMVLAN 10 Management
- here in goes my OPNSENSE and my Switch
VLAN 20 Trusted devices
- here goes my PC
VLAN 30 Guest WIFI
- here goes an AP ( doesn't know VLAN )
Quote from: teddybearnemo on July 22, 2026, 08:14:39 PMI dont know if VLAN 10 needs any rules or something ? some said it does, because it needs updates, and some say it doesn't because thats within the software so that i can update opnsense....i know the switch would be a file that i download on the website tp link and then upload it in the gui of the switch.In this case, there is no rule needed on VLAN10, expect for NTP if the swicht request it.
Quote from: Bob.Dig on July 22, 2026, 10:33:10 PMThis makes no sense to me to begin with.
Quote from: ivoruetsche on July 21, 2026, 12:10:15 AMFloating rule:This makes no sense to me to begin with.
Interface: nothing selected