Ron, When you add a dNAT rule in a VPC there's a drop down to select your tier, it might have defaulted a tier that doesn't have any VMs.
Cheers Alex From: Daan Hoogland <daan.hoogl...@shapeblue.com> Sent: 28 December 2024 02:31 To: users@cloudstack.apache.org Subject: Re: Problem encountered adding an instance to a port forward entry Ron, I just replayed your scenario in a lab environment * create a vpc * create a tier * create a vm * aquire a public ip * create a portforwarding rule for the ip and add the vm to it I've seen no strangeties. The only thing I can think of is the port range overlapping with something already assigned? ________________________________ From: Ron Gage <r...@rongage.org.INVALID<mailto:r...@rongage.org.INVALID>> Sent: 27 December 2024 22:08 To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org> <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>> Subject: Problem encountered adding an instance to a port forward entry Hi everyone! I must be doing something wrong here because I cannot enter a port forwarding rule on my VPC. CS Version 4.19.1.3. When I click on the "Add Instance" button in the UI (after specifying public and private port ranges) in the port forwarding tab, the new screen has no instances listed. The network tier searcher in the upper left of the screen is likewise empty. [cid:part1.XER7Iwkx.Op2UYOig@rongage.org] If I am understanding the terminology correct, I do indeed have a network tier defined as well as a couple of instances. From the VPC page: [cid:part2.UWBEnBLH.lseOd2Uh@rongage.org] Could someone please help me figure out what I am doing wrong here? Thanks! Ron Gage Westland, MI
