I'm trying to test out reconfigure support on CNR 7.0.1 on a linux build. I'm able to use webGUI to send a v6 reconfigure message to my client and it responds properly however in order to test this feature I need to change DHCP server policy information and this requires a DHCP reload. Once reload occurs my client's DHCP reconfigure key changes and my client will no longer respond to reconfigure message. I get this output in the NRCMD cli prompt when I manually request a reconfigure.
nrcmd> lease6 2001:50:101::C159 reconfigure 320 AX_DHCP_NO_RECONFIGURE_KEY - The 2001:50:101::c159 client has not negotiated a reconfigure key with the server
Is it possible to configure this key to be persistant value or to change policy information such as a time server IP without a DHCP reload killing my old session key? Any help would be appreciated, thanks.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...