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 Lenz
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About Lenz
10-04-2022
1Post
2Likes
0Solutions
Oct 04, 2022Last Visited
User
Activity
User
Profile
Latest posts by Lenz
| Subject | Views | Posted |
|---|---|---|
| 1581 | 01-07-2022 11:31 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 2 Likes | 01-07-2022 11:31 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 4 Likes |
User Badges
Community Statistics
| Member Since | 01-07-2022 11:28 AM |
| Date Last Visited | 10-04-2022 08:35 AM |
| Posts | 1 |
| Total Likes Received | 2 |
01-07-2022
11:31 AM
2 Kudos
Was trying to commit some shared objects and getting an interesting error:
Validation Error:
shared -> pre-rulebase -> security -> rules -> GeoBlocking_Outbound -> destination 'CE' is not an allowed keyword
shared -> pre-rulebase -> security -> rules -> GeoBlocking_Outbound -> destination CE is an invalid ipv4/v6 address
shared -> pre-rulebase -> security -> rules -> GeoBlocking_Outbound -> destination CE range separator('-') not found
shared -> pre-rulebase -> security -> rules -> GeoBlocking_Outbound -> destination 'CE' is not a valid reference
shared -> pre-rulebase -> security -> rules -> GeoBlocking_Outbound -> destination is invalid
Would have figured I'd find something online about CE being funneled under another region code, but I didn't find anything. Any one else notice this?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
10-04-2022
08:35 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks