From: ddx@ddx.ml.org
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.102 and ipfwadm
Date: Sat, 16 May 1998 19:01:58 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356531045@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222356531042@msgid-missing>
On Sat, 16 May 1998, David S. Miller wrote:
>
> You need to install the new ipfwchains utilities from:
>
> http://www.adelaide.net.au/~rustcorp/ipfwchains/ipfwchains.html
hmms ok i have it
problem is i can't get it working how i want it...
hope som1 here has done it and can say me how to do
i asked on irc on some linux channels
but all guys answered to go back to 2.1.101
i normally did :
ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.0.0/24 -D 0.0.0.0/0
but from now this does not work
so i did try some thing with that new tool
ipchains -A forward -j DENY
ipchains -I forward -j ACCEPT -s 192.168.0.0/24 -d 0.0.0.0/0
what i think would do the same after looking in the docs
[root@ddx /root]# ipchains -L forward
Chain forward (policy ACCEPT):
target prot opt source destination ports
ACCEPT all ------ 192.168.0.0/24 anywhere n/a
DENY all ------ anywhere anywhere n/a
but then ping and telnet from an internal box does not work
so i hope som1 here can tell me what i do wrong...
>
> And I don't want to hear complaints about this, if you use CVS you
but what i heard cvs was the only way to get a working kernel
cose i can't use normal kernel files
> deal with late breaking (no pun intended) developments and changes to
> the code. What ends up in UltraPenguin will have the updated ipfwadm
> utility from the ipfwchains toolset to complement the ipfw rewrite in
> the kernel.
ok i understand
next prev parent reply other threads:[~1998-05-16 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-16 17:12 2.1.102 and ipfwadm ddx
1998-05-16 19:01 ` ddx [this message]
1998-05-16 19:49 ` David S. Miller
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=marc-linux-ultrasparc-90222356531045@msgid-missing \
--to=ddx@ddx.ml.org \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.