Contributed by jose on from the jacek's-writings dept.
(Comments are closed)
OpenBSD Journal
Contributed by jose on from the jacek's-writings dept.
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By Anonymous Coward () on
Comments
By Anonymous Coward () on
Comments
By Kirill () km-dated-1047740097@krot.org on mailto:km-dated-1047740097@krot.org
block in all
block out all
Blocks everything :)
Comments
By Anonymous Coward () on
Comments
By Anonymous Coward () on
1) Make a list of what should be let through and in what directions.
2) Read the man page.
3) Write a pf.conf.
4) Test.
5) Repeat 2-4 until the tests are successful.
It'll take a while, but it's worth it. pf is great to work with.
By Xavier Santolaria () xsa@bsdcow.net on http://open.bsdcow.net
http://www.xs4all.nl/~hanb/configs/pf.conf-{3.2,current}. You should get enough information there to make it work in your env'.
By Michael Anuzis () on
http://www.anuzis.net/openbsd/day3.html
If you scroll down to "Designing your firewall", section 3; there's an area where I've recommended a basic structure of what order to put your rules in. This is the structure I use and I find it works very well.
just a disclaimer/forwarning the class was taught fairly casually don't expect too much strictness/formality. --Michael
By gryp () gryp@dakin.be on http://gryp.dakin.be
By Anonymous Coward () on
By Anonymous Coward () on
By Anonymous Coward () on
Here's to daniel.
Or RTFM (:0
By Anonymous Coward () on