All Port Forwards Broken with Latest Update (26.1.6) (Resolved)

[LostSpark]

I admit I may be doing something wrong here, and I'm hoping I can get some pointers from some kind onlookers.

I had multiple ports forwarded correctly just two days ago, but I've updated twice since then and realized that since this period all of my port forwards are now completely broken.

I was previously already upgraded to 26.1, so this was likely 26.1.5 or 26.1.6 that did me in. Everything worked on 26.1.4.

If it's relevant, I use two gateway groups with failover from fiber to cellular (works great, and sends me alerts through monit). This is the only non-standard thing I can think of here...

I am still using the "old" rules, but I went ahead and deleted every rule for one of my game server ports and I started fresh with a new Destination NAT forward (with "pass" set up). I also tried a manual setup where I created a old rule, and then a new rule, and absolutely nothing let the traffic through...

The only other thing I can think of here is that somehow Crowdsec is blocking this. I just don't know why it would suddenly do this, that's all... so I figured I'd ask here and see if anyone else has had a similar problem, or could shed light on this problem that's plagued me for 6-7 hours now.

Thank you in advance to anyone who might be able to help!

[LostSpark]

After reviewing the changelog, I can see a lot of NAT changes were made in this latest update. Something about these changes has broken the entire way I had things set up. This is very likely the biggest clue to follow here, I'm thinking.

[LostSpark]

So, this is wild... I've  not experienced this before, and perhaps it has something to do with the update, or just some misfortune... my WAN (fiber) IP was wrong inside OPNsense. I didn't catch it until many hours of frustration, but it was simply not the same IP as what I got when I typed "what is my IP" into google. Manually restarting my modem fixed the problem...

Normally this is something most people do in the early stages, but my modem is in a crawl space under my house and I hadn't had this issue before.