Having trouble created WAN to LAN Access Rule

Started by fbeye, July 01, 2023, 07:17:18 PM

Previous topic - Next topic
Hi!

So my goal is, from anywhere remotely I am able to input my server ip and port 8888 [x.x.x.182 : 8888] into my Firefox and I am able to surf through my home Proxy which uses the VPN the Proxy container is attached to.
The container, tinyproxy, is running on 192.168.5.44:8888 alongside docker container nordvpn. When on the LAN I have verified the proxy does work.
My OPNSense [x.x.x.182] has subnet lan 192.168.5.x, so 192.168.5.44 is indeed incoming and outgoing using x.x.x.182.
ALL I have done thus far is in Opnsense;
QuoteFIREWALL;WAN;     IPv4 TCP    *    *    192.168.5.44    8888    *    * .

This apparently is either wrong, though I can not imagine why or how. Am I also supposed to make a LAN rule?

You need a NAT port forwarding rule. This will, by default, also create the firewall rule.

Interesting. So I removed all of what I had done and started over using your reference; I indeed see how it creates a rule alongside with it.

The NAT/Port Forwrd shows
QuoteWAN    TCP/UDP    *    *    WAN address    8888    192.168.5.44    8888    
The WAN/Rule shows
QuoteIPv4 TCP/UDP    *    *    192.168.5.44    8888

Here remotely in my firefox, I go to settings/proxy and type in x.x.x.182 8888 (and for https) and nothing loads.
I am wondering if I somehow need to see if the docker container which hosts tinyproxy (which runs through qbittorrent-vpn) has a firewall blocking anything outside the 192.168.5.0 LAN.