From: Turritopsis Dohrnii Teo En Ming <ceo@teo-en-ming-corp.com>
To: lartc@vger.kernel.org
Subject: My attempt in configuring Application Control Traffic Shaping for Zoom Meetings in Fortigate 201F Fi
Date: Fri, 18 Jun 2021 16:43:57 +0000 [thread overview]
Message-ID: <6b01bf7c5d666fb08822f08296ac7990@teo-en-ming-corp.com> (raw)
Subject: My attempt in configuring Application Control Traffic Shaping
for Zoom Meetings in Fortigate 201F Firewall
Good day from Singapore,
Today 18 June 2021 Friday, our client wanted to prioritise the network
traffic for Zoom meetings. I proceeded to configure application control
traffic shaping for Zoom meetings in their Fortigate 201F firewall.
Firstly, login to Fortigate 201F firewall.
Turn on Traffic Shaping
===========
Go to System > Feature Visibility. Turn on Traffic Shaping.
Create New Traffic Shaper
============
Go to Policy & Objects > Traffic Shapers
Click "Create New"
Type: Shared
Name: Zoom Meeting
Under section "Quality of Service":
Traffic priority: High
Bandwidth unit: Mbps
Maximum bandwidth: 300 Mbps
Guaranteed bandwidth: 280 Mbps
DSCP: off
Click OK.
Please note that all the default traffic shapers are shared shapers.
Create New Traffic Shaping Policy
================
Go to Policy & Objects > Traffic Shaping Policy
Click "Create New"
Name: Zoom Meeting
Status: Enabled
Comments: leave empty
Under section "If Traffic Matches":
Source: all
Destination: all
Schedule: off
Service: ALL
Application:
Zoom
Zoom_File.Download
Zoom_File.Upload
Zoom_Login
Zoom_Meeting
URL Category: Leave empty
Under section "Then":
Action: Apply Shaper
Outgoing interface: SD-WAN
Shared shaper: Zoom Meeting
Reverse shaper: Zoom Meeting
Per-IP shaper: off
Click OK.
Create/Edit Internet Access Policy
=================
Go to Policy & Objects > IPv4 Policy
Click "Create New"
Name: Internet access
Incoming interface: lan
Outgoing interface: SD-WAN
Source: lan network
Destination: all
Schedule: always
Service: ALL
Action: ACCEPT
Inspection Mode: Flow-based
Under section "Firewall / Network Options":
NAT: Enabled
IP Pool Configuration: Use Outgoing Interface Address
Preserve Source Port: off
Protocol Options: PRX, default
Under section "Security Profiles":
AntiVirus: off
Web Filter: off
DNS Filter: off
Application Control: ON (APP, default profile)
SSL Inspection: SSL, certificate-inspection
Click OK.
==END=
Mr. Turritopsis Dohrnii Teo En Ming, 43 years old as of 19 June 2021, is
a TARGETED INDIVIDUAL living in Singapore. He is an IT Consultant with a
System Integrator (SI)/computer firm in Singapore. He is an IT
enthusiast.
--
-----BEGIN EMAIL SIGNATURE-----
The Gospel for all Targeted Individuals (TIs):
[The New York Times] Microwave Weapons Are Prime Suspect in Ills of
U.S. Embassy Workers
Link:
https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html
********************************************************************************************
Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's
Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts
at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan
(5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020):
[1] https://tdtemcerts.wordpress.com/
[2] https://tdtemcerts.blogspot.sg/
[3] https://www.scribd.com/user/270125049/Teo-En-Ming
-----END EMAIL SIGNATURE-----
reply other threads:[~2021-06-18 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b01bf7c5d666fb08822f08296ac7990@teo-en-ming-corp.com \
--to=ceo@teo-en-ming-corp.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).