Firewall - Revision history

Græmer at 18:38, 3 May 2022

2022-05-03T18:38:48Z

← Older revision		Revision as of 18:38, 3 May 2022
Line 34:		Line 34:
	The term "Firewall" has grown to encompass many functionalities and has a wide array of meanings.		The term "Firewall" has grown to encompass many functionalities and has a wide array of meanings.
	The "firewall" is often use interchangeably with "router" "gateway" and "UTM" or "Unified Threat Management"		The "firewall" is often use interchangeably with "router" "gateway" and "UTM" or "Unified Threat Management"
	Even the ~~Untangle NGFW~~ is a "next-gen" "firewall." There are also host-based "firewalls" that run on the local host computer.		Even the NG Firewall is a "next-gen" "firewall." There are also host-based "firewalls" that run on the local host computer.

	The "Firewall" app itself is a traditional firewall used to block and/or flag TCP and UDP sessions passing through ~~Untangle~~ using rules. The ''Firewall'' app provides the same functionality as the traditional "firewall" - the ability to use rules to control which computers and communicate on a network.		The "Firewall" app itself is a traditional firewall used to block and/or flag TCP and UDP sessions passing through NG Firewall using rules. The ''Firewall'' app provides the same functionality as the traditional "firewall" - the ability to use rules to control which computers and communicate on a network.


Line 53:		Line 53:
	=== Rules ===		=== Rules ===

	The '''Rules''' tab allows you to specify rules to Block, Pass or Flag traffic that crosses the ~~Untangle~~.		The '''Rules''' tab allows you to specify rules to Block, Pass or Flag traffic that crosses the NG Firewall.

	The [[Rules\|Rules documentation]] describes how rules work and how they are configured. Firewall uses rules to determine to block/pass the specific session, and if the sessions is flagged. Flagging a session marks it in the logs for reviewing in the event logs or reports, but has no direct effect on the network traffic.		The [[Rules\|Rules documentation]] describes how rules work and how they are configured. Firewall uses rules to determine to block/pass the specific session, and if the sessions is flagged. Flagging a session marks it in the logs for reviewing in the event logs or reports, but has no direct effect on the network traffic.

	Typically ~~Untangle~~ is installed as a NAT/gateway device, or behind another NAT/gateway device in bridge mode. In this scenario all inbound sessions are blocked by NAT except those explicitly allowed with port forwards. Because of this, the Firewall '''does not block anything by default'''. It is up to you to decide to best fit for your network, whether you only want to block specific ports or you want to block everything and allow only a few services.		Typically NG Firewall is installed as a NAT/gateway device, or behind another NAT/gateway device in bridge mode. In this scenario all inbound sessions are blocked by NAT except those explicitly allowed with port forwards. Because of this, the Firewall '''does not block anything by default'''. It is up to you to decide to best fit for your network, whether you only want to block specific ports or you want to block everything and allow only a few services.

Dmorris at 19:40, 15 January 2019

2019-01-15T19:40:26Z

