Skip to main content
Best answer by simonorch

Upgraded my lab 60E and noticed either a deliberate change in behaviour or a bug but i couldn't find it in the notes.

 

when dhcp dns settings are at default (same as system dns) and the WAN/internet connection retrieves dns servers from dhcp, the previous behaviour was for the dhcp aquired dns servers to be used in internal dhcp scopes. Now it uses the configured system dns (fortiguard by default), which could be fatal for users if you have restricted dns traffic in your policies

 

I haven't tested this on any other boxes to confirm so i could be mistaken but be aware

1 reply

bascheew
bascheew
Visitor III
October 10, 2019

I think I found a bug.

 

On AP Profiles, if SSIDs are manually assigned and you choose to view the profile, the SSID fields will be blank and if you press OK then you save the profile with no SSIDs.  If you're not paying attention you'll easily miss that you just removed any SSIDs!

 

See attached gif for how to reproduce:

simonorch
simonorchAnswer
Explorer
October 10, 2019

Upgraded my lab 60E and noticed either a deliberate change in behaviour or a bug but i couldn't find it in the notes.

 

when dhcp dns settings are at default (same as system dns) and the WAN/internet connection retrieves dns servers from dhcp, the previous behaviour was for the dhcp aquired dns servers to be used in internal dhcp scopes. Now it uses the configured system dns (fortiguard by default), which could be fatal for users if you have restricted dns traffic in your policies

 

I haven't tested this on any other boxes to confirm so i could be mistaken but be aware

Jirka1
Jirka1
Explorer II
October 10, 2019

Finally add support for wildcard FQDN addresses in firewall policy!

Terms & ConditionsAccessibility statement