Configuring Filter-Based Forwarding
Configure a firewall filter that forces a lookup against the different routing tables. Any routes that match the specified forwarding class specified and then match a specified topology are installed in the routing table for that topology. To configure a firewall filter for MTR that performs filter-based forwarding, include the following configuration at the [edit firewall] hierarchy level:
[edit firewall]family inet { # inet6 is also supported.filter topology-selection {term ef {from {forwarding-class expedited-forwarding; # The following
class types are also
# supported: assured-forwarding, best-effort, and network-control.}then {topology voice; # Specify the name of a configured topology.accept;}}}}
# supported: assured-forwarding, best-effort, and network-control.}then {topology voice; # Specify the name of a configured topology.accept;}}}}
You must apply the filter to an ingress interface. Include the following statements at the [edit interfaces] hierarchy level to apply the filter to an interface:
[edit interfaces]fe-2/2/1 {unit 0 {family inet {filter {input topology-selection; # Specify the name of the filter
configured under
# the [edit firewall] hierarchy.}}}}
# the [edit firewall] hierarchy.}}}}