Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    I think the issue is that, the next hope has to be on the same network that you are on. ie you can set your default route to use 192.168.11.18. In turn that system will then know where to go next on the 172.16.x.x network.
    – grag42
    Commented Apr 22, 2015 at 21:49
  • You might well be right (I'm an absolute beginner at this stuff). But this feels like it would require routers all over the place (ie: 192.168.11.18 has to be a router...). This may not be relevant but the reason I want to target 172.16.111.99 specifically is that it's a firewall appliance, running inside a VM hosted by 192.168.11.18.
    – sxc731
    Commented Apr 22, 2015 at 21:52
  • 1
    There are routes all over the place and the needed routes. There are network protocols that take care of that on the internet. Default route is usually used to get you to the internet. Generally you will only have to add routes if you are connecting to a network that is behind a router that is not along your default route.
    – grag42
    Commented Apr 22, 2015 at 21:57
  • I have not tried to configure that kind of setup. but, i would think that you will need on the external box to default route to 11.18, then on 11.18 forward or route (depending on how your vm network is setup) to 111.99. From there the 111.99 can handle the traffic
    – grag42
    Commented Apr 22, 2015 at 22:07
  • @grag42 cheers. Your first comment is likely the correct answer to my q. Please post it as a reply so I can accept it. Thanks again!
    – sxc731
    Commented Apr 22, 2015 at 22:14