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

Technical Documentation
 
CLI Explorer New
 
Content Explorer New
 
Documentation Help New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
Glossary
 
Portable Libraries
 
Home > Support > Technical Documentation > Understanding OSPFv3 Authentication
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

  • J Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • M Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • SRX Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • T Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
 

Understanding OSPFv3 Authentication

OSPFv3 does not have a built-in authentication method and relies on IPsec to provide this functionality. OSPFv3 uses the IP authentication header (AH) and the IP Encapsulating Security Payload (ESP) portions of the IPsec Protocol to authenticate routing information. You can secure specific OSPFv3 interfaces and protect OSPFv3 virtual links.

Use ESP with NULL encryption to provide authentication to the OSPFv3 protocol headers only. Use AH to provide authentication to the OSPFv3 protocol headers, portions of the IPv6 header, and portions of the extension headers. Use ESP with non-NULL encryption for full confidentiality. You configure the actual IPsec authentication separately.

The following restrictions apply to IPsec authentication for OSPFv3:

  • Dynamic IKE SAs are not supported.
  • Only IPsec transport mode is supported. Tunnel mode is not supported.
  • Because only bidirectional manual SAs are supported, all OSPFv3 peers must be configured with the same IPsec SA. You configure a manual bidirectional SA at the [edit security ipsec] hierarchy level.
  • You must configure the same IPsec SA for all virtual links with the same remote endpoint address.
 

Related Documentation

  • J Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • M Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • SRX Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
  • T Series
  • Example: Configuring IPsec Authentication for an OSPF Interface
 

Published: 2011-10-25

 
  • 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-2013 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out