From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Source routing, sort of
Date: Mon, 24 Dec 2001 21:38:59 +0000 [thread overview]
Message-ID: <marc-lartc-100922997111628@msgid-missing> (raw)
On Mon, Dec 24, 2001 at 03:57:24PM -0500, Michael T. Babcock wrote:
> I'm assuming some basic source NATting is required; off to read the
> docs again ...
I hate self-follow-ups, but after reading the SNAT target for iptables,
that's exactly what I need, except on a 2.2.19 kernel. I'd love to
migrate to 2.4.x but we have a driver that doesn't work properly on
2.4, so we're stuck on 2.2.x for the reasonable future.
Any way to do SNAT or another way to do what I described using 2.2.x?
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2001-12-24 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-24 21:38 Michael T. Babcock [this message]
2001-12-25 13:08 ` [LARTC] Re: Source routing, sort of Jerome Petazzoni
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-100922997111628@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox