Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
hi,
have a look at Ken explanation.
http://socpuppet.blogspot.fr/2015/03/ipv6-traceroutes-that-dont-report-next.html
Still no solution.
Regards,
I spoke to FTNT about this and they claim they will look into it, but still no resolution as of yet. So the best you can do is for increasing the TTL in the traceroute probes.
PCNSE
NSE
StrongSwan
Hello,
I've just joined to check that issue is still valid.
I getting the same issue, traceroute still not work from inside.
Can someone confirm this? seems to be bug since 5+ years :(
Hi,
i can confirm that issue is valid on version 7.0.3 ;-/
Tested on my 40F
Thanks,
Still an issue on 6.4.10 and 7.0.6 in 2022. :( I thought I was going crazy and suddenly didn't know how to get time-exceeded packets to be allowed, but this just seems like a bug that's never been fixed with SIT tunnels.
Hi
I mean time I've switched to GRE tunnels, probably SIT can be fixed if ticket will be open to Fortigate and provide real scenario.
I've opened such ticket in past but without such tunnel and it's was closed by Fortigate because I was not able to proof it that is still valid.
Thanks,
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1702 | |
1092 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.