Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


rewrite-rules (Interfaces)


Hierarchy Level


Associate a rewrite-rules configuration or default mapping with a specific interface.

The [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level is not supported on ACX Series routers.

Integrated Bridging and Routing (IRB) interfaces are used to tie together Layer 2 switched and Layer 3 routed domains on MX routers. MX routers support classifiers and rewrite rules on the IRB interface at the [edit class-of-service interfaces irb unit logical-unit-number] level of the hierarchy. All types of classifiers and rewrite rules are allowed, including IEEE 802.1p.


The IRB classifiers and rewrite rules are used only for routed packets; in other words, it is for traffic that originated in the Layer 2 domain and is then routed through IRB into the Layer 3 domain, or vice versa. Only IEEE classifiers and IEEE rewrite rules are allowed for pure Layer 2 interfaces within a bridge domain.

On an MX Series router and on an EX Series switch, exp-push-push-push, exp-swap-push-push, and frame-relay-de are not supported on an integrated routing and bridging (IRB) interface.

On an ACX Series router, only the outer tag is supported for dscp, inet-precedence, and ieee802.1.

For IQ PICs, you can configure only one IEEE 802.1 rewrite rule on a physical port. All logical ports (units) on that physical port should apply the same IEEE 802.1 rewrite rule.


rewrite-name—Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules] hierarchy level.

default—The default mapping.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.