I am using version 4.5.2 with hypervisor CentOS 6 HVM. I am using advanced networking with VLAN's.
I've reviewed the log files and I think my VPC router is a complete mess. Rebooting take a very long time and when it comes back and I console into it, the virtual router has no IP addresses, just the local connection. I should see public addresses if I use 'ifconfig' from the VPC virtual router, correct? Can I safely destroy a VPC virtual router and ACS will rebuild a fresh one? Dustin On Fri, Aug 19, 2016 at 4:01 PM, Pierre-Luc Dion <[email protected]> wrote: > Can you tell us on what CloudStack version and hypervisor ? > > > > On Fri, Aug 19, 2016 at 3:00 PM, Dustin Wright < > [email protected]> wrote: > > > I don't believe so. Its a vanilla setup. I am going to keep > troubleshooting > > today and see if I can grab more log data. I do load balancing and port > > forwarding with a normal network, but for some reason its all messed up > > within this VPC. I am going to try creating a second VPC to see if the > > problem persists... > > > > I'm open to any other suggestions for troubleshooting. > > > > Dustin > > > > On Fri, Aug 19, 2016 at 2:56 PM, Pierre-Luc Dion <[email protected]> > > wrote: > > > > > Did you defined custom ACL on the network tier of the VPC that could > > > prevent to Port Forwarding to work ? > > > > > > > > > > > > > > > On Fri, Aug 19, 2016 at 12:58 PM, Dustin Wright < > > > [email protected]> wrote: > > > > > > > "Failed to apply port forwarding rule". The firewall and LB sections > > are > > > > crossed out? > > > > > > > > Now the port forwarding rules are there, but say "deleting". > > > > > > > > I create port forwarding rules for private networks fine. Within a > VPC > > > I'm > > > > stuck. > > > > > > > > I tried rebooting the VPC router and that did not resolve the > problem. > > > > > > > > Dustin > > > > > > > > > > > > On Fri, Aug 19, 2016 at 12:49 PM, Kirk Kosinski < > > > > [email protected] > > > > > wrote: > > > > > > > > > Hi, the attachment didn't go through. What's the error message > > you're > > > > > seeing? > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > [email protected] > > > > > www.shapeblue.com > > > > > 53 Chandos Place, Covent Garden, London WC2N 4HS > > > > > @shapeblue > > > > > > > > > > > > > > > > > > > > From: Dustin Wright [mailto:[email protected]] > > > > > Sent: Friday, August 19, 2016 7:19 AM > > > > > To: [email protected] > > > > > Subject: Port Forwarding within VPC > > > > > > > > > > ACS Users, > > > > > I have a client who has a VPC setup. They connect a few remote > > offices > > > > > back to the cloud to access remote desktops. Works well. Now they > > want > > > to > > > > > add a port forwarding rule to allow non-VPN access to a specific > > > > instance. > > > > > I attached another public IP, created the rule, but the rule fails, > > > > please > > > > > see the attached screenshot. > > > > > What do I need to do to be able to offer port forwarding within a > > VPC? > > > > > What am I missing? I assume my network offerings are wrong somehow. > > > > > Thanks in advance, > > > > > Dustin > > > > > > > > > > > > > > > > > > > > > > > > >
