Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > Releasing IPv4 Addresses During Termination of PPP Sessions
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • IPCP Renegotiation of IPv4 Addresses for Dual-Stack Subscribers
  • Overview of Processing IPCP Negotiations for Dual-Stack Subscribers
  • AAA Access Messages During IPCP Negotiations for Dual-Stack Subscribers
  • AAA Accounting Messages During IPCP Negotiations for Dual-Stack Subscribers
 

Releasing IPv4 Addresses During Termination of PPP Sessions

When a request for termination of the IPCP negotiation is received from the CPE, the B-RAS application running on the router acknowledges this terminate-request for closing the IPv4 session by sending a terminate-acknowledgment packet. If the IPCP termination is successful, the IPv4 address that the RADIUS server allocated to the client is released. The RADIUS client, which is the router, sends an immediate accounting message that contains the Ipv4-release-control RADIUS VSA attribute [26-164] to the RADIUS server. In this immediate accounting message, the Framed-Ip-Address RADIUS IETF attribute [8] is not included. This Acct-Update message is sent immediately on release of the IPv4 address to the RADIUS server and the configured interval for Interim-Acct messages is not considered in such a case. The Ascend-Data-Filter attribute [242] is modified to delete the Framed-IP-Address attribute for the released IPv4 address.

After the immediate accounting message is sent, the Interim-Acct message is sent to the RADIUS server at the configured interval. The Interim-Acct message contains all the supported RADIUS attributes except the Framed-Ip-Address attribute. Because the IPv6 addresses are not released in this scenario, the Interim-Acct message contains the IPv6 prefixes.

 

Related Documentation

  • IPCP Renegotiation of IPv4 Addresses for Dual-Stack Subscribers
  • Overview of Processing IPCP Negotiations for Dual-Stack Subscribers
  • AAA Access Messages During IPCP Negotiations for Dual-Stack Subscribers
  • AAA Accounting Messages During IPCP Negotiations for Dual-Stack Subscribers
 

Published: 2012-06-26

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out