Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
docs:guide-user:network:routing:pbr [2023/03/15 02:43] – [PBR / VPN policy routing / VPN bypass] vgaeteradocs: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: See also:
-[[docs:guide-user:network:routing:basics#policy-based_routing|How it works / Policy-based routing]]+[[docs:guide-user:network:routing:basics#policy-based_routing|Routing basics]]
  
 [[wp>Policy-based_routing|PBR]] is a technique used to make routing decisions based on policies set by the network administrator. [[wp>Policy-based_routing|PBR]] is a technique used to make routing decisions based on policies set by the network administrator.
Line 7: Line 7:
  
 ===== Solutions ===== ===== Solutions =====
 +==== PBR app ====
 +See also:
 +[[docs:guide-user:network:routing:pbr_app|PBR app]]
 +
 +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/subnets/domains.
 +  * 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:guide-user:network:routing:pbr_netifd|PBR with netifd]], +[[docs:guide-user:network:routing:pbr_netifd|PBR with netifd]]
-[[docs:guide-user:network:routing:examples:pbr_netifd|Routing example: PBR with netifd]]+
  
 PBR with netifd helps to utilize different routing tables to route traffic to a specific interface based on traffic parameters like ingress/egress interface, source/destination address, firewall mark, etc.: PBR with netifd helps to utilize different routing tables to route traffic to a specific interface based on traffic parameters like ingress/egress interface, source/destination address, firewall mark, etc.:
Line 16: Line 25:
   * Suitable for managed and unmanaged interfaces declared in the network configuration.   * Suitable for managed and unmanaged interfaces declared in the network configuration.
   * Works well with interfaces, subnets, IP addresses and ports, but not domains.   * Works well with interfaces, subnets, IP addresses and ports, but not domains.
- 
-==== PBR / VPN policy routing / VPN bypass ==== 
-See also: 
-[[https://docs.openwrt.melmac.net/pbr/|PBR]] / [[https://docs.openwrt.melmac.net/vpn-policy-routing/|VPN policy routing]] / [[https://docs.openwrt.melmac.net/vpnbypass/|VPN bypass]], 
-[[docs:guide-user:network:routing:examples:pbr_app|Routing example: PBR]] 
- 
-PBR / VPN policy routing / VPN bypass helps overcome routing issues for the following scenarios: 
-  * Utilize split tunneling to route your traffic to VPN/WAN selectively for some of hosts/subnets/domains. 
-  * 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. 
  
 ==== mwan3 ==== ==== mwan3 ====
  • Last modified: 2023/10/29 00:46
  • by vgaetera