Multiple external IP Address support per virtual network in WAP with HNV Gateway
In WAP only one external IP address from Windows Azure Pack is possible on a virtual network. If multiple virtual machines require a NAT rule on the same port (for instance 443) then multiple external IP addresses are required.
Thanks for your suggestions and ideas! This is now possible if using Azure Pack UR8 which went out today!
As you can see Gisli the WAP team hasn't completed this so they are still working on it. In the KBs for UR7 it is said that the feature is not complete and will be completed with WAP integration in future URs.
Gisli Gudmundsson commented
The rollup did not contain adding multiple ip through the WAP but only through powershell. Hopefully it will be added in RU8.
Stefan Denninger @ acpcloud.rocks commented
Hey Marc, arival is near! Looking forward to RU7, great!!
Vahric Muhtaryan commented
Exactly, this means service providers like us manage such ip addresses for customers (hard to do) and also another question here , when you start to support multiple ip address how you (or ourself ) will migrate such manually defined ip addresses to the customer context ?
I would not call this workaround as it is not available trough WAP and also VMM.
This is a workaround, but would definitely like to have a solution supported by microsoft.
Ivan PATILLON commented
I do agree with Stanislav Zhelyazkov, it's important in case of multiple VMs doing some SSL websites.
Agreed, this feature is badly needed. Currently, this is a dealbreaker for us.
I agree with Marc and Stanislav, There are some cases where multiple VMs will require NAT rule for the same port (443,80). As a workaround we have been asked to create the rules statically on edge routers.
Nanang Astrianto commented
How to add ip proxy on mozilla ?
Nanang Astrianto commented
Darryl van der Peijl commented
This feature will definitely contribute on the practical use of NVGRE.
1 external IP per VM Network is in many situations not workable.
Thomas Maurer commented
Would love to see more about this feature!
Jesper Jensen commented
Agree with Stanislav.
It seems that the limitation is VMM and WAP. It's possible to add the IP's to Windows Server Gateway manually via PowerShell, but you can't add it via VMM or the WAP portals.
Currently you can assign only one Public IP per VM Network. It will be great if you can assign multiple Public IPs per VM Network and this to allows you to create NAT rules for every Public IP. In the end you can have something like this:
Name Public IP Protocol Source Port Destination IP (internal) Destination Port
rule1 126.96.36.199 tcp 443 vm1.contoso.com (192.168.10.12) 443
rule2 188.8.131.52 tcp 444 vm1.contoso.com (192.168.10.12) 444
rule3 184.108.40.206 tcp 443 vm3.contoso.com (192.168.10.13) 443