From: Togan Muftuoglu <toganm@dinamizm.com>
To: netfilter@lists.netfilter.org
Subject: Re: help with routing/firewall
Date: Thu, 18 Dec 2003 20:11:24 +0100 [thread overview]
Message-ID: <20031218191124.GP29795@dinamizm.com> (raw)
In-Reply-To: <013501c3c592$f845d8d0$7000a80a@melita.com>
* Ian Hunter; <ihunter@hunterweb.net> on 18 Dec, 2003 wrote:
>SuSE comes with a script called SuSEfirewall that automatically configures
>things for you. You probably don't want that if you're talking to folks on
>this list.
>
>See if you have iptables or ipchains -- type iptables-save and if you get
>output, post it to the list and we'll see what SuSE is doing firewall wise.
http://sourceforge.net/projects/susefaq has an unofficial manual for
SuSEfirewall.
And no SuSUfirewall does not automatically configures anything
especially when it is security :-)
--
Togan Muftuoglu
next prev parent reply other threads:[~2003-12-18 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 18:01 help with routing/firewall Fred Gurn
2003-12-18 18:08 ` Juan Hernandez
2003-12-18 18:15 ` Ian Hunter
2003-12-18 18:33 ` Jeffrey Laramie
2003-12-18 19:11 ` Togan Muftuoglu [this message]
2003-12-18 18:19 ` Jeffrey Laramie
2003-12-18 20:46 ` Rob Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 19:29 Togan Muftuoglu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031218191124.GP29795@dinamizm.com \
--to=toganm@dinamizm.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox