From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Unable to add rule on Chain with 28 characters.
Date: Fri, 8 Jul 2005 15:50:49 -0400 [thread overview]
Message-ID: <20050708195049.GA7221@bender.817west.com> (raw)
In-Reply-To: <42CECD47.5050003@interage.com.br>
On Fri, Jul 08, 2005 at 04:00:23PM -0300, Rafael Dreher wrote:
> Hi,
>
> I'm trying do add a rule on a user-defined chain, on the NAT table, with 28
> characters.
my guess is you're leaving out the '-t nat' as custom chains only exist
in the table they're created in:
# iptables -t nat -N GqKOJUpUAOboDEbYcaVUCDqprFy
# iptables -t nat -A GqKOJUpUAOboDEbYcaVUCDqprFy -j ACCEPT
# iptables -t nat -A PREROUTING -j GqKOJUpUAOboDEbYcaVUCDqprFy
# iptables -t nat -vnxL
Chain GqKOJUpUAOboDEbYcaVUCDqprFy (1 references)
pkts bytes target prot opt in out source
destination
1 78 ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
1 78 GqKOJUpUAOboDEbYcaVUCDqprFy all -- * *
0.0.0.0/0 0.0.0.0/0
<--- snip --->
# iptables -V && uname -r
iptables v1.3.1
2.6.11.4-21.7-default
i also tested this on:
# iptables -V && uname -r
iptables v1.2.11
2.4.27-2-386
alas--i have no 2.4 + 1.3.1 combo i can test on; so i cannot say there
isn't some weird interaction between those two that causes your issue to
crop up.
-j
--
"Brian: Whose leg do I have to hump to get a dry martini around here?"
--Family Guy
next prev parent reply other threads:[~2005-07-08 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 19:00 Unable to add rule on Chain with 28 characters Rafael Dreher
2005-07-08 19:50 ` Jason Opperisano [this message]
2005-07-08 20:01 ` Rafael Dreher
2005-07-08 20:09 ` Jason Opperisano
2005-07-08 20:11 ` Jason Opperisano
2005-07-09 10:23 ` Jan Engelhardt
2005-07-08 20:10 ` Royce Kemp
2005-07-11 13:11 ` Rafael Dreher
2005-07-11 13:15 ` Jan Engelhardt
2005-07-11 13:22 ` Rafael Dreher
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 18:53 Rafael Dreher
2005-07-11 10:57 ` John A. Sullivan III
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=20050708195049.GA7221@bender.817west.com \
--to=opie@817west.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