Port Forward Virtual IP

[jjonsson]

I can't get portforward to work with a virtual IP. What am I doing wrong ?

The WAN port is X.X.199.3/24. I have added a virtual IP of X.X.199.4/24

I have port forward from WAN address to internal host and I have port forward from virtual Ip to internal (different) host.
WAN address to 192.168.10.12


Virtual IP to 192.168.10.16


If entering https://X.X.199.4/ host on WAN address (192.168.10.12) is shown, not on virtual IP (192.168.10.16)

Any help appreciated...

[Ciprian]

Hello!

You need NAT -> Port-Forward Rules also, in conjunction with Firewall Linked Rules to those NAT -> Port-Forward rules.
You didn't mention anything about P/F rules, do you have them? What are those looking like?

PS I don't have such or similar setup scenario, so I think that, as you need some reverse proxy rules, port forward might not be enough. To be seen, discussed, and tested.

[jjonsson]

Ok, this is very strange. Port forward to X.X.199.4 works as long as no similar portforward is setup to X.X.199.3

I have portforward to SSH up running. I get correct server when using X.X.199.4 (No portforward is setup on port 22 to X.X.199.3 -> 192.168.12)
Same does not apply with X.X.199.4. Both port 80/443 forwards to X.X.199.3 instead.

For X.X.199.3 I'm using "WAN address" in port forward rule. For X.X.199.4, I'm using "X.X.199.4" in port forward rule. I can't use X.X.199.3 instead of WAN address (seems like that would solve the issue).

Is this a bug or ?

[bladman]

Ok, this is very strange. Port forward to X.X.199.4 works as long as no similar portforward is setup to X.X.199.3

I have portforward to SSH up running. I get correct server when using X.X.199.4 (No portforward is setup on port 22 to X.X.199.3 -> 192.168.12)
Same does not apply with X.X.199.4. Both port 80/443 forwards to X.X.199.3 instead.

For X.X.199.3 I'm using "WAN address" in port forward rule. For X.X.199.4, I'm using "X.X.199.4" in port forward rule. I can't use X.X.199.3 instead of WAN address (seems like that would solve the issue).

Is this a bug or ?

I have had the same issue after upgrading from 16.x.

You have to create an Alias (Firewall -> View -> Aliases) and create an alias called WANIP with the primary IP address of your router (so the WAN Address).

After that change the rule that has WAN Address in it and set the Destination address to your newly created alias. After that everything starts working.

It seems that the bug is that instead of WAN Address being used, the WAN NET is being used in the port forward.