From: wyonker@dcsnow.com wyonker@dcsnow.com
To: lartc@vger.kernel.org
Subject: [LARTC] Masquerading under 2.4
Date: Thu, 11 Jan 2001 22:47:02 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416861@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416855@msgid-missing>
<PRE>Well I guess I deserved that. I saw my mistake after I sent this
message but of course it was too late by then. Sorry.
On 11 Jan 2001, at 22:30, Arthur van Leeuwen wrote:
><i> On Thu, 11 Jan 2001 <A HREF="mailto:wyonker@dcsnow.com">wyonker@dcsnow.com</A> wrote:
</I>><i>
</I>><i> > On 11 Jan 2001, at 15:45, Arthur van Leeuwen wrote:
</I>><i> >
</I>><i> > > Check out Rusty Russel's Linux 2.4 NAT HOWTO on
</I>><i> > > <A HREF="http://netfilter.kernelnotes.org/unreliable-guides/NAT-HOWTO.html">http://netfilter.kernelnotes.org/unreliable-guides/NAT-HOWTO.html</A>
</I>><i>
</I>><i> > Cool. That worked great. I have one more question please.
</I>><i>
</I>><i> > What is the replacement for ipmasqadm and where can I find some
</I>><i> > documentation on it?
</I>><i>
</I>><i> If you had really read the Linux 2.4 NAT HOWTO, you would've known
</I>><i> that the PREROUTING and POSTROUTING tables also handle port
</I>><i> forwarding. And that the 2.4 NAT HOWTO describes *that* as well.
</I>><i>
</I>><i> Doei, Arthur.
</I>><i>
</I>><i> --
</I>><i> /\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need
</I>><i> the money
</I>><i> /__\ / | A friend is someone with whom | Love like you have never
</I>><i> been hurt
</I>><i> / \/__ | you can dare to be yourself | Dance like there's nobody
</I>><i> watching
</I>
</PRE>
next prev parent reply other threads:[~2001-01-11 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 14:45 [LARTC] Masquerading under 2.4 Arthur
2001-01-11 15:12 ` Willis
2001-01-11 20:12 ` wyonker
2001-01-11 21:30 ` Arthur
2001-01-11 22:47 ` wyonker [this message]
2001-01-12 1:51 ` wyonker
2001-01-12 9:51 ` Arthur
2001-01-13 0:37 ` wyonker
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-lartc-98373940416861@msgid-missing \
--to=wyonker@dcsnow.com \
--cc=lartc@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.