Feature Request - Network Topology on Trusted, Optional and Custom Interfaces

Claus

Hello,

I recently ran into an issue where there is only a small transfer network (/29) on the trusted interface. There is routes in place which route several networks to a MPLS router within this transfer network.

However, as far as I know, the "Trusted" built-in Alias only covers IPs (primary and secondary) directly configured on that interface.
Therefor I cannot use this "Trusted" Alias in any rule as it would not allow other networks behind the MPLS router.

Would it be possible to introduce a "Topology" Feature, where it is possible to define other networks/hosts which are available on a Trusted, Optional, Custom interface?

With this in place the Firebox is aware of other networks on its (in this case "Trusted") Interface.

Kind regards
Claus

james.carson

Hi @Claus

Trusted and Optional are just aliases for networks the firewall owns (divided into two zones years ago because someone asked for that functionality.)

You can make your own aliases with any subnets or networks you'd like:
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/policies/aliases_about_c.html