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 Freaky
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About Freaky
06-16-2021
3Posts
0Likes
0Solutions
Jun 16, 2021Last Visited
User
Activity
User
Profile
Latest posts by Freaky
| Subject | Views | Posted |
|---|---|---|
| 1231 | 06-16-2021 02:39 AM | |
| 1233 | 06-16-2021 02:38 AM | |
| 1280 | 06-15-2021 11:49 PM |
User Badges
Community Statistics
| Member Since | 06-15-2021 11:36 PM |
| Date Last Visited | 06-16-2021 12:06 AM |
| Posts | 3 |
06-16-2021
02:39 AM
We reported this to our PA supplier by the way, don't have access to support myself. Might take a while to propagate upstream.
... View more
06-16-2021
02:38 AM
Hi, couldn't find it in the known issues nor in the fixed issues for 9.1.10. As mentioned in the title it concerns 9.1.9 🙂 Thanks for the re'!
... View more
06-15-2021
11:49 PM
Hi, we're running into an issue with IPv6 NPTv6 which we use to route traffic through IPS on PA. The address isn't translated as expected. We tried NPTv6 in 2 configurations, both translate the same. We either used: xxxx:xxxx:xxxx:ffe0::/60 -> xxxx:xxxx:xxxx:fff0::/60 or xxxx:xxxx:xxxx:ffe3::/64 -> xxxx:xxxx:xxxx:fff3::/64 In both cases we sent traffic towards xxxx:xxxx:xxxx:ffe3:83:0:1:0 and it was translated by NPTv6 to xxxx:xxxx:xxxx:fff3:73:0:1:0. Any ideas? Seems like a nasty bug. Tried with 2 completely different source IPv6 addresses by the way, both translated the same with the 5th hextet being 0x10 lower than the original.
... View more
- Tags:
- NPTv6
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
06-16-2021
12:06 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks