Yes, I read your mails :) But I had the impression that it was advertised to support ingress rewrite in 14.2 (R3), and not egress... In fact, while it's useable directly on ingress interface only, as firewall filter action it's available both for ingress and egress.
There's mainly a Junidoc mismatch, finally... In 14.2: "Beginning with Junos OS Release 14.2R3, there is a packet marking scheme, called policy map, that allows the definition of rewrite rules on a per-customer basis." And only documented as a KB article (KB30973). In 15.1: -nothing- In 16.1: "An alternative packet marking scheme, available starting in Junos OS 16.1, called policy map, enables you to define rewrite rules on a per-customer basis." And documented in the normal JunOS doc. Olivier > Le 2 juil. 2016 à 12:10, Mark Tinka <[email protected]> a écrit : > > This feature (Policy Map) is not introduced in 16.1. It was introduce in 14.2. > I know because I requested this feature and was personally responsible for > working with them to introduce it. > We use it, and it works perfectly. We are on 14.2R6.5. I highly recommend it; > far better than Juniper's old-style rewriting on egress. > > > On 1/Jul/16 18:02, Olivier Benghozi wrote: >> I know this thread is more than one year old, but I had a not_that_far need >> (outbound packet 802.1p field rewrite based on DSCP, instead of internal >> CoS)... >> Well, I've just seen that the needed feature is only available in (freshly >> released) (completely radioactive) 16.1 release. >> https://www.juniper.net/documentation/en_US/junos16.1/topics/concept/policy-maps-overview-cos.html >> >> <https://www.juniper.net/documentation/en_US/junos16.1/topics/concept/policy-maps-overview-cos.html> >> >> Not exactly similar to the byDCSPclassifying, though. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
