Routing

set class-of-service classifiers dscp WIFI-traffic forwarding-class WIFI loss-priority low code-points 101100

set class-of-service routing-instances VRF1 classifiers dscp WIFI-traffic

set firewall family inet filter WIFI-filter term 1 from dscp be

set firewall family inet filter WIFI-filter term 1 then forwarding-class WIFI

set firewall family inet filter WIFI-filter term 1 then loss-priority low

set firewall family inet filter WIFI-filter term 1 then accept

set firewall family inet filter WIFI-filter term 2 then accept

set routing-instances VRF1 forwarding-options family inet filter input WIFI-filter

thanks !!

set class-of-service code-point-aliases dscp be 101100​

set class-of-service routing-instances VRF1 classifiers dscp​

This is only relevant if VRF1 has vrf-table-label enabled (or, at least, I don't know what it does other than in that context!).
It only applies to traffic coming from an MPLS interface.
It replaces the default exp classifier that happens here otherwise (exp-default). (This also happens on junos versions that don't even normally apply exp-default to mpls enabled interfaces, I hadn't even noticed that newer versions appear to fix this, and always apply exp-default to mpls enabled interfaces).
I think this happens on the ingress PFE, so any changes here done would alter fabric priority.

set routing-instances VRF1 forwarding-options family inet filter input​

This is the equivalent of putting that filter onto each interface in the VRF in the input direction. 

It would apply to traffic from non-MPLS interfaces, and also MPLS interfaces if vrf-table-label is on for the VRF, as this adds the lsi interface to the VRF, and traffic appears to "ingress" from it. Not 100% sure on what does/doesn't work without vrf-table-label, would need to test.

Is that an answer to anything like what you were asking?


I've probably missed things.

set class-of-service classifiers dscp WIFI-traffic forwarding-class WIFI loss-priority low code-points 101100

set class-of-service routing-instances VRF1 classifiers dscp WIFI-traffic

set firewall family inet filter WIFI-filter term 1 from dscp be

set firewall family inet filter WIFI-filter term 1 then forwarding-class WIFI

set firewall family inet filter WIFI-filter term 1 then loss-priority low

set firewall family inet filter WIFI-filter term 1 then accept

set firewall family inet filter WIFI-filter term 2 then accept

set routing-instances VRF1 forwarding-options family inet filter input WIFI-filter

thanks !!

set class-of-service code-point-aliases dscp be 101100​

set class-of-service routing-instances VRF1 classifiers dscp​

This is only relevant if VRF1 has vrf-table-label enabled (or, at least, I don't know what it does other than in that context!).
It only applies to traffic coming from an MPLS interface.
It replaces the default exp classifier that happens here otherwise (exp-default). (This also happens on junos versions that don't even normally apply exp-default to mpls enabled interfaces, I hadn't even noticed that newer versions appear to fix this, and always apply exp-default to mpls enabled interfaces).
I think this happens on the ingress PFE, so any changes here done would alter fabric priority.

set routing-instances VRF1 forwarding-options family inet filter input​

This is the equivalent of putting that filter onto each interface in the VRF in the input direction. 

It would apply to traffic from non-MPLS interfaces, and also MPLS interfaces if vrf-table-label is on for the VRF, as this adds the lsi interface to the VRF, and traffic appears to "ingress" from it. Not 100% sure on what does/doesn't work without vrf-table-label, would need to test.

Is that an answer to anything like what you were asking?


I've probably missed things.

set class-of-service classifiers dscp WIFI-traffic forwarding-class WIFI loss-priority low code-points 101100

set class-of-service routing-instances VRF1 classifiers dscp WIFI-traffic

set firewall family inet filter WIFI-filter term 1 from dscp be

set firewall family inet filter WIFI-filter term 1 then forwarding-class WIFI

set firewall family inet filter WIFI-filter term 1 then loss-priority low

set firewall family inet filter WIFI-filter term 1 then accept

set firewall family inet filter WIFI-filter term 2 then accept

set routing-instances VRF1 forwarding-options family inet filter input WIFI-filter

thanks !!

set class-of-service code-point-aliases dscp be 101100​

set class-of-service routing-instances VRF1 classifiers dscp​

This is only relevant if VRF1 has vrf-table-label enabled (or, at least, I don't know what it does other than in that context!).
It only applies to traffic coming from an MPLS interface.
It replaces the default exp classifier that happens here otherwise (exp-default). (This also happens on junos versions that don't even normally apply exp-default to mpls enabled interfaces, I hadn't even noticed that newer versions appear to fix this, and always apply exp-default to mpls enabled interfaces).
I think this happens on the ingress PFE, so any changes here done would alter fabric priority.

set routing-instances VRF1 forwarding-options family inet filter input​

This is the equivalent of putting that filter onto each interface in the VRF in the input direction. 

It would apply to traffic from non-MPLS interfaces, and also MPLS interfaces if vrf-table-label is on for the VRF, as this adds the lsi interface to the VRF, and traffic appears to "ingress" from it. Not 100% sure on what does/doesn't work without vrf-table-label, would need to test.

Is that an answer to anything like what you were asking?


I've probably missed things.

set class-of-service classifiers dscp WIFI-traffic forwarding-class WIFI loss-priority low code-points 101100

set class-of-service routing-instances VRF1 classifiers dscp WIFI-traffic

set firewall family inet filter WIFI-filter term 1 from dscp be

set firewall family inet filter WIFI-filter term 1 then forwarding-class WIFI

set firewall family inet filter WIFI-filter term 1 then loss-priority low

set firewall family inet filter WIFI-filter term 1 then accept

set firewall family inet filter WIFI-filter term 2 then accept

set routing-instances VRF1 forwarding-options family inet filter input WIFI-filter

thanks !!

set class-of-service code-point-aliases dscp be 101100​

set class-of-service routing-instances VRF1 classifiers dscp​

This is only relevant if VRF1 has vrf-table-label enabled (or, at least, I don't know what it does other than in that context!).
It only applies to traffic coming from an MPLS interface.
It replaces the default exp classifier that happens here otherwise (exp-default). (This also happens on junos versions that don't even normally apply exp-default to mpls enabled interfaces, I hadn't even noticed that newer versions appear to fix this, and always apply exp-default to mpls enabled interfaces).
I think this happens on the ingress PFE, so any changes here done would alter fabric priority.

set routing-instances VRF1 forwarding-options family inet filter input​

This is the equivalent of putting that filter onto each interface in the VRF in the input direction. 

It would apply to traffic from non-MPLS interfaces, and also MPLS interfaces if vrf-table-label is on for the VRF, as this adds the lsi interface to the VRF, and traffic appears to "ingress" from it. Not 100% sure on what does/doesn't work without vrf-table-label, would need to test.

Is that an answer to anything like what you were asking?


I've probably missed things.

set class-of-service classifiers dscp WIFI-traffic forwarding-class WIFI loss-priority low code-points 101100

set class-of-service routing-instances VRF1 classifiers dscp WIFI-traffic

set firewall family inet filter WIFI-filter term 1 from dscp be

set firewall family inet filter WIFI-filter term 1 then forwarding-class WIFI

set firewall family inet filter WIFI-filter term 1 then loss-priority low

set firewall family inet filter WIFI-filter term 1 then accept

set firewall family inet filter WIFI-filter term 2 then accept

set routing-instances VRF1 forwarding-options family inet filter input WIFI-filter

thanks !!