Managed FortiSwitch Renaming

Managed FortiSwitch Renaming

When upgrading the firewall or replacing a FortiSwitch, it’s important to note that the switch names are lost. This means it is only possible to see the FortiSwitch serial number in the ‘Name’ field in the GUI, highlighting the significant impact of the upgrade on the switch names.

To rename the managed FortiSwitch in v7.4 from GUI, it is required to de-authorize the FortiSwitch and then rename it. This will cause the FortiSwitch to go offline, so this must be done during a maintenance window to avoid any outages during production time.

Read more

Making the Invisible Visible: Troubleshooting Bridged WiFi Clients Missing in FortiAnalyzer

Suppose the settings listed below are not configured on FortiGate. FortiAnalyzer Reports and FortiView will not generate SSID usage statistics for clients in bridge mode. The default settings for these log objects are set to ’notifications.’ To ensure that reports are generated properly, you need to change the setting to ‘information’ using the following command:

FortiGate

config wireless-controller log
    set sta-event-log information  
    set sta-locate-log information
    set wtp-event-log information
end

After configuring these settings, you can check the logs on FortiGate to monitor this capability. This step is essential for sending logs related to bridge mode SSIDs to FortiAnalyzer, allowing you to analyze SSID usage in bridge mode. To access the logs, navigate to Log View -> Logs -> Fortinet Logs - FortiGate -> Events -> WiFi Events and set the filter to Action == sta-wl-bridge-traffic-stats.

Read more

echo ‘secret’ | base64 vs echo -n ‘secret’ | base64

echo “secret” | base64 vs echo -n “secret” | base64

echo "secret" | base64

Is not the same as

echo -n "secret" | base64

Without the -n switch, echo will append a newline which will also be encoded by base64.

1
2
3
4
5
zero@prod-002:~$ echo "secret" | base64
c2VjcmV0Cg==

zero@prod-002:~$ echo -n "secret" | base64
c2VjcmV0
Read more