This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About rking13
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About rking13
05-06-2021
7Posts
0Likes
0Solutions
May 06, 2021Last Visited
User
Activity
User
Profile
Latest posts by rking13
| Subject | Views | Posted |
|---|---|---|
| 2546 | 02-04-2014 02:46 PM | |
| 2723 | 02-04-2014 02:31 PM |
User Badges
Community Statistics
| Member Since | 06-17-2013 01:38 PM |
| Date Last Visited | 05-06-2021 01:50 PM |
| Posts | 7 |
02-04-2014
02:46 PM
Does the private IP assigned to the tunnel need to be a part of any of the protected networks? For example, 192.168.0.1/24 is a protected network currently being sent over the tunnel, so my tunnel address would be 192.168.0.2? EDIT: OK so I'm going to configure my tunnel with IP 172.16.25.1/32, add it to the crypto map for both local and remote endpoints, and that should do it? I'll have to try testing it out when no one is on
... View more
02-04-2014
02:31 PM
Operation Commit Result Failed Details IPSec tunnel #NAME enabled tunnel monitoring while binding to tunnel interface tunnel which has no IP address assigned to it yet. I receive this error when configuring a tunnel monitor to the IPSec tunnel. I'm guessing the actual tunnel interface needs an IP, what what kind of configuration is needed when that IP address is added to the tunnel? Will that IP be of local significance or do I have to add that IP to the other end of my tunnel? Thanks, Ryan
... View more
Labels:
- Labels:
-
Networking
-
Troubleshooting
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
05-06-2021
01:50 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks