From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: kelly@cliffhanger.com
Cc: netfilter@lists.netfilter.org
Subject: Re: Is there a way....
Date: Mon, 01 May 2006 15:50:51 +0100 [thread overview]
Message-ID: <4456204B.6090407@dsl.pipex.com> (raw)
In-Reply-To: <20060430211531.GH23121@Knoppix>
kelly@cliffhanger.com wrote:
> This link may have an answer. I haven't read the
> entire thing but, it talks about netfilter and the
> iproute2 utility.
>
> http://www.policyrouting.org/PolicyRoutingBook/ONLINE/CH08.web.html
>
>
> It's an online copy of a book (I have the hard
> copy). It's a very good book.
>
> Policy Routing With Linux - Online Edition
> by Matthew G. Marsh
>
> http://www.policyrouting.org/PolicyRoutingBook/ONLINE/TOC.html
>
I don't think stateless NAT with ip works in 2.6 kernels.
Andy.
next prev parent reply other threads:[~2006-05-01 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 23:43 Is there a way David Sims
2006-04-30 21:15 ` kelly
2006-05-01 14:50 ` Andy Furniss [this message]
2006-05-01 3:45 ` Rob Sterenborg
2006-05-02 21:02 ` R. DuFresne
2006-05-03 2:22 ` David Sims
2006-05-02 22:40 ` kelly
2006-05-04 19:40 ` Pascal Hambourg
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=4456204B.6090407@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=kelly@cliffhanger.com \
--cc=netfilter@lists.netfilter.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