Talk:Firewall, Configuring - Revision history

Jimbo: Reverted edits by 66.92.43.99 (Talk) to last revision by Jimbo

2010-11-15T18:10:30Z

Reverted edits by 66.92.43.99 (Talk) to last revision by Jimbo

66.92.43.99: Another method (file name should be known in advance).

2010-11-15T01:45:55Z

Another method (file name should be known in advance).

Jimbo: Reverted edits by 91.214.128.24 (Talk) to last revision by Jimbo

2010-07-15T17:05:43Z

Reverted edits by 91.214.128.24 (Talk) to last revision by Jimbo

91.214.128.24: /* buy allegra */ new section

2010-07-15T11:38:37Z

buy allegra: new section

Jimbo: dunno about running it as a module

2005-09-08T01:09:54Z

dunno about running it as a module

213.83.138.185: Start/stop

2005-09-07T21:10:40Z

Start/stop

Jimbo: starting and stopping the firewall

2005-09-07T04:17:18Z

starting and stopping the firewall

Jimbo: $inside to any via $iif

2005-09-07T04:13:30Z

$inside to any via $iif

Dave: also, typo?

2005-09-06T17:24:20Z

also, typo?

Dave at 14:58, 6 September 2005

2005-09-06T14:58:12Z

New page

ok, so how do you start and stop the firewall? In linux it's a simple "iptables stop" (or start) -- or the redhat dumbed down version is "service iptables stop"....curious how it's done in FreeBSD (haven't had a need to put a FW on one yet...)

--[[User:Dave|Dave]] 10:58, 6 Sep 2005 (EDT)

← Older revision		Revision as of 18:10, 15 November 2010
Line 33:		Line 33:

	Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)		Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)
−
−	~~One uncommon way to configure the firewall is find configuration~~
−	~~files on the web and test a heavily commented one carefully, then~~
−	~~if it works one essentially does not need to learn the syntax.~~
−	~~Might save a little time...~~

← Older revision		Revision as of 01:45, 15 November 2010
Line 33:		Line 33:

	Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)		Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)
		+
		+	One uncommon way to configure the firewall is find configuration
		+	files on the web and test a heavily commented one carefully, then
		+	if it works one essentially does not need to learn the syntax.
		+	Might save a little time...

← Older revision		Revision as of 17:05, 15 July 2010
Line 33:		Line 33:

	Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)		Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)
−
−	~~== buy allegra ==~~
−
−	~~represent nice video site -~~
−
−	~~<a href=http://trailfire.com/allegra> allegra aventis </a>~~
−
−	~~http://trailfire.com/allegra~~
−	~~<a href=http://trailfire.com/allegra> allegra 180 </a>~~

← Older revision		Revision as of 11:38, 15 July 2010
Line 33:		Line 33:

	Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)		Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)
		+
		+	== buy allegra ==
		+
		+	represent nice video site -
		+
		+	<a href=http://trailfire.com/allegra> allegra aventis </a>
		+
		+	http://trailfire.com/allegra
		+	<a href=http://trailfire.com/allegra> allegra 180 </a>

← Older revision		Revision as of 01:09, 8 September 2005
Line 27:		Line 27:

	In this article, the IPFW is loaded via the kernel, if the firewall was loaded via kernel module, you could issue a "kldunload ipfw.ko".		In this article, the IPFW is loaded via the kernel, if the firewall was loaded via kernel module, you could issue a "kldunload ipfw.ko".
		+
		+	== dunno about running it as a module ==
		+
		+	Never tried. Everything I read said that you needed to build an ipfw kernel, that many things just didn't work properly when you tried to kldload it as a module. I'm not saying I know for a fact that it won't work, just that that's what I've read, and that I haven't tried anything otherwise.
		+
		+	Also, with that said - if you DID build it into the kernel, there IS no such thing as "stopping the firewall" in the manner of kldunloading a module. If it's built into the kernel, the firewall is ALWAYS running - "up" or "down" is a matter of what the ruleset is, not of actually "stopping" a service or daemon. --[[User:Jimbo\|Jimbo]] 21:09, 7 Sep 2005 (EDT)

