All by IP. Private instances can't get hostnames because they can't get TCP/UDP back from DNS, so all testing is via IP.
-Chris - Christopher T. Hull I am presently seeking a new career opportunity Please see career page http://chrishull.com/career 333 Orchard Ave, Sunnyvale CA. 94085 (415) 385 4865 chrishul...@gmail.com http://chrishull.com On Thu, Mar 31, 2016 at 10:51 AM, Neil Jerram <neil.jer...@metaswitch.com> wrote: > On 31/03/16 18:40, Christopher Hull wrote: > > Hi all; > > Was originally DNS issue, but that was a downstream symptom. > > > > Instances on Private net can't access internet TCP, but CAN ICMP. ping > all. > > Details: > > 1. Instances on Public net work perfectly. > > 2. Instances on Private net can fully access Public net instances, both > > virtual and physical boxes. > > ssh from Private to Public instance works. > > http to OpenStack dashboard (physical box) from Private instance > works. > > 3. Private instances can ping everything, including the internet. > > By IP or by hostname? > > > 4. Private instances can NOT TCP to my ATT gateway. (public net) > > HTTP to ATT gateway which has a web interface fails. > > Same is true for internet. Ping, but no TCP (UDP?) > > Again, are these TCP attempts to an IP or to a hostname? > > Just want to be sure that this isn't still a name resolution issue. > > Neil > > > > 5. Floating IPs work. I think the Neutron Router is fine. > > > > Any ideas?? > > -Chris > > > > > > > > > > > > > > > > - Christopher T. Hull > > I am presently seeking a new career opportunity Please see career page > > http://chrishull.com/career > > 333 Orchard Ave, Sunnyvale CA. 94085 > > (415) 385 4865 > > chrishul...@gmail.com <mailto:chrishul...@gmail.com> > > http://chrishull.com > > > > > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
