Differences

This shows you the differences between two versions of the page.

--- advanced-pbr [2022/01/26 18:33] – rs232
+++ advanced-pbr [2023/06/10 17:27] (current) – [MultiWan Routing] -change title to "MultiWAN" hogwild
@@ Line 1: / Line 1: @@
-===== MultiWan Routing =====
+===== MultiWAN Routing =====
-Similarly to the Routing page the MultiWAN Routing allows you to affect traffic outbound in case of multiwan scenario. In this page you can define advanced parameter to make a connection "sticky" to a specific WAN. Directing traffic outbound will implicitly affect the return traffic as well; so a packet going to WAN0 is expected to return to the same interface only.
+While somewhat similar to the Routing menu, the MultiWAN Routing menu allows you to direct outbound traffic in multiwan scenarios.
-{{:pasted:20220126-181958.png}}\\
+This menu lets you define advanced parameters to make a connection bind to a specific WAN. Where outbound traffic is directed will implicitly affect the corresponding (inbound) return traffic. A packet going to WAN0 should return only via the same interface.
+===== Rules =====
+{{:pasted:20220126-181958.png}}\\  \\
+**On**: When checked, this enables the routing rule on that line of the table.
+**Protocol**:  This lets you choose the transport protocols that will be matched by the rule. There are hundreds of layer 4 protocols. This menu and setting refer to only the most common ones.
+  * All Protocols * (Default).
+  * TCP+UDP
+  * TCP
+  * UDP
+  * ICMP
+**Source Address**:  Filters in the defined source of traffic. All filters in all LAN devices. The IP setting allows you to define a specific IP address or set of addresses using a netmask syntax (e.g. 192.168.1.0/24), where MAC binds the rule to a defined MAC Address only.
+  * All
+  * IP
+  * MAC
+**Destination Address**:  Similar to the source IP, the destination address makes the rule more restrictive based on/or destination address. This can be defined as ALL (as in Internet), IP address or set of addresses, defined in a netmask format or even a destination domain.
+  * All
+  * IP
+  * Domain
+**Select WAN**:  (WANx) - Here, you choose the logical interface where the defined outbound traffic will be directed.
+**Description**: In this field, you can enter any notes you wish to make management easier.\\
+Rules defined will take precedence over any WAN's weight-related setting.
+ \\
+ \\ \\
-**On**: If enabled makes the rule active.\\
-**Protocol**: All/TCP+UDP/TCP/UDP/ICMP - Here you can define the transport protocol that should be matched by the rule. Please not there are hundreds of layer 4 protocols this page and this setting in particular refers to the most common only.\\
-**Source Address**: All/IP/MAC - Filters in the defined source of traffic. All stands for all LAN devices, IP allows you to define a specific IP or set of IPs in a netmask syntax (e.g. 192.168.1.0/24), where MAC binds the rule to a defined MAC address only.\\
-**Destination Address**: All/IP/Domain - Similarly to the source IP the destination address makes the rule more restrictive based on/or destination address. This can be defined as ALL (as in Internet), IP or set of, defined in a netmask format or even a destination domain.\\
-**Selected WAN**: WANx - Is the logical interface where the defined traffic should be sent to in outbound.\\
-**Description**: Free text field to ease the management.\\
-Please note the rule defined will take precedence over any WAN's weight related setting.\\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools