Skip to main content
debasis_parida
debasis_parida
New Member
January 29, 2016
Solved

Using DMZ as 3rd WAN on Fortigate 60D

  • January 29, 2016
  • 1 reply
  • 10418 views

Hello,

 

I am pretty new to Fortigate products, so sorry in advance for any confusion in my post.

 

I am using a fortigate 60D in dual WAN and using it as NAT mode. We have three ISPs at work, and want to use two ISPs at the same time to do traffic load balance (currently static routes are used for particular traffics), and want to use the third ISP as a backup for automatic failover.

 

Is there any way how I can use the DMZ port as WAN3 to achieve above?

    Best answer by ede_pfau

    hi,

     

    and welcome to the forums.

     

    I will assume you are using FortiOS v5.0 or v5.2. In v5.2, you would configure the 2 existing WAN ports as one "WAN load balancing" port. In order to include the 3rd WAN port (you can use ANY free port - "DMZ" is just a label) you would create 2 default routes with equal distances but (!) different priorities. This way, both routes will show up in the Routing Monitor but only the one with smaller priority will be actually used. (In FortiOS, translate "priority" with "cost"). So if the WLLB port is down it's route will be deleted from the Routing Table and the 3rd WAN will take over.

     

    Have a look at the Cookbook, and eventually the Handbook (both on docs.fortinet.com) to see how that is done in detail. For any questions you've got the forum now.

    1 reply

    ede_pfau
    SuperUser
    ede_pfauAnswer
    SuperUser
    January 29, 2016

    hi,

     

    and welcome to the forums.

     

    I will assume you are using FortiOS v5.0 or v5.2. In v5.2, you would configure the 2 existing WAN ports as one "WAN load balancing" port. In order to include the 3rd WAN port (you can use ANY free port - "DMZ" is just a label) you would create 2 default routes with equal distances but (!) different priorities. This way, both routes will show up in the Routing Monitor but only the one with smaller priority will be actually used. (In FortiOS, translate "priority" with "cost"). So if the WLLB port is down it's route will be deleted from the Routing Table and the 3rd WAN will take over.

     

    Have a look at the Cookbook, and eventually the Handbook (both on docs.fortinet.com) to see how that is done in detail. For any questions you've got the forum now.

    debasis_parida
    debasis_paridaAuthor
    New Member
    February 8, 2016

    Hello @ede_pfau, Thank you very much for the explanation. I am extremely sorry for the delay in reply, as I had to wait for a weekend to carry out the testing.

     

    Setting up priorities in static routes do work, but still I can't use third ISP in DMZ port. The current setup is, ISP1 on WAN1, and ISP2 on WAN2. Default routes are set for both the ISPs, and we are using static routes to specific packets to be sent across ISP2 on WAN2.

     

    I have setup the DMZ interface with ISP3 WAN IP and subnet, and set a default route using ISP3's gateway. But when tried to route a packet through ISP3 (tried both static routing and policy routing), it doesn't work.

    Current firmware version is - 5.2.4,build688

     

    Any suggestions?

     

    Thanks!

     

     

    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    February 8, 2016

    Well, if you set it up like I've posted then WAN3 will only be active if the other WAN trunk fails. You may have several default routes in the Routing Table but only one is used at any time.

     

    Policy routing though should work. I bet if you look at WAN3 with the sniffer (CLI: diag deb enable; diag sniffer packet <wan3 port name> '' 4) you'll see outgoing traffic but no replies. Could be that the return traffic comes in on the other port which would make the FGT discard it (asymmetric routing).

    Terms & ConditionsAccessibility statement