Network | Routing | Tables

In SKUDONET ADC, each routing table knows about the subnets of the ADC’s configured interfaces. This means that the system can forward packets to any destination network through any configured table.

For example, eth0 manages the subnet, and eth1 manages The tables table_eth0 and table_eth1 also know about each other’s subnets.

This means that if a packet reaches a VIP in table_eth0 with a backend in the network (reachable through eth1), table_eth0 will forward the packet directly to network through table_eth0.

However, if a subnet is not known through any other routing table, then that network may be unreachable through the selected table.

The image below shows a list of all the routing tables that are configured in the system.

Each table has the following properties:

  • Name: A unique name for the routing table.
  • Configure: An Action button that allows you to configure the selected routing table.

Next Article: Network | Routing | Tables | Configure

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support

Download Skudonet ADC Load Balancer
Community Edition

Source Code

A versatile and installable ADC system designed for diverse vendor hardware.


Installable ISO 

Load Balancing as a Service alongside an ADC orchestration toolkit.

Download Community Edition

Download Community Edition

“We manage the information you provide with the sole aim of assisting with your requests or queries in regards to our products or services; applying the computer and security procedures to ensure its protection. Your data can be rectified or removed upon request but won’t be offered to any third parties, unless we are legally required to do so.” Responsible: SKUDONET SL -