Contents x
      Reaching Devices Behind an Edge iNode from Application Instances In Your Cloud
      • 24 Jul 2024
      • 1 Minute to read
      • Print
      • Dark
        Light
      Contents

      Reaching Devices Behind an Edge iNode from Application Instances In Your Cloud

      • Updated on 24 Jul 2024
      • 1 Minute to read
      • Print
      • Dark
        Light
      Article summary

      If you want to reach devices behind an Edge iNode from your application instance running in your cloud, use the instructions in this section. This is an optional step. For this to work, the application instance must be in same virtual private cloud (VPC) network as the Virtual iNode instance.

      To reach the devices on the local network behind Edge iNode from an application running on a virtual machine in your cloud subnet, you have to add a custom route in the virtual machine.

      Follow these steps:

      1. From the iNodes > All iNodes page, select the name of the Edge iNode to display iNode details.image26
      2. In the Networks tab, hover over the info icon next to the name of the remote network to which your local network connects. This displays a help pop-up with an instruction you can cut and paste to add a default route. For each virtual machine that needs to reach the local network, add a default route. After adding the default route, you can ping a device IP address on your local network from your application VM.image27
      • When a representational network is used for the local network behind Edge iNode, specify the corresponding representational network CIDR instead of the local network CIDR to add the route.
      • The route added using route add command doesn’t persist across reboot. When you restart your application instance, you must add the route again.
      • When more than one Edge iNode is connected to one Virtual iNode, for each local network you need to add a default route through the Virtual iNode.
      Was this article helpful?
      What's Next