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

Wan 1 Wan2 configuration Fortigate 80c

We have configured Wan 1 port on one ISP with didicated IP, The second IP from this provider is in the same subnet as first. To configure WAN2 i use the second provider, but its the modem dsl connection. 1) I configured modem wan interface and its local interface as: 196.168.20.1 2) I configured Wan2 interface on fortigate as: 196.168.20.2 3) Configured Static Rout(Gateway) to Wan2: 196.168.20.1 4) Configured internal2 interface on fortigate as: 197.168.20.2 5) Set the firewall policy Internal2 (all) to Wan2(all) The problem is when I connect a network cable from modem to Wan2 all terminal clients that get dhcp ip adresses by our dhcp server cant connect to the Web in WAN1..The terminal server uses Wan1 to connect to the web. From static Ips i can do that in Wan1. But I cant connect to Wan1 external Ip address when i use some static ip 196.168.20.10 through Wan2
6 REPLIES 6
rwpatterson
Valued Contributor III

Your best bet here would be to get into the ISP' s modem, and change the local subnet to something other than the default (192,168,111,x/24, or similar). It shouldn' t be a big deal, if you can get to the management interface.

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
stebelskiy2709

Your best bet here would be to get into the ISP' s modem, and change the local subnet to something other than the default (192,168,111,x/24, or similar). It shouldn' t be a big deal, if you can get to the management interface.
Ok, I did it, changed the local subnet on modem as 172.16.100.1 and gateway to Wan2 on Fortigate same(172.16.100.1), But I have noticed it is something wrong with DNS settings all workstations on WAN1 which has static DNS (fortigate DNS which directed straight on ISP) are working when I connect modem with Fortigate WAN2;; but these which obtain DNS from our dhcp upped on domen DNS has same ip as domen 192.168.250.212 and 213) dont work.. But when modem and wan2 is disconnected(cable is unplugged) every local interface of fortigate which going through WAN1 and every workstation which has local dns assigned by dhcp or ISP' s DNS assigned static works perfectly....?? I cant understand where is the problem???
rwpatterson

You have several issues going on here. Let' s start from the beginning. Unplug WAN2 and make sure WAN1 works 100%. Check DNS and everything. Next, add WAN2. Make sure the default route is there with the same distance. Make sure your policy(s) is in place. Now check your DNS resolution. I have seen in the past the the odd IPs go through one interface, while the even go through the other. Beat it up a bit, and make sure everything is working.

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
stebelskiy2709

The local IP of modem which connected to WAN2 fortigate is same as static rout(gateway) of WAN2.. The IP of WAN2 is in the same subnet as gateway as modem.. The internal2 port has some ip which differ from WAN2 (other subnet).. The firewall policy is: internal2 all to wan2 all.. The DNS configured on fortigate has static Ips assigned by first ISP.. I just cant underst... why when i connect modem and WAN2 I have the dns problem on wan1...
rwpatterson

Try using an outside DNS service like Google (8.8.8.8 and 8.8.4.4). Your first ISP' s DNS server won' t resolve on a second ISP' s network.

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
stebelskiy2709

Your first ISP' s DNS server won' t resolve on a second ISP' s network
OK.. I see.. The second network working fine when I connect modem to wan2 (I set a static ip, gateway on my notebook), ips are resolving by DNS of second provider, its DNS is configured on modem' s WAN interface... The problem appears with first network: the our locals DNS which configured on local servers and assigned to users by dhcp cant resolve... The local servers going throug internal1 interface(as our network).. The policy is internall1 all wan1 all
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