From: Patrick McHardy <kaber@trash.net>
To: dkiba@yandex.ru
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: REDIRECT in kernel >= 2.6.15 broken???
Date: Wed, 25 Jan 2006 11:05:28 +0100 [thread overview]
Message-ID: <43D74D68.5090808@trash.net> (raw)
In-Reply-To: <43D74B7D.000002.25194@pantene.yandex.ru>
KdF wrote:
> Is there a problem with REDIRECT in kernels >= 2.6.15?
>
> We are using 2.6.14 on a router and billing stations, and users with exceeded quotas are redirected to local server, but after test upgrade to 2.6.15, 15.1 and 16-rc1 REDIRECT seems not to work :(
>
> Packets get forwarded as usual without any attempt to be redirected.
> Netfilter is built as a part of whole kernel, not a module.
> DNAT does not work too in this case, but 2.6.14.6 works fine on same ruleset and kernel config.
Works fine for me. Please post some details about your setup, the
exact rules you're using and what (if any) patches you've applied.
next prev parent reply other threads:[~2006-01-25 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:57 REDIRECT in kernel >= 2.6.15 broken??? KdF
2006-01-25 10:05 ` Patrick McHardy [this message]
2006-01-25 11:04 ` KdF
2006-01-25 11:31 ` Patrick McHardy
2006-01-25 15:21 ` KdF
2006-01-26 11:19 ` Patrick McHardy
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=43D74D68.5090808@trash.net \
--to=kaber@trash.net \
--cc=dkiba@yandex.ru \
--cc=netfilter-devel@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 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.