From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: netfilter@lists.netfilter.org
Subject: Re: iptables random support
Date: Wed, 2 Aug 2006 10:39:22 +0800 [thread overview]
Message-ID: <015101c6b5dc$dc8eb390$0100a8c0@newlife> (raw)
In-Reply-To: Pine.LNX.4.61.0608011305260.29748@yvahk01.tjqt.qr
I took the patch and apply to a vanilla 2.6.17.7, it failed :-
patching file include/linux/netfilter_ipv4/ipt_random.h
patching file include/linux/netfilter_ipv6/ip6t_random.h
patching file net/ipv4/netfilter/Kconfig
Hunk #1 succeeded at 314 with fuzz 2 (offset -34 lines).
patching file net/ipv4/netfilter/Makefile
Hunk #1 FAILED at 64.
1 out of 1 hunk FAILED -- saving rejects to file net/ipv4/netfilter/Makefile.rej
patching file net/ipv4/netfilter/ipt_random.c
patching file net/ipv6/netfilter/Kconfig
Hunk #1 succeeded at 123 with fuzz 2 (offset -24 lines).
patching file net/ipv6/netfilter/Makefile
Hunk #1 FAILED at 12.
1 out of 1 hunk FAILED -- saving rejects to file net/ipv6/netfilter/Makefile.rej
patching file net/ipv6/netfilter/ip6t_random.c
----- Original Message -----
From: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
To: "Daniel Williams" <danielw@staff.iinet.net.au>
Cc: <netfilter@lists.netfilter.org>
Sent: Tuesday, August 01, 2006 7:06 PM
Subject: Re: iptables random support
> >
> >I have been trying to get iptables -m random support working to very
> >little success.
> >
> >Does anyone have a modern 2.6 kernel with iptables -m random working ?
>
> http://freshmeat.net/p/jen_kernel/
> look for random in the .tar.bz2
>
>
> Jan Engelhardt
> --
>
next prev parent reply other threads:[~2006-08-02 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 13:52 iptables random support Daniel Williams
[not found] ` <427c54c0607301802h40c9f934l679e822899cf5c61@mail.gmail.com>
2006-07-31 1:20 ` Fwd: " Daniel De Graaf
2006-08-01 11:06 ` Jan Engelhardt
2006-08-02 2:39 ` Ming-Ching Tiew [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 1:13 Daniel Williams
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='015101c6b5dc$dc8eb390$0100a8c0@newlife' \
--to=mingching.tiew@redtone.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