From: Tobias DiPasquale <codeslinger@gmail.com>
To: Yun Mao <maoy+netfilter@cis.upenn.edu>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: availability of ROUTE target
Date: Sun, 6 Mar 2005 12:12:54 -0500 [thread overview]
Message-ID: <876ef97a05030609126e4aa085@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503060105470.9386@forty-thieves.cis.upenn.edu>
On Sun, 6 Mar 2005 01:08:05 -0500 (EST), Yun Mao
<maoy+netfilter@cis.upenn.edu> wrote:
> I can't find ipt_ROUTE.c in my 2.6.10 kernel source. I tried google
> "ipt_ROUTE" but only diff patches were found. Any hint on how to use
> the ROUTE target? Thanks!
It's not part of the vanilla sources. To get the ROUTE target, you
need to apply it from patch-o-matic. Check out
http://www.netfilter.org/ for more information on that.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next prev parent reply other threads:[~2005-03-06 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 6:08 availability of ROUTE target Yun Mao
2005-03-06 17:12 ` Tobias DiPasquale [this message]
2005-03-06 17:34 ` Yun Mao
2005-03-06 17:45 ` Tobias DiPasquale
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=876ef97a05030609126e4aa085@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=maoy+netfilter@cis.upenn.edu \
--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