← Older revision		Revision as of 21:10, 7 September 2005
Line 23:		Line 23:

	For instance that ruleset in the article? Notice that the first line is #!/bin/sh - you guessed it, it's a Bourne shell script, so to start a firewall with that ruleset you would just run that script. You have to define what a "stopped" condition is before I can tell you how to "stop" the firewall. By "stop the firewall" do you mean "drop all traffic" or "pass all traffic"? --[[User:Jimbo\|Jimbo]] 00:17, 7 Sep 2005 (EDT)		For instance that ruleset in the article? Notice that the first line is #!/bin/sh - you guessed it, it's a Bourne shell script, so to start a firewall with that ruleset you would just run that script. You have to define what a "stopped" condition is before I can tell you how to "stop" the firewall. By "stop the firewall" do you mean "drop all traffic" or "pass all traffic"? --[[User:Jimbo\|Jimbo]] 00:17, 7 Sep 2005 (EDT)
		+
		+	== Start/stop ==
		+
		+	In this article, the IPFW is loaded via the kernel, if the firewall was loaded via kernel module, you could issue a "kldunload ipfw.ko".

← Older revision		Revision as of 04:17, 7 September 2005
Line 17:		Line 17:

	I tend to prefer my firewalls to let me-the-user do pretty much anything I want to, as a general rule. It shouldn't really make a whole lot of difference, in practice. --[[User:Jimbo\|Jimbo]] 00:13, 7 Sep 2005 (EDT)		I tend to prefer my firewalls to let me-the-user do pretty much anything I want to, as a general rule. It shouldn't really make a whole lot of difference, in practice. --[[User:Jimbo\|Jimbo]] 00:13, 7 Sep 2005 (EDT)
		+
		+	== starting and stopping the firewall ==
		+
		+	There isn't any real "omg this stops and starts it" sort of command - you just issue the rule commands you want, either directly from the command line or from a script.
		+
		+	For instance that ruleset in the article? Notice that the first line is #!/bin/sh - you guessed it, it's a Bourne shell script, so to start a firewall with that ruleset you would just run that script. You have to define what a "stopped" condition is before I can tell you how to "stop" the firewall. By "stop the firewall" do you mean "drop all traffic" or "pass all traffic"? --[[User:Jimbo\|Jimbo]] 00:17, 7 Sep 2005 (EDT)

← Older revision		Revision as of 04:13, 7 September 2005
Line 11:		Line 11:
	# let everything on your internal network talk to the firewall		# let everything on your internal network talk to the firewall
	$cmd 01101 allow all from $inside to any via $iif keep-state		$cmd 01101 allow all from $inside to any via $iif keep-state
		+
		+	== $inside to any via $iif ==
		+
		+	If you're concerned with preventing address spoofing FROM your internal network going OUT to the real world, yes.
		+
		+	I tend to prefer my firewalls to let me-the-user do pretty much anything I want to, as a general rule. It shouldn't really make a whole lot of difference, in practice. --[[User:Jimbo\|Jimbo]] 00:13, 7 Sep 2005 (EDT)

← Older revision		Revision as of 17:24, 6 September 2005
Line 2:		Line 2:

	--[[User:Dave\|Dave]] 10:58, 6 Sep 2005 (EDT)		--[[User:Dave\|Dave]] 10:58, 6 Sep 2005 (EDT)
		+
		+	== also, typo? ==
		+
		+	# let everything on your internal network talk to the firewall
		+	$cmd 01101 allow all from any to any via $iif keep-state
		+
		+	shouldn't this be
		+	# let everything on your internal network talk to the firewall
		+	$cmd 01101 allow all from $inside to any via $iif keep-state