"vlanforward" field allowed in Routed/NAT Opmode - a bug?

Forum|Forum|1 year ago
March 13, 2025
1 reply
700 views

Hi!

All KBs and documentation (except very early v5.0 Handbook) documents "vlanforward" field as being functional ONLY in VDOM configured in Transparent Opmode. However, this field is allowed to be set (using CLI/GUI/FortiManager) on a vlan-type subinterface whose VDOM is configured in NAT/Routed mode.

Normally, if a field is not appropriate in a particular context, FortiOS syntax disallows it to be set. So, is ability to set "vlanforward" field in subinterface with "vdom" field set to VDOM configured in NAT/Routed mode - a bug?

Thanks!

FortiGate

Toshi_Esumi

SuperUser

This KB:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-VLAN-forward-interface-parameter/ta-p/193078
says only "meaningful". So I would interpret it as it's "meaningless"(antonym) if it's not TP mode and even if you configured it. I wouldn't call it a bug.

Toshi

AlexFerenXAuthor

New Member

> So I would interpret it as it's "meaningless"(antonym) if it's not TP mode and even if you configured it.

What function "vlanforward" field serves within NAT/Routed Opmode?

> I wouldn't call it a bug.

The whole point of enforcing syntax is to not allow to set fields that have no function within a context or are mutually exclusive with values set for other fields - this has always been the case with FortiOS CLI. Otherwise, all fields could be set - which, luckily, isn't so.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded