This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
advanced-pbr [2022/01/31 22:55] – clarity, grammar hogwild | advanced-pbr [2023/06/05 03:19] – [Rules] -formatting hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== MultiWan Routing ===== | ===== MultiWan Routing ===== | ||
- | While similar to the Routing menu, the MultiWAN Routing menu allows you to direct outbound traffic in multiwan scenarios. On this menu, you can define advanced parameters to make a connection bind to a specific WAN. Directing traffic outbound will implicitly affect the corresponding return traffic as well. A packet going to WAN0 is expected to return only via the same interface. | + | While somewhat |
- | \\ | + | 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. |
- | {{: | ||
- | **On**: When enabled, makes the routing rule on that line of the table active. | + | ===== Rules ===== |
- | **Protocol**: | + | {{:pasted: |
- | | + | **On**: When checked, this enables the routing rule on that line of the table. |
+ | |||
+ | **Protocol**: | ||
+ | |||
+ | | ||
* TCP+UDP | * TCP+UDP | ||
* TCP | * TCP | ||
Line 17: | Line 20: | ||
* ICMP | * ICMP | ||
- | Here you can choose the transport protocols that should be matched by the rule. Note that there are hundreds of layer 4 protocols. This menu and this setting refer only to the most common ones. | + | **Source Address**: |
- | + | ||
- | **Source Address**: | + | |
* All | * All | ||
Line 25: | Line 26: | ||
* MAC | * MAC | ||
- | Filters in the defined | + | **Destination Address**: |
- | **Destination Address**: | + | |
+ | | ||
+ | | ||
- | All | + | **Select WAN**: |
- | IP | + | **Description**: |
- | Domain | + | Rules defined will take precedence over any WAN's weight-related setting. |
- | 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. | + | \\ |
- | + | ||
- | **Selected WAN**: WANx - Specfies the logical interface where the defined traffic should be sent outbound. | + | |
- | + | ||
- | **Description**: | + | |
- | Please note that the rules defined will take precedence over any WAN's weight-related setting.\\ | + | |