Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-user:network:routing:pbr [2021/08/16 23:31] – [PBR with netifd] vgaetera | docs:guide-user:network:routing:pbr [2023/09/27 02:36] – [PBR (Policy-Based Routing)] vgaetera | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== PBR (Policy-Based Routing) ===== | + | ====== PBR (Policy-Based Routing) ====== |
| + | See also: | ||
| + | [[docs: | ||
| [[wp> | [[wp> | ||
| There are different methods to implement PBR with their own pros and cons, and some methods can be more suitable than others depending on your goal. | There are different methods to implement PBR with their own pros and cons, and some methods can be more suitable than others depending on your goal. | ||
| - | ===== PBR solutions | + | ===== Solutions |
| + | ==== PBR app ==== | ||
| + | See also: | ||
| + | [[docs: | ||
| + | |||
| + | PBR app helps overcome routing issues for the following scenarios: | ||
| + | * Utilize split tunneling to route your traffic to VPN/WAN selectively for some of hosts/ | ||
| + | * Implement port forwarding on the WAN interface when traffic is routed to VPN by default. | ||
| + | * Run VPN client and server simultaneously and route traffic to the VPN client. | ||
| + | * Provide web interface to manage routing policies. | ||
| ==== PBR with netifd ==== | ==== PBR with netifd ==== | ||
| See also: | See also: | ||
| - | [[docs: | + | [[docs: |
| - | [[docs: | + | |
| PBR with netifd helps to utilize different routing tables to route traffic to a specific interface based on traffic parameters like ingress/ | PBR with netifd helps to utilize different routing tables to route traffic to a specific interface based on traffic parameters like ingress/ | ||
| * Relies on the built-in netifd functionality and requires no extra software installation. | * Relies on the built-in netifd functionality and requires no extra software installation. | ||
| - | * Suitable for network interfaces | + | * Suitable for managed |
| - | * Can be used for network | + | |
| * Works well with interfaces, subnets, IP addresses and ports, but not domains. | * Works well with interfaces, subnets, IP addresses and ports, but not domains. | ||
| - | |||
| - | ==== VPN policy routing ==== | ||
| - | See also: | ||
| - | [[https:// | ||
| - | [[docs: | ||
| - | |||
| - | VPN policy routing helps overcome routing issues for the following scenarios: | ||
| - | * Utilize split tunneling to route your traffic to VPN/WAN selectively for some of hosts/ | ||
| - | * Implement port forwarding on the WAN interface when traffic is routed to VPN by default. | ||
| - | * Run VPN server and client simultaneously and route traffic to the VPN client. | ||
| ==== mwan3 ==== | ==== mwan3 ==== | ||
| See also: | See also: | ||
| [[docs: | [[docs: | ||
| - | [[docs: | + | [[docs: |
| mwan3 provides load balancing and failover with multiple WAN interfaces. | mwan3 provides load balancing and failover with multiple WAN interfaces. | ||