The RELIANOID Load Balancer is engineered to seamlessly integrate into multiple subnets, facilitated by a robust routing system governed by predefined rules and customizable tables. Each rule defines specific conditions for packet handling and routing.
The system ensures that packets arriving at a Virtual IP (VIP) are forwarded to the backend through the same routing table used by the VIP. If the backend isn’t directly reachable via a configured subnet, the packet is directed to the gateway specified in the VIP’s routing table. This methodology prevents asymmetric routing, ensuring consistent packet management.
While each subnet should be configured uniquely across interfaces to avoid routing conflicts, users retain the flexibility to modify this behavior. Custom rules and route tables can be added, adapting the Routing module to suit individual network requirements.
Routing Rules List #
The Rules table below outlines the configured rules within the system:
Fields Description:
ID. Unique identifier for each rule, non-configurable.
Description. Brief explanation of the rule’s function.
From. Source CIDR (IP/bitmask) for incoming packets.
Not match. Option to negate the condition (disabled by default).
Table. Destination table where matched packets are routed.
Priority. Priority of the rule; lower numbers indicate higher priority.
Bulk actions:
Create routing rule. Initiates the creation of a new routing rule.
Delete. Removes selected rules from the table.
Add routing rule #
Table. Specify the routing table where packets matching this rule will be directed.
From. Define the source IP or CIDR (IP/mask) for incoming packets.
Priority. Assign a priority number to determine rule precedence.
Description. Provide a brief description outlining the purpose of this rule.
Not match. Optionally negate the condition if necessary.
This configuration allows for precise control over packet routing within the load balancer environment, ensuring optimal network performance and adherence to specific routing requirements.
