This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
The is not much Netgear specific involved. On a trunk, one VLAN can be operated untagged (the PVID setting does define the VLAN where incoming untagged frames ar assigned to - this is the only Ntgr specific thing), all the other VLAN on a trunk must travel tagged.
The same applies to your security applianc for example, too.
To make the trunk work, both ends must be configured the very same way - this is standard.
All I can see is that the Fortigate des know about the WIRED VLAN, and the Netgear switch has just (0ne!) port participating on that same VLAN.
No indication on how the Fortigate and the Netgear switch should handle the supposedly tagged VLANon the trunk making up the connection for both VLANs, while the basic VLAN does most likely run untagged (that's ok), an the added VLAN isn't configured on what IP s supposed to make up the trunk.
@schumaku Thanks for the reply. I have very limited knowledge on Netgear and how they handle VLANs. I made the assumption that if port 8 (uplink) knew about all of the VLANs (VLAN Membership) that I was advertising from the FGT then I could simply set the PVID to 112 on port 3 (laptop connected) and the computer would associate with that VLAN.
I have played around with specifically tagging (VLAN Tag field) that port to 112 and nothing I am doing will have that computer associate with VLAN 112.
The is not much Netgear specific involved. On a trunk, one VLAN can be operated untagged (the PVID setting does define the VLAN where incoming untagged frames ar assigned to - this is the only Ntgr specific thing), all the other VLAN on a trunk must travel tagged.
The same applies to your security applianc for example, too.
To make the trunk work, both ends must be configured the very same way - this is standard.
