Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Access and Access-Internal Routes for Subscriber Management

The DHCP and PPP applications on the router use both access routes and access-internal routes to represent either the end users or the networks behind the attached router. An access route represents a network behind an attached router, and is set to a preference of 13. An access-internal route is a /32 route that represents a directly attached end user, and is set to a preference of 12.

Access routes typically are used to apply the values of the RADIUS Framed-Route attribute [22] for IPv4 routes and the Framed-IPv6-Route attribute [99] for IPv6 routes. A framed route consists of a prefix that represents a public network behind the CPE, a next-hop gateway, and optional route attributes consisting of a combination of metric, preference, and tag. The only mandatory component of the framed route is the prefix. The next-hop gateway can be specified explicitly in the framed route. Alternatively, the absence of the gateway address implies address 0.0.0.0, which the must resolve using the CPE’s IP address. In either case, the convention is that the next-hop gateway is the CPE IP address.

You can configure a dynamic profile to use predefined variables to dynamically configure access routes using the values specified in the RADIUS attribute. To configure access routes include the access stanza at the edit dynamic-profiles profile-name routing-options] hierarchy level. To configure access-internal routes, include the access-internal stanza at the same hierarchy level.

• If the RADIUS framed route always specifies the next-hop gateway, only the access stanza is required in the dynamic profile. The access-internal stanza is not required.
• If the RADIUS framed route does not specify the next-hop gateway—as is more common—the variable representing the next-hop, $junos-framed-route-nexthop, defaults to 0.0.0.0. This value implies that the CPE IP address is to be used. For this case, the access-internal stanza is required to resolve $junos-framed-route-nexthop to the CPE IP address (represented in the access-internal stanza by $junos-subscriber-ip-address) and the logical interface (represented as a qualified next-hop by $junos-interface-name).

Best Practice: We recommend that you always include the access-internal stanza in the dynamic-profile when the access stanza is present for framed route support.