I had serious challenges with getting the client to accept a ipv6 address. Fortinet TAC was called in for support and struggle with assisting me. So far , we are isolating if the problem is; " the fortigate or the forticlient ".
Here's the vpn ssl configs;
And here's the static routes and address6 details;
Now originally when connecting, I was only getting a ipv4 address. The FWF60D was NOT reflecting this in the diag show commands btw;
So in our webUI, the ssl monitor showed the following;
So at this point it was confusing as to what/why the client was not seeing any ipv6 assignments. Fortinet KB was also not of any help. So TAC was called in.
The logs didn't give any clue as to any errors or issues;
Stay tuned, we see what TAC proposes and so far I was not impressed with the TAC. They where trying to proposed that I can't assign a ipv4 and ipv6 address at the same. The fortigate actually kicks a error if you remove the ipv4-pool and enable a ipv6-pool-only.
I will keep you posted on any developments on this front.
Freelance Network / Security Engineer
kfelix ----a---t---socpuppets ---d---o---t---com
=( @ @ )=