Technical Note: Managing the 'capability-default-o...

mflamingos · 08-31-2018

DescriptionThis article describes how to process non-tagged packets on a transparent unit. When sending NON-Tagged packets from a Switch to a FortiGate unit in transparent mode, packets are dropped unless the receiving interface is a physical one.Sol...

mflamingos · 08-01-2018

DescriptionThis article describes how to manage the traffic with packets that are not tagged between a Transparent FortiGate and a FortiSwitch. When receiving traffic to and from a FortiSwitch from a Transparent FortiGate unit, it is important to be ...

mflamingos · 07-02-2018

Description This article describes the basics of TACACS+ authentication, how this can be used for authorization, and general troubleshooting logs. Scope FortiAuthenticator. Solution Provides Authentication, Accounting, and Authorization for devices a...

mflamingos · 03-30-2017

DescriptionThe "set capability-default-originate" command when enabled on a neighbor will enable/disable the advertising of the default route to the BGP neighbors. Still when deleting a neighbor that includes it the feature must be disabled first oth...

mflamingos · 02-28-2017

Description When on a 5K unit, one or more slave blades are in 'Waiting' status and are not synchronizing with master blade, the system is actively processing data within the 5K cluster: To confirm this issue, verify if any of factory slave blades ar...

User Statistics

User Activity

Technical Tip: Processing non-tagged packets on a transparent unit

Technical Tip: Packet TAGGING management between a Transparent FortiGate and a FortiSwitch

Technical Tip: FortiAuthenticator support TACACS+ for authentication and authortization