How do I configure policy-based routing in QuWAN Orchestrator?

When configuring routing rules, it is important to understand the order of priority among different routing mechanisms. The system applies rules in the following order of precedence:

• Firewall rules
• Policy-based routing rules
• Static routes
• Quality of Service (QoS) rules
• Default routes

This priority ensures that specific, security-related configurations (such as firewall rules) are enforced before broader routing rules.

• Customizable routing criteria
  You can define routing paths based on factors such as source IP address, destination IP address, protocol type, packet size, port number, or user-defined tags.
• Enhanced traffic control
  PBR allows you to manage network traffic with greater precision, ensuring efficient routing strategies tailored to your requirements.

1.Multi-line fault tolerance

Assign specific traffic types to backup connections, improving network reliability during outages.

Use case: A logistics company relies on its network to transmit real-time shipment data from LAN interface port 5 to an external server at 203.0.113.10. To ensure uninterrupted communication, they configure a primary route that directs traffic through the next hop 192.168.1.1.If this route becomes unavailable, a backup route automatically takes over, allowing traffic from 203.0.113.10 to be forwarded through the next hop 192.168.2.1. This setup ensures continuous data transmission, preventing disruptions in critical logistics operations.

2.Application-based prioritization

Route latency-sensitive traffic of specific sources, such as video conferencing and voice calls, through optimized paths, while less critical traffic uses alternative routes.

Use case: A software development company uses LAN interface port 5 to handle video conferencing and voice call traffic. To ensure stable call quality, they configure application-based routing rules. Latency-sensitive traffic, such as calls, is prioritized and routed through optimized low-latency paths. Meanwhile, less critical traffic, like file uploads or general browsing, is redirected to alternative routes, ensuring high-quality communication for important meetings.

For example, suppose a development team uses the LAN interface port 5 to handle voice and video traffic. The traffic, such as SIP and RTP packets for voice and video calls, originates from the IP address 192.168.20.10. This traffic is routed through a low-latency optimized path using the gateway 192.168.1.1, ensuring that the calls and video conferencing experience high-quality communication with minimal delay. On the other hand, less critical traffic, like file uploads and general browsing originating from the same device, is sent through a different path, using a standard route with a gateway at 192.168.2.1. This separation ensures that non-critical traffic does not interfere with important communication tasks.

3.Localized traffic management

Apply distinct routing rules for traffic sending to specific regions or IP segments to meet organizational or regional needs.

Use case: An enterprise with global operations requires efficient routing for traffic between its locations. Traffic from the IP segment 192.168.1.1/24, destined for a US office network, follows a specific routing rule to ensure optimized paths that meet organizational and regional requirements, improving connectivity and performance.For example, traffic from a US office device (192.168.1.10) is routed locally via the next hop 10.1.1.1 for quick and reliable communication.However, traffic from the same device to a server in the Europe office (192.0.2.10) takes a different route through the next hop 10.1.1.1, ensuring efficient international routing while maintaining optimized local traffic flow.

PBR is particularly important in enterprise networks, data centers, and environments with multiple connections, providing unmatched flexibility to optimize network performance and meet diverse traffic management requirements.