Understanding the ToS Value of a Tunnel Packet
To ensure that the tunneled packet continues to have the same CoS treatment even in the physical interface, you must preserve the type-of-service (ToS) value from the inner IP header to the outer IP header.
For transit traffic, Junos OS preserves the CoS value of the tunnel packet for both GRE and IP-IP tunnel interfaces. The inner IPv4 or IPv6 ToS bits are copied to the outer IPv4 ToS header for both types of tunnel interfaces.
For Routing Engine traffic, however, the router handles GRE tunnel interface traffic differently from IP-IP tunnel interface traffic. Unlike for IP-IP tunnels, the IPv4 ToS bits are not copied to the outer IPv4 header by default. You have a configuration option to copy the ToS value from the packet's inner IPv4 header to the outer IPv4 header.
To copy the inner ToS bits to the outer IP header (which is
required for some tunneled routing protocols) on packets sent by the
Routing Engine, include the copy-tos-to-outer-ip-header statement at the logical unit hierarchy level of a GRE interface.
For IPv6 traffic, the inner ToS value is not copied to
the outer IPv4 header for both GRE and IP-IP tunnel interfaces even
if the copy-tos-to-outer-ip-header statement is specified.
This example copies the inner ToS bits to the outer IP header on a GRE tunnel:
[edit interfaces]
gr-0/0/0 {
unit 0 {
copy-tos-to-outer-ip-header;
family inet;
}
}