Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
metturarun
New Contributor

NAT issue

Hi I have added VIP to access Local Network IP cameras to be accessed from Internet. Out IP Cameras are assigned with IPs and ports eg: 192.168.5.301:8081 192.168.5.302:8082 . . . 192.168.5.307:8087 I have done below 1) Crated VIP for each IP with exernal as 0.0.0.0 and Mapped IP as 192.168.5.301 with port 8081. 2) Created VIP Group Named " Camera" and added all VIPs 3) Created policy ( Policy ID 3 ) . 4) " Wan" is WAN1 terminal connected to internet , " internal" is the our LAN where cameras connected. Our issue :- We unable to access from Internet with our public DNS . For example http://xxxxx.xxxx.xxx:8086 But some time http://xxxxx.xxxx.xxx:8085 or http://xxxxx.xxxx.xxx:8083 is working and some time it will not. Can any you please help me on this issue ? Thanks
4 REPLIES 4
Jeff_FTNT
Staff
Staff

VIP use 0.0.0.0 as external usually used for Wan1 is in DHCP/PPPoE mode, it may got different IP from DHCP/PPPoE server. In your case, you only have one Public IP, it it only map one internal server. Try to set up one VIP only, to see what happen. If you need map more internal server, you need get more public IP.
Istvan_Takacs_FTNT

or you can also have 1 external IP with different ports to map the same public IP to different internal IPs. e.g. edit " vip-camera_8081" set extip 1.1.1.1 set extintf " WAN1" set portforward enable set mappedip 192.168.5.301 set extport 8081 set mappedport 8081 next edit " vip-camera_8082" set extip 1.1.1.1 set extintf " WAN1" set portforward enable set mappedip 192.168.5.302 set extport 8082 set mappedport 8082 next end
ede_pfau
SuperUser
SuperUser

Istvan is right but this doesn' t solve the problem. To me it looks like metturarun has done just the identical configuration. I would check if there is anything ' non-regular' with the WAN link, i.e. dual WAN, load balancing or such. I don' t think the VIP definitions are wrong. I would have configured this just the same.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
rwpatterson
Valued Contributor III

Check the service. Source ports should be 1-65535, not the destination port (8086, for example).

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Bob - self proclaimed posting junkie!See my Fortigate related scripts at: http://fortigate.camerabob.com
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors