NAT Query - should be simple?

billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: NAT Query - should be simple?

Post by billion_fan »

evansnp wrote:
basiluk wrote:Ok a little clarification here.

What I need to perform is as follows:

IP 180.1.2.3.4 needs port 443 open
IP 190.1.2.3.5 needs port 443 open
IP 192.1.2.3.6 needs port 80 open
IP 192.1.2.3.7 needs port 80 open
etc

If I do 121 NAT then all four IP's have all ports opened. If I use virtual servers then it will only accept one IP per port designation. SO how do I open the same port on multiple public IP's?
As long as you don't mind using custom ports externally, then this is an ideal candidate for using VMs.
e.g. for 190.1.2.3.4, you could use external port 8443, mapped to 443 internally; IP 190.1.2.3.5 use 9443, mapped to 443 internally etc.

Otherwise known as port re-direction, for when you only have 1 WAN/public IP address
basiluk
Posts: 15
Joined: Tue Feb 17, 2015 12:57 pm

Re: NAT Query - should be simple?

Post by basiluk »

Thanks, that is a good suggestion - bi of a pain but would work.

Hope that Billion introduce the proper way as a feature!
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: NAT Query - should be simple?

Post by billion_fan »

basiluk wrote:Thanks, that is a good suggestion - bi of a pain but would work.

Hope that Billion introduce the proper way as a feature!
That solution is only for when using 1 WAN IP.

If you are using public range(in 121 NAT mode), all ports will open/mapped the that public address, so there is no need open/map ports as they are already mapped/open. (as shown on my screen shots, you can see I don't need any virtual servers and ports are showing as open for the WAN IP set within 121 NAT)

So once you have setup 121 NAT, all the ports that you need will mapped/open correctly (only when you are behind normal NAT will need port forwarding with 1 public IP as you can't have external access to two devices running on the same port, hence port direction is solution)
Post Reply