From: David Cary Hart <DCH@TQMcube.com>
To: Sam Loy <sampaw@mac.com>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Still having problems...
Date: Wed, 30 Jun 2004 16:44:22 -0400 [thread overview]
Message-ID: <1088628262.4626.0.camel@localhost> (raw)
In-Reply-To: <9E8B5B9C-CAC3-11D8-A356-000A95AD0230@mac.com>
On Wed, 2004-06-30 at 14:30, Sam Loy wrote:
> I sorry to be such a newbie, but I still cannot get my firewall up and
> running.
>
> Actually, I had it working with the enclosed script, until I generated
> /etc/sysconfig/iptables using /sbin/service iptables save.
>
I'm not sure what OS you are using but I have found that the easiest
way to configure netfilter is through the Webmin modules. Have you tried
it.
> After I tried to get things to spin up at boot time it quit
> working...not sure what I did.
>
> I erased my tracks, can still ping and set the net before loading
> iptables. Afterwords, I can't even ping the 192.168.1.1 interface on
> the same machine!
>
> Anyway, jason, antony, dick, a lot of you have been very helpful. Thank
> you so much for your continued help and patience.
>
> It is starting to make sense, but I still don't get it. I'm also in
> processing of up2dating my linux. maybe that will help.
>
> fwscript is the script I'm using (from Jason with slight mods). I run
> it after I connect ppp0 and get an ip from my isp, before running
> dhcpd. stillnowork is the output of iptables-save.
>
> Like I said, it worked until I tried to get it to start at boot time.
>
> Thanks,
>
> Sam
--
David Cary Hart
Hart's PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x58A60BB1
prev parent reply other threads:[~2004-06-30 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 18:30 Still having problems Sam Loy
2004-06-30 20:44 ` David Cary Hart [this message]
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=1088628262.4626.0.camel@localhost \
--to=dch@tqmcube.com \
--cc=netfilter@lists.netfilter.org \
--cc=sampaw@mac.com \
/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