← Older revision		Revision as of 19:40, 15 January 2019
Line 32:		Line 32:
	Firewall provides traditional [http://en.wikipedia.org/wiki/Firewall firewall] functionality, blocking and/or flagging traffic based on rules.		Firewall provides traditional [http://en.wikipedia.org/wiki/Firewall firewall] functionality, blocking and/or flagging traffic based on rules.

	The term "Firewall" has grown to encompass many functionalities and has a wide ~~case~~ of ~~uses~~.		The term "Firewall" has grown to encompass many functionalities and has a wide array of meanings.
	The "firewall" is often use ~~interchangably~~ with "router" "gateway" and "UTM" or "Unified Threat Management"		The "firewall" is often use interchangeably with "router" "gateway" and "UTM" or "Unified Threat Management"
	Even the Untangle NGFW is a "next-gen" "firewall." There are also host-based "firewalls" that run on the local host computer.		Even the Untangle NGFW is a "next-gen" "firewall." There are also host-based "firewalls" that run on the local host computer.

Dmorris at 18:14, 20 June 2018

2018-06-20T18:14:16Z

← Older revision		Revision as of 18:14, 20 June 2018
Line 7:		Line 7:
	{\| width='100%'		{\| width='100%'
	\|-		\|-
	\| align="center" \| [[Image:~~Firewall_128x128~~.png]]     '''Firewall'''		\| align="center" \| [[Image:Firewall.png\|128px]]     '''Firewall'''
	\| align="center" \|		\| align="center" \|
	{\|		{\|

Dmorris at 01:35, 19 July 2017

2017-07-19T01:35:23Z

← Older revision		Revision as of 01:35, 19 July 2017
Line 1:		Line 1:
	[[Category:Applications]]		[[Category:Applications]]
	<span style="display:none" class="helpSource firewall">Firewall</span>		<span style="display:none" class="helpSource firewall">Firewall</span>
			<span style="display:none" class="helpSource firewall_status">Firewall#Status</span>
	<span style="display:none" class="helpSource firewall_rules">Firewall#Rules</span>		<span style="display:none" class="helpSource firewall_rules">Firewall#Rules</span>
	<span style="display:none" class="helpSource firewall_event_log">Firewall#Event_Log</span>		<span style="display:none" class="helpSource firewall_event_log">Firewall#Event_Log</span>

Dmorris at 21:33, 14 June 2017

2017-06-14T21:33:21Z

← Older revision		Revision as of 21:33, 14 June 2017
Line 14:		Line 14:
	\|[http://www.untangle.com/store/firewall.html Firewall Description Page]		\|[http://www.untangle.com/store/firewall.html Firewall Description Page]
	\|-		\|-
	\|[http://~~www~~.untangle.com/~~store~~/firewall~~.html~~ Firewall ~~Screenshots~~]		\|[http://demo.untangle.com/admin/index.do#apps/1/firewall Firewall Demo]
	\|-		\|-
	\|[http://forums.untangle.com/firewall/ Firewall Forums]		\|[http://forums.untangle.com/firewall/ Firewall Forums]

Dmorris at 16:41, 12 June 2017

2017-06-12T16:41:25Z

← Older revision		Revision as of 16:41, 12 June 2017
Line 65:		Line 65:

	Additionally a session can be flagged. If '''Flag''' is checked the event is flagged for easier viewing in the event log. Flag is always enabled if the action is Block.		Additionally a session can be flagged. If '''Flag''' is checked the event is flagged for easier viewing in the event log. Flag is always enabled if the action is Block.

			{{AppScreenshot\|firewall\|rules}}

Dmorris at 16:30, 12 June 2017

2017-06-12T16:30:24Z

← Older revision		Revision as of 16:30, 12 June 2017
Line 41:		Line 41:

	This section reviews the different settings and configuration options available for Firewall.		This section reviews the different settings and configuration options available for Firewall.


			=== Status ===

			This displays the current status and some statistics.

			{{AppScreenshot\|firewall\|status}}

Dmorris at 18:42, 29 December 2016

2016-12-29T18:42:08Z

← Older revision		Revision as of 18:42, 29 December 2016
Line 29:		Line 29:
	== About Firewall ==		== About Firewall ==

	Firewall provides traditional [http://en.wikipedia.org/wiki/Firewall firewall] functionality, blocking and/or flagging traffic based on rules. ~~Although the~~ term "Firewall" has grown to encompass many functionalities, the Untangle "Firewall" is a ~~simple~~ traditional firewall used to block and/or flag TCP and UDP sessions passing through Untangle using rules.		Firewall provides traditional [http://en.wikipedia.org/wiki/Firewall firewall] functionality, blocking and/or flagging traffic based on rules.

			The term "Firewall" has grown to encompass many functionalities and has a wide case of uses.
			The "firewall" is often use interchangably with "router" "gateway" and "UTM" or "Unified Threat Management"
			Even the Untangle NGFW is a "next-gen" "firewall." There are also host-based "firewalls" that run on the local host computer.

			The "Firewall" app itself is a traditional firewall used to block and/or flag TCP and UDP sessions passing through Untangle using rules. The ''Firewall'' app provides the same functionality as the traditional "firewall" - the ability to use rules to control which computers and communicate on a network.


Line 44:		Line 50:

	Typically Untangle is installed as a NAT/gateway device, or behind another NAT/gateway device in bridge mode. In this scenario all inbound sessions are blocked by NAT except those explicitly allowed with port forwards. Because of this, the Firewall '''does not block anything by default'''. It is up to you to decide to best fit for your network, whether you only want to block specific ports or you want to block everything and allow only a few services.		Typically Untangle is installed as a NAT/gateway device, or behind another NAT/gateway device in bridge mode. In this scenario all inbound sessions are blocked by NAT except those explicitly allowed with port forwards. Because of this, the Firewall '''does not block anything by default'''. It is up to you to decide to best fit for your network, whether you only want to block specific ports or you want to block everything and allow only a few services.


	=== Rule Actions ===		=== Rule Actions ===

Dmorris at 17:46, 5 June 2016

2016-06-05T17:46:29Z

New page

[[Category:Applications]]
Firewall
Firewall#Rules
Firewall#Event_Log

{| width='100%'
|-
| align="center" | [[Image:Firewall_128x128.png]]     '''Firewall'''
| align="center" |
{|
|-
| Other Links:
|-
|[http://www.untangle.com/store/firewall.html Firewall Description Page]
|-
|[http://www.untangle.com/store/firewall.html Firewall Screenshots]
|-
|[http://forums.untangle.com/firewall/ Firewall Forums]
|-
|[[Firewall Reports]]
|-
|[[Firewall FAQs]]
|}
|}
 
----

== About Firewall ==

Firewall provides traditional [http://en.wikipedia.org/wiki/Firewall firewall] functionality, blocking and/or flagging traffic based on rules. Although the term "Firewall" has grown to encompass many functionalities, the Untangle "Firewall" is a simple traditional firewall used to block and/or flag TCP and UDP sessions passing through Untangle using rules.

== Settings ==

This section reviews the different settings and configuration options available for Firewall.

=== Rules ===

The '''Rules''' tab allows you to specify rules to Block, Pass or Flag traffic that crosses the Untangle.

The [[Rules|Rules documentation]] describes how rules work and how they are configured. Firewall uses rules to determine to block/pass the specific session, and if the sessions is flagged. Flagging a session marks it in the logs for reviewing in the event logs or reports, but has no direct effect on the network traffic.

Typically Untangle is installed as a NAT/gateway device, or behind another NAT/gateway device in bridge mode. In this scenario all inbound sessions are blocked by NAT except those explicitly allowed with port forwards. Because of this, the Firewall '''does not block anything by default'''. It is up to you to decide to best fit for your network, whether you only want to block specific ports or you want to block everything and allow only a few services.

=== Rule Actions ===

* '''Pass''': Allows the traffic which matched the rule to flow.
* '''Block''': Blocks the traffic which matched the rule.

Additionally a session can be flagged. If '''Flag''' is checked the event is flagged for easier viewing in the event log. Flag is always enabled if the action is Block.

== Reports ==

{{:Firewall Reports}}

== Related Topics ==

[[User Guide]]

== Firewall FAQs ==

{{:Firewall FAQs}}