L3 to the host rack on a laptop external routing issue

  • 1
  • Question
  • Updated 2 years ago
I am under the impression that the (part II L3 to the host) is suppose to allow me to reach out to the internet?

I set it up, and I can ping the router as well as the other instances from within an instance, but I am not able to get out externally to say google.  Is there a step I am missing?
Photo of Ryan Ruscett

Ryan Ruscett

  • 90 Points 75 badge 2x thumb

Posted 2 years ago

  • 1
Photo of Andrius Benokraitis

Andrius Benokraitis, Alum

  • 362 Points 250 badge 2x thumb
Hi Ryan, you're seeing what was originally designed. Our next version/update of this demo will allow for access to the Internet. You aren't doing anything wrong, as it was originally designed as a standalone no-internet kiosk mode. Stay tuned!
Photo of Ryan Ruscett

Ryan Ruscett

  • 90 Points 75 badge 2x thumb
Hey, 

Thanks, but can this be done? For example: I took the Ext_Rtr and changed around the interfaces so it would NAT out the vbox gateway. I can access the internet and I can ping my openstack instances from it. I can ping to Ext_Rtr  as well on 203.0.112.1. Except, for the life of me I can't get this to route from 203.0.112.1 out the gateway that vbox has 10.0.2.2. ALthough the RDO Servers have this gateway too and they can't access the internet. 

I love a good challenge but f it's not possible for some reason or another. I am good with that too lol. 

Thanks!
Photo of Scott Suehle

Scott Suehle, Alum

  • 3,772 Points 3k badge 2x thumb
With some tweaking to he configuration it should be possible. As stated above, this was created to give a look at the setup in a stand alone manner. Give is a chance to take a look at the configurations used and see what can be done.
Photo of Ryan Ruscett

Ryan Ruscett

  • 90 Points 75 badge 2x thumb
Hey,

I deleted my last post since all that stuff is not relevant anymore. I was able to install OVS on the Virtual External Router. Created a switch, added eth0 which I changed to be my NAT from Virtualbox. Then eth1 is the 192 and eth2 is the 203. 

I then just created one simple nat rule to nat traffic from Eth2 to the ovs switch. This way it re-writes the IP with the outgoing box IP and route through virtual box 10.0.2.2 and out to the internet. 

I was able to get this instance up and working so now I have 2 cloud fedora images deployed using the example heat templates. Sweet!
(Edited)