Maybe one in a thousand sites will need to bind a definition to an interface. The 99.9% of the time it's not necessary, it's likely to cause mysterious problems.
I would say that you should never choose Internal, External, DMZ, etc.; always choose > unless told to change it by an Astaro Support engineer.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
Maybe one in a thousand sites will need to bind a definition to an interface. The 99.9% of the time it's not necessary, it's likely to cause mysterious problems.
I would say that you should never choose Internal, External, DMZ, etc.; always choose > unless told to change it by an Astaro Support engineer.
Cheers - Bob
So you have set any in ALL interface definition in "Definitions-->Networks"???
My question is......why Astaro add this feature if doesn't work or add some problem???
Maybe one in a thousand sites will need to bind a definition to an interface. The 99.9% of the time it's not necessary, it's likely to cause mysterious problems.
I would say that you should never choose Internal, External, DMZ, etc.; always choose > unless told to change it by an Astaro Support engineer.
Cheers - Bob
So you have set any in ALL interface definition in "Definitions-->Networks"???
My question is......why Astaro add this feature if doesn't work or add some problem???
Yes I read the Italian thread, but this is most populated and discussed.
I didn't understand why an Enterprise level firewall have this strange bug and also not documentated.
I used that feature also with previous version (7.x) without any evident problem, but now for more stability I have set all network definitions to interface any.
