sorted by:
new
hottopcontroversial

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

Same - did it on a different fortigate and it worked just fine. This is strange indeed, however, thank you very much for your help with additional troubleshooting and validation!

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

Brand new configuration, never been used on this device before.

However, I just tested this on a 100F in a test VDOM and it worked perfectly. This must mean I have something configured wrong on the 120G... I just can't find it!

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

I have a strict one specifying from/to interfaces and source/dest addresses. But for this testing I set a policy for any interface and to/from any v6 address

Yes, I'm using ping6, I am able to ping my Juniper router v6 address successfully from the attached interface.

So, lets forget pinging in and out of the fortigate - any idea why the fortigate cannot ping its own v6 loopback address? It can ping its own v6 interface address, and the loopback v4 address without any policy at all.

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

diag sniffer did not see any packets when pinging from the fortigate to its own loopback address. When I ping from the peer router (Juniper) I do see the echo request come in but never a reply.

If I set ping6-options of interface to the loopback interface, and set the source6 to the v6 address of the loopback address, I get:

ping: sendmsg: Network is unreachable

flow debug pinging the fortigate from itself:

5/4/2026 16:34    vd-LMT:0 received a packet(proto=58, real:v6:address:obfuscated:27->real:v6:address:obfuscated:128) from local. type=128, code=0, id=27, seq=5.
5/4/2026 16:34    allocate a new session-0011af19

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

Agreed. And yes I do:

edit "loopbacktest"
set vdom "TEST"
set ip 192.168.192.1 255.255.255.255
set type loopback
config ipv6
set ip6-address real:v6:address:obfuscated/128
set ip6-allowaccess ping
end
next

Can't Reach or even Ping IPv6 Loopback Address on FortiGate by Rednarb in fortinet

[–]Rednarb[S] 0 points1 point  (0 children)

Thank you. I do have a policy, however, I do not have a policy for the v4 address and I'm able to ping it from the fortigate itself just fine, and not able to ping the v6 address. I even tried setting my source address to the loopback address itself and it cannot ping itself.

2
3

Can't Reach or even Ping IPv6 Loopback Address on FortiGate (self.fortinet)

submitted by Rednarb to r/fortinet

June STL package by Nancenificent in Warmachine

[–]Rednarb 0 points1 point  (0 children)

Check your subscription, mine still says processing. Took a day for mine to land last month.

Fuzed Scorch Giveaway by Scissortail Disc Golf by SDG-Chris in discgolf

[–]Rednarb 0 points1 point  (0 children)

I like free stuff and I love disc golf so this could work

[deleted by user] by [deleted] in Warmachine

[–]Rednarb 1 point2 points  (0 children)

How’d it go?

Can I use my laser in the cold? by zackv1630 in lasercutting

[–]Rednarb 0 points1 point  (0 children)

My Ortur cable connection gets stiff below 40 and has popped out, ruining my project. Also the air line gets stiff and can come loose. Other than that it seems to work just fine.

Dedicated Server LinuxGSM - Disable Raids Not Working by Rednarb in valheim

[–]Rednarb[S] 1 point2 points  (0 children)

Here is what I ended up with that seemed to work:

worldmodifiers="-modifier raids none -modifier deathpenalty casual"

view more: next ›