Thursday, 29 December 2016
Thursday, 4 February 2016
How-to: Use the grep command on a FortiGate
Grep is a fast and easy way of filtering lots of information from the console. The FortiGate allows you to pipe grep to many commands including show, get and diagnose.
To use grep you must pipe it with the search value after a command ex: | grep <value>
There are a few options available with grep that can be seen with the -h flag. Below is a show command that's been piped with grep to display all the options available:
gate1 # show | grep -h
Usage: grep [-invfcABC] PATTERN
Options:
-i Ignore case distinctions
-n Print line number with output lines
-v Select non-matching lines
-f Print fortinet config context
-c Only print count of matching lines
-A Print NUM lines of trailing context
-B Print NUM lines of leading context
-C Print NUM lines of output context
To use grep you must pipe it with the search value after a command ex: | grep <value>
There are a few options available with grep that can be seen with the -h flag. Below is a show command that's been piped with grep to display all the options available:
gate1 # show | grep -h
Usage: grep [-invfcABC] PATTERN
Options:
-i Ignore case distinctions
-n Print line number with output lines
-v Select non-matching lines
-f Print fortinet config context
-c Only print count of matching lines
-A Print NUM lines of trailing context
-B Print NUM lines of leading context
-C Print NUM lines of output context
Tuesday, 19 January 2016
How-to: Configure Collector mode on a FortiAnalyzer
The FortiAnalyzer allows you to aggregate logs from multiple FortiGate firewalls giving you a central console to view logs, alerts and run reports for all the FortiGates in your organisation.
Each FortiAnalyzer can only handle a certain number of logs per second, be it the hardware or VM models. If you have dozens, hundreds or even thousands of FortiGates it would not be feasible to have all these devices send their logs to one FortiAnalyzer. Good news is that FortiAnalyzers can be configured in a 'collector' mode and deployed regionally to take the burden from your Analyzer that is doing the reporting.
One advantage of this is that FortiAnalyzer VMs that have been configured as a collector have no GB per day limitation as their standard config does. This means you'll only need a FortiAnalyzer VM BASE license for each of the remote regions.
In this example I'll configure two FortiGates and FortiAnalyzers that have been configured in collector modes. This will simulate two regions for my organisation and the firewalls within each region. The collectors will then forward their logs to the global Analyzer from where I can run reports for the entire organisation.
The FortiGates are running 5.4.0 and the FortiAnalyzers 5.2.5.
Each FortiAnalyzer can only handle a certain number of logs per second, be it the hardware or VM models. If you have dozens, hundreds or even thousands of FortiGates it would not be feasible to have all these devices send their logs to one FortiAnalyzer. Good news is that FortiAnalyzers can be configured in a 'collector' mode and deployed regionally to take the burden from your Analyzer that is doing the reporting.
One advantage of this is that FortiAnalyzer VMs that have been configured as a collector have no GB per day limitation as their standard config does. This means you'll only need a FortiAnalyzer VM BASE license for each of the remote regions.
In this example I'll configure two FortiGates and FortiAnalyzers that have been configured in collector modes. This will simulate two regions for my organisation and the firewalls within each region. The collectors will then forward their logs to the global Analyzer from where I can run reports for the entire organisation.
The FortiGates are running 5.4.0 and the FortiAnalyzers 5.2.5.
Thursday, 15 October 2015
Q&A: Can you stack FortiCloud licenses to increase the duration?
Yes you can. If you add multiple FortiCloud 1 year licenses to a FortiGate, it will increase the amount of years.
It won't increase the storage space however.
It won't increase the storage space however.
Tuesday, 22 September 2015
FortiMail quarantine URL points to the wrong address
Today I was testing out the quarantine feature on the FortiMail and noticed something strange with the release link. The domain name that the link forwarded me to was doubling the hostname of the FortiMail.
For example, below is the quarantine email I received. I click on the 'Release' link to try and release the email:
Unfortunately the quarantine page doesn't load. Looking at the URL I can see that it's pointing to mail.mail.ingramlabs.com.au instead of mail.ingramlabs.com.au. The 'mail' hostname here has doubled up for some reason.
For example, below is the quarantine email I received. I click on the 'Release' link to try and release the email:
Unfortunately the quarantine page doesn't load. Looking at the URL I can see that it's pointing to mail.mail.ingramlabs.com.au instead of mail.ingramlabs.com.au. The 'mail' hostname here has doubled up for some reason.
Labels:
fortimail,
fqdn,
quarantine,
troubleshooting,
webgui
Monday, 7 September 2015
How-to: Configure a FortiAuthenticator to be used for admin RADIUS authentication, Single Sign On and as a Certificate Authority
In the post I'm going to go through the steps on how-to configure a FortiAuthenticator (FAUTH) from scratch so that it can serve as a RADIUS server for admin logins on a FortiGate (FGT), as the Single Sign On (SSO) service for a FortiGate and lastly as a Certificate Authority that will create a cert for a FortiGates admin GUI and to be used in the SSL proxy for deep packet inspection.
It's quite a long one so grab a coffee and get ready!
It's quite a long one so grab a coffee and get ready!
Labels:
CA,
certificates,
fortiauthenticator,
fortigate,
FortiOS 5.2,
fsso,
how-to,
webgui
Tuesday, 1 September 2015
How-to: Configure a workflow in FortiManager to enforce change management policies
The FortiManager allows you to enforce change management policies so that while junior members are able to make configuration changes, they will not be applied until management approves them.
This blog will go through the steps on how-to set this up.
This blog will go through the steps on how-to set this up.
Labels:
adom,
cli,
fortigate,
fortimanager,
FortiOS 5.2,
how-to,
policy,
webgui
Friday, 28 August 2015
How-to: Configure a pre-login warning message on a FortiGate
By default when you login to a FortiGate there is no warning message. This blog will go through howto enable the banner and edit the default message to help scare away those baddies.
Friday, 21 August 2015
How-to: Automate user browsing from a text file containing URLs
In this blog I'll go through how I configure my lab environment so that computer/users will automatically connect to web servers via a text document on a schedule. The reason I set this up is to simulate constant 'real world' browsing from computers in the lab so that my web filtering reports are filled up when it comes time to demo to customers!
Labels:
fortianalyzer,
fortigate,
how-to,
script,
web filter,
wget,
windows
Wednesday, 25 February 2015
How-to: Create a YouTube report for the FortiAnalyzer
One of the new features of FortiOS 5.2 was the introduction of Cloud Application logging which allows you to track web application traffic like Youtube videos, email address logins and files uploaded/downloaded via Dropbox.
This quick how-to guide goes through creating a small chart that will only show us the YouTube videos that have been watched and the users that watched them.
This config is done a FortiAnalyzer running 5.2.2.
This quick how-to guide goes through creating a small chart that will only show us the YouTube videos that have been watched and the users that watched them.
This config is done a FortiAnalyzer running 5.2.2.
Labels:
5.2,
application control,
fortianalyzer,
fortigate,
FortiOS 5.2,
how-to,
reporting,
youtube
Subscribe to:
Posts (Atom)