H Series Firewalls: Routing Configuration in Nebula vs. Local GUI

Zyxel_Claudia

As cloud-based management becomes increasingly popular, Zyxel continues to align its local and Nebula experiences for the H Series firewalls. However, there are still a few differences when configuring routing policies.

Policy Route: Trunk Configuration Difference

What Is a Policy Route?

Policy routing lets administrators direct specific traffic (by source, destination, application, etc.) to specific WAN interfaces or gateways.

In Local GUI:

In the local GUI, administrators can set the next-hop of a policy route to a trunk interface. This is useful when WAN failover or load balancing via trunk groups is needed.

In Nebula:

The Nebula Control Center currently does not support trunk as a next-hop option in policy routing. If the local configuration is synced to Nebula:

• The trunk-based next-hop is visible, but not editable in NCC.
• Admins must change the next-hop to a standard interface or IP in Nebula if they need to modify the route.

Static Route Configuration

Static route configuration is consistent between local and Nebula platforms.

Summary:

While most routing features are well-aligned between Nebula and local GUI, policy route trunk support remains a local-only feature for now. Zyxel may include this in future updates.