REally appreciate your effort in helping Collin!
But that is for the firewall rules not for the port forwarding...
Okay i got it setup like this.
I got what Fortigate calls a Virtual IP okay?
Now with this virtual ip i map a public ip address with a internal ip addresss
Addicional i can port forward so, so for example i have have an ip address let say 190.2.5.6 and have different services to different internal servers using it for example
190.2.5.6 mapped to 192.168.1.5 on port 80
190.2.4.6 mapped to 192.168.1.6 on port 10443
Now for the Remote AP i got this
190.2.4.6 mapped to 192.168.1.20(wireless controller ip udp 4500
190.2.4.6 mapped to 192.168.1.20 udp 69
For VIA
190.2.4.6 mapped to 192.168.1.20 tcp 443
190.2.4.6 mapped to 192.168.1.20 tcp 1701
190.2.4.6 mapped to 192.168.1.20 tcp 1723
190.2.4.6 mapped to 192.168.1.20 udp 500
Now thats what i got there...
When you creating a port forward there is no option of IP you just can select TCP or UDP protocols nothing else...
About the custom ports thats for the firewall rule not for the virtual IP which map one external IP with an internal ip
in the Firewall Rule i got a virtual ip like this
PORT WAN!
ALL
PORT INTERNAL
Virtual IP GROUP
PORTS Allowed
ANY
For now i got the ports as ANY becasue im testing...
So in the firewall rule im allowing all the ports... if i were blocking ports yes i can create the ip protocol with the custom port for the firewall rule but thats just for the firewall rule not for the virtual ip which port forwards.
You got what i mean?
When i testted i had udp 1701 im hoping thats the mistake... which i just changed to tcp 1701... and as you said it wont work if i dont have the L2tp ports forwarded... and i didnt because i had udp 1701 udp instead of tcp 1701 which is the port i need!
The sad thing is that its sunday and i dont own an ipad :P so icant test! :(