YAPFQ - Yet Another Port Forward Question

[S7evin]

Hi all,

My first question here.  I followed the numerous posts in this forum to setup a NAT rule for Plex, port 32400.


INTERFACE: WAN
TCP: IPV4
Protocol: TCP
Source: Nothing changed
Destination: WAN Address
Destination Port Range:  32400 to 32400
Redirect Target IP:  192.168.X.100
Redirect Target Port: 32400
NAT Reflection: Enable
Filter rule association: Pass

Plex is showing that it's connected through port forward inside the settings...and I can go to app.plex.tv and connect to my server without issue...however, I can't seem to get my WAN IP with port 32400 to respond in my browser to view plex web.  I use a dynamic dns domain so that family can utilize Plex with me and that's not working when I use it either.

Anyone have any ideas what is going on?  How do I test connections to my dynamic domain and/or WAN IP to make sure that it works?

Is there a setting that prevents LAN traffic for a specific port from hitting WAN IP outside?

[S7evin]

So, I was able to successfully test the port was open and forwarded by connecting to my mobile hotspot and testing then.


The question then becomes...what is there in the default settings of Opnsense that blocks a local LAN computer from accessing the public WAN IP?

[Animosity]

Generally, I find NAT reflection to be annoying so I just stay away from it.

If you have Unbound, just do a DNS override for your "outside" name so it resolves inside.

So app.domain.com might be 26.246.12.23 for the outside world, but inside, I have an override for 192.168.1.30

So it works locally.

I assume you have plex.domain.com so just override it and be done with it.

You seem to have NAT reflection setup so without seeing more details on what the error is, logs, not sure how easily that will be to fix.