Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


no-nexthop-change (BGP multihop)



Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Statement introduced in Junos OS Release 11.3 for the QFX Series.


Specify that the BGP next-hop value not be changed. For route advertisements, specify the no-nexthop-self option.

An external confederation peer is a special case that allows unconnected third-party next hops. You do not need to configure multihop sessions explicitly in this particular case; multihop behavior is implied.

If you have external BGP confederation peer-to-loopback addresses, you still need the multihop configuration.


You cannot configure the accept-remote-nexthop statement at the same time.


If you omit this statement, all EBGP peers are assumed to be directly connected (that is, you are establishing a nonmultihop, or “regular,” BGP session), and the default time-to-live (TTL) value is 1.


no-nexthop-self— Specify this option for route advertisements.

Required Privilege Level

routing—To view this statement in the configuration.

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