Hi Jonathan, > Regarding the default behavior in firewall filters, there is no way > you can have an 'exact' match, since all source addresses are /32s by > definition. Therefore, the behavior of matching all addresses within > the prefix is the only reasonable behavior. > Yes it's right. > And, you can actually apply different match types to prefix lists in > routing policy now. Use the 'prefix-list-filter' configuration > statement. > > For example: > > [edit policy-options policy-statement example term example] > [EMAIL PROTECTED] set from prefix-list-filter internal-routes ? > Possible completions: > exact Exactly match the prefix length > longer Mask is greater than the prefix length > orlonger Mask is greater than or equal to the prefix length > Thanks for this tip!
Regards, Samuel _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
