• Topic ID: id_2019734
  • Version: 2.0
  • Date: Oct 13, 2019 7:17:09 PM

Creating Routing Table for InSite RSvP connectivity through GE VPN Proxy

In certain customer sites where the VPN router IP Address is not in the same subnet as that of the customer site gateway IP address, a route is needed in order for these MR systems to connect to the InSite back office.

Adding a Static Route

To add a persistent route to the external interface of the MR scanner, follow these steps:

  1. Determine the parameters needed to set up the static route:

    • the network address of the destination network: 150.2.0.0
    • the netmask to determine which hosts are in and out of the destination network: 255.255.0.0
    • the gateway address to send these packets to: This detail needs to be obtained from the customer IT department
  2. Open a command prompt and change over to root user using the “su –“ command
  3. Determine the name of the external interface of the system using the mr-network-cli command

    [root@t19 ~]# /usr/local/bin/mr-network-cli --get-interface-name external 
    enp0s25 

    The output of the above command indicates the name of the external interface is enp0s25. Replace <ext eth port> in the steps below with the name of the interface for your specific machine.

  4. Create the /etc/sysconfig/network-scripts/route-<ext eth port> file as root

    [root@t19 ~]# gedit /etc/sysconfig/network-scripts/route-<ext eth port> 
  5. Populate it with the following information, then save and quit:

    ADDRESS0=150.2.0.0 
    NETMASK0=255.255.0.0 
    GATEWAY0=x.x.x.x 

    where x.x.x.x is the customer site gateway ip address

  6. Restart the networking subsystem with the service command:

    [root@t19 ~]# service network restart  
    Restarting network (via systemctl): [ OK ] 
    root@t19 ~]# 
  7. Confirm that the route was added - use the ip route command to check:
  8. [root@t19 ~]# ip route
    ...
    150.2.0.0/16 via x.x.x.x dev enp0s25
    ...
    

The static route will be added at boot time when the interface is brought up.

You can add more such static routes as needed in the route-<ext eth port> file using incremental suffixes for ADDRESS, NETMASK, and GATEWAY for the additional entries. Example:

  • the second static route would use ADDRESS1, NETMASK1, GATEWAY1
  • the third static route would use ADDRESS2, NETMASK2, GATEWAY2

Removing the Static Route

Remove the /etc/sysconfig/network-scripts/route-<ext eth port> file to remove all external static routes. You can remove the ADDRESSn, NETMASKn, and GATEWAYn entries from the same file if you want to remove just a single route. Restart the network with service network restart to remove the route on the running machine without rebooting.

The network configuration scripts cannot handle gaps between entries, so make sure any remaining entries have contiguous numbering. Given the following example:

ADDRESS0=...
NETMASK0=...
GATEWAY0=...
ADDRESS1=...
NETMASK1=...
GATEWAY1=...
ADDRESS2=...
NETMASK2=...
GATEWAY2=...

Removing ADDRESS2, NETMASK2, and GATEWAY2 without renumbering is okay.

Removing ADDRESS1, NETMASK1, and GATEWAY1 without renumbering ADDRESS2, NETMASK2, and GATEWAY2 will result in this route not being applied.