SD-WAN

I am looking at a Conductor deployment in a Data Center, where it is desired to access the conductor by local routers/resources via a private network interface, say 10.0.0.0/8 network, while having branch and other DC routers access it via a public network interface. Has anyone deployed 128T Conductor for such a use case, with multiple network interfaces?

Gene,

Thank you for reaching out.

While the 128T Conductor does leverage 128T Software to fully manage, monitor, and orchestrate all 128T Routers within an authority, it does not leverage 128T software for packet forwarding as of version 3.2.2. Instead it leaves this task to the underlying Linux Kernel IP routing Table.

In such a situation where a Conductor might have multiple network interfaces, one would need to setup routing to accommodate both public internet routing as well as data center routing.

With the example above, one would set the default route for the public internet facing interface by ensuring the following is in the ifcfg file for that interface.

So, if the interface facing the public internet on your conductor was ""enp1s0f0"" , the file /etc/sysconfig/network-scripts/ifcfg-enp1s0f0 would need the following configuration to be used as the default route

DEFROUTE=yes

Meanwhile, if the interface enp2s2f2 were used to face the data center, and the data center routing could be summarized as 10.0.0.0/8, one would NOT set this interface to be the default route, but instead create a route file specifically to allow for this routing:

/etc/sysconfig/network-scripts/route-enp2s2f2

And it would have the following contents (for this theoretical example, the gateway for this interface is 10.1.2.3):

10.0.0.0/8 via 10.1.2.3 dev enp2s2f2

Since this is a more specific route than the default route (0.0.0.0/0) it will be more preferred over the internet-facing route.

Full Details on configuring static routes in Linux (RHEL & CentOS 7), can be found here:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-editing_network_configuration_files#sec-Configuring_Static_Routes_in_ifcfg_files

 

Thomas Sullivan

128 Technology

Please note: the new release 3.2.3 feature, which automatically sets up a conductor service for managing routers via forwarding interfaces, currently has a limitation of one IP address per Conductor node.