[j-nsp] Re-write rule for GRE interface

[Diogo Montagner]

Hi,

You can also try to apply an output firewall filter in the gre
interface to rewrite the DSCP of the packet.

I think the option copy-tos-to-outer-ip-header will not work because
your inner packet is not an IP packet and this option only works for
inner IP packet.

If this does not work, you can apply an outbound firewall filter in
the output direction of your interfaces matching GRE packets + ipsrc +
ipdst of your tunnel and then applying the right dscp values.

Another option you can give it a try is the output-forwarding-class-map:
http://www.juniper.net/techpubs/en_US/junos9.6/information-products/topic-collections/config-guide-cos/cos-classifying-packets-by-egress-interface.html

HTH
./diogo -montagner



On Tue, Jan 18, 2011 at 4:59 AM, Dale Shaw <dale.shaw+j-nsp at gmail.com> wrote:
> Hi Shiva,
>
> On Monday, January 17, 2011, Shiva Shankar <shankarks at gmail.com> wrote:
>> Hi All, Thanks for the reply. Platform is M7i, and the junos is 9.3
>>
> [...]
>
> How are you classifying traffic into the forwarding classes in the
> first place? The rewrite-rule assumes traffic has been classified
> already. For example, for the 'ef' rewrite-rule to work, you must have
> already mapped your voice RTP traffic into the 'ef' forwarding-class.
>
> You need a Behaviour Aggregate (BA) classifier, Multi-Field (MF)
> classifier or static classifier applied on the ingress interface(s)
> under the class-of-service stanza.
>
> Cheers,
> Dale
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>