On Fri, 9 Apr 2010, per...@pluto.rain.com wrote:
Ian Smith smi...@nimnet.asn.au wrote:
http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
rant
This is absolutely the worst section of an otherwise great
handbook ... Nothing short of a rewrite from scratch could
fix it ...
In freebsd-questions Digest, Vol 305, Issue 9, Message: 1
On Thu, 8 Apr 2010 08:10:34 -0400 Robert Huff roberth...@rcn.com wrote:
Adam Vande More writes:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be
Ian Smith writes:
So ... double-checking I'm doing this right:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
I thought from your earlier mail that you wanted to use in-kernel
NAT?
I want whatever works. :-)
Beyond that ... all other
On Fri, 9 Apr 2010, Robert Huff wrote:
Ian Smith writes:
So ... double-checking I'm doing this right:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
I thought from your earlier mail that you wanted to use in-kernel
NAT?
Ian Smith smi...@nimnet.asn.au wrote:
http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
rant
This is absolutely the worst section of an otherwise great
handbook ... Nothing short of a rewrite from scratch could
fix it ...
As always, I'm sure a patch -- to provide that rewrite --
Adam Vande More writes:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?
Logging is compiled into the modules and there are a few sysctl's.
Adam Vande More writes:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?
Logging is compiled into the modules and there are a few sysctl's.
On Thu, Apr 8, 2010 at 7:10 AM, Robert Huff roberth...@rcn.com wrote:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
2) in the kernel config:
#options IPFIREWALL #firewall
#options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
#options
On Thu, 8 Apr 2010 08:10:34 -0400 Robert Huff roberth...@rcn.com wrote:
So ... double-checking I'm doing this right:
1) in /boot/loader.conf:
ipfw_load=YES
ipdivert_load=YES
yes; see NAT HB 31.9.3
2) in the kernel config:
IMHO, and according to Adam Vandr More, kernel options are
IMHO, and according to Adam Vandr More, kernel options are no
longer required.
The original reason I asked was:
30.6.2 Kernel Options
It is not a mandatory requirement to enable IPFW by
compiling the following options into the FreeBSD
I am setting up a router to share one Wi-Fi link between a few computers that
only support CAT-5. Like a wireless access point except wired and wireless
sides are reversed. My question is about the ipfw packet filter. From the
handbook section on NAT, 31.9.3, I can achieve what I need with boot
On Wed, Apr 7, 2010 at 9:51 PM, Gary Dunn o...@aloha.com wrote:
I am setting up a router to share one Wi-Fi link between a few computers
that only support CAT-5. Like a wireless access point except wired and
wireless sides are reversed. My question is about the ipfw packet filter.
From the
Adam Vande More writes:
I am setting up a router to share one Wi-Fi link between a few computers
that only support CAT-5. Like a wireless access point except wired and
wireless sides are reversed. My question is about the ipfw packet filter.
From the handbook section on NAT, 31.9.3,
On Wed, Apr 7, 2010 at 11:28 PM, Robert Huff roberth...@rcn.com wrote:
If compiled into the kernel, there's a set of optional settings
(VERBOSE, LOG_LINIT, DEFAULT_TO_ACCEPT, etc) that can be set there.
If using the module, how does one set these?
Logging is compiled into the
14 matches
Mail list logo
