From: Patrick McHardy <kaber@trash.net>
To: Gilles Kerdoncuff <gkerdoncuff.ext@orange-ftgroup.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Update SNMP basic for full IP address NAT
Date: Thu, 23 Nov 2006 14:49:00 +0100 [thread overview]
Message-ID: <4565A6CC.1090404@trash.net> (raw)
In-Reply-To: <455C7E46.6080404@orange-ftgroup.com>
Gilles Kerdoncuff wrote:
> ** I understand that you'd like to keep the /8 behavior, yet, something
> still troubles me with the current ip_nat_snmp_basic.c file :
>
> The from/to fields of the oct1_map structure are filled-in by calling
> the NOCT1 (0xFF mask) macro on the tuple IP.
> Which means that on a 192.168.1.x address, it takes the x part.
I'm confused - you seem to be right, but quick testing shows it behaves
correctly and takes the 192 part.
> On the second hand, the mangle_address routine is called with
> "ctx->pointer - 4", which points to the beginning of the IP. So, the
> routine will compare the x part to the '192' part !!
>
> Am I misinterpretting the code or is it really a bug ?
> My understanding is that the '192' part of the address should be subject
> to the NAT translation, correct ?
Yes.
> ** Anyway, if any use case for the /8 behavior exists, I don't mind
> adding a parameter to test only the first 8,16,24 or 32 bits of the
> address, keeping /8 as a default.
Please do so. But why only 8,16,24,32? I don't believe allowing
any prefix len will be harder to do.
next prev parent reply other threads:[~2006-11-23 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 10:44 [PATCH] Update SNMP basic for full IP address NAT zze-Ganesh KERDONCUFF G ext RD-MAPS-REN
2006-11-15 6:45 ` Patrick McHardy
2006-11-16 15:05 ` Gilles Kerdoncuff
2006-11-23 13:49 ` Patrick McHardy [this message]
2006-11-23 16:09 ` Gilles Kerdoncuff
2006-11-23 16:15 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 17:38 zze-Ganesh KERDONCUFF G ext RD-MAPS-REN
2006-11-03 10:23 ` 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=4565A6CC.1090404@trash.net \
--to=kaber@trash.net \
--cc=gkerdoncuff.ext@orange-ftgroup.com \
--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.