Skip to main content
Maikel
New Member
May 17, 2018
Question

Switch back to Interface policys instead of Zone based

  • May 17, 2018
  • 6 replies
  • 7354 views

Hi all,

 

Due to too many issues (Fortinet was not able to solve) with FSSO we where not able to upgrade our Fortimanager (it was not accepting our FSSO configuration). Long story short we quit using Fortimanager and started to manage our Clusters individual, but due to the use of FM we have Zones configured. I want to quit using these Zones to and use the Fysical and VLAN interfaces as Zones only make my config more complex and badly readable. Having said this, my 92D clusters are located abroad (in the US and in Asia) and all my VPN routers are behind my Fortigates.

Is there a way to remove the Zones without affecting the Policy and thus loosing (VPN) connectivity on my 92D clusters ? Any thoughts opinions and or experiences are more than welcome.

 

 

 

6 replies

Toshi_Esumi
SuperUser
SuperUser
May 17, 2018

You're current zones likely include the interface to reach the vpn router. What I would consider as options in situation like yours are:

a) allow direct admin access to the 92D on the outside interface temporarily only from your source address. So that you don't have to rely on a VPN while you're reconstructing policies.

b) terminate a new vpn at 92D and set a new set of policies without using existing zones.

 

emnoc
New Member
May 17, 2018

You should be able to  remove the interface(s) from the zone and then apply the policies to the   interfaces, going from  interface-policy to zone does REQUIRE you  to unbind   exiting firewall.policy, but undoing it is much friendly

 

NOTE: ( maybe Ede will chime in ), you can't have a zone with no  interface iirc , so if you want to unbind the  zone-policy, craft some dummmy  loopback-interfacs  using ipv4 address from  the   test NET01/NET02 and install them in the zone;

 

 

 

e.g

 

config sys int

     edit dummy1

                 set subnet 192.0.2.1/32

                 set type loop

                 set vdom  root

     next

     edit dummy2

                 set subnet 192.0.2.2/32

                 set type loop

                 set vdom  root

     next

end

 

config sys zone

 

    edit external

       set interface dummy1

    next

   edit   trust

       set interface dummy2

   end

 

 

Do this for EACH zone,  This will allow you  to  keep the zone up while you move things in and out and around  YMMV ;)

 

 

localhost
Visitor III
May 17, 2018

You might also consider to just modify the config file manually (search zone name/replace with interface name) and reupload it.

 

Just make sure, you allow external access to do a rollback if things go sideways.

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.