PBR is a technique used to make routing decisions based on policies set by the network administrator. 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.

See also: PBR with 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.:

  • Relies on the built-in netifd functionality and requires no extra software installation.
  • Suitable for network interfaces managed by netifd such as static, DHCP/DHCPv6, WireGuard, OpenConnect, PPTP, etc.
  • Can be used for network interfaces unmanaged by netifd such as OpenVPN using the PBR protocol.
  • Works well with interfaces, subnets, IP addresses and ports, but not domains.

See also: VPN policy routing, Routing example: VPN policy routing

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/subnets/domains.
  • 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.
  • Provide web interface to manage routing policies.

See also: mwan3, Routing example: Dual VPN with mwan3

mwan3 provides load balancing and failover with multiple WAN interfaces.

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2021/08/17 11:31
  • by vgaetera