Linux Netfilter discussions
 help / color / mirror / Atom feed
From: David T-G <davidtg-netfilter@justpickone.org>
To: NetFilter Users' List <netfilter@lists.netfilter.org>
Cc: "P.Italiaander" <pc-secure@home.nl>
Subject: Re: is forwarding compiled in? (was "Re: SuSEfirewall2 and NAT ...")
Date: Mon, 19 May 2003 10:49:13 -0400	[thread overview]
Message-ID: <20030519144913.GA57271@justpickone.org> (raw)
In-Reply-To: <200305161954.18096.pc-secure@home.nl>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

Pascal, et al --

...and then P.Italiaander said...
% 
...
% At first I thought somebody would notice ,but you have a hugh hole in your 
% firewall :
% so you do:
% 
% Chain INPUT (policy DROP)
% target     prot opt source               destination
% ACCEPT     all  --  anywhere             anywhere
% ACCEPT     all  --  anywhere             anywhere           state 
% RELATED,ESTABLISHED

Hmmm...  Yes, now that you've pointed it out I see that :-)

At this point I don't actually care, because I'm having so much trouble
trying to get NATting to work.  But I certainly don't want to stick with
this!

I've decided to give up on the SuSEfirewall2 front end and write the
rules myself.  For one thing, I *don't* have a ppp interface; I use eth0
and eth1!

I wonder if I even have forwarding compiled into the kernel, though.  Per
the 'Masqerading Made Simple' HOWTO I tried

  linux:~ #modprobe ipt_MASQERADE
  modprobe: Can't locate module ipt_MASQERADE

so it isn't a module and yet forwarding doesn't seem to work.  For a last
try (before starting over completely) I will try your


% iptables -A FORWARD -m state --state NEW -i $int_if -o $ext_if -j ACCEPT

suggestion as well.


Thanks a bunch & HAND

:-D
-- 
David T-G                      * There is too much animal courage in 
(play) davidtg@justpickone.org * society and not sufficient moral courage.
(work) davidtgwork@justpickone.org  -- Mary Baker Eddy, "Science and Health"
http://justpickone.org/davidtg/      Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

      reply	other threads:[~2003-05-19 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 20:39 SuSEfirewall2 and NAT help : i am so lost! David T-G
2003-05-15 20:51 ` Jeremy C. Reed
2003-05-15 21:18   ` David T-G
2003-05-15 22:45     ` David T-G
2003-05-16 12:49       ` Aide Florent
2003-05-16 15:16         ` David T-G
2003-05-16 17:54           ` P.Italiaander
2003-05-19 14:49             ` David T-G [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=20030519144913.GA57271@justpickone.org \
    --to=davidtg-netfilter@justpickone.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=pc-secure@home.nl \
    /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