github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 18:18:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: remove filters section from may update (#4944)

Browse Source 
This got merged inadvertently and should be removed
This commit is contained in:
Jamil
2024-05-09 19:36:18 -07:00
committed by GitHub
parent 1876850615
commit 65acd36ecf
1 changed files with 0 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
website/src/app/blog/may-2024-update/readme.mdx
View File

@@ -45,14 +45,6 @@ Restrictions are enforced at the **Gateway** level. If a user tries to access a
service on the host not allowed by the restriction, the Gateway will simply drop
the traffic, preventing it from ever reaching the service in question.
One popular use case for traffic restrictions is segmenting access to individual
services on a host. To do this, simply create a Resource for each service on the
host you want to allow access to, and add the appropriate traffic restrictions
to each one. Create an Resource with the `TCP/22` restriction to allow SSH
access for your DevOps team, then add another Resource with the `TCP/443`
restriction to allow access to an HTTPS service for the rest of your
organization.
Traffic restrictions are supported on all Resource types, including DNS, IP, and
CIDR-based Resources, and can be enabled on the Team and Enterprise plans.