From: "David S. Miller" <davem@davemloft.net>
To: Harald Welte <laforge@netfilter.org>
Cc: linux-net@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] MASQUERADE handling of device events
Date: Thu, 11 Nov 2004 14:58:38 -0800 [thread overview]
Message-ID: <20041111145838.6bdb40ce.davem@davemloft.net> (raw)
In-Reply-To: <20041108135025.GF12437@sunbeam.de.gnumonks.org>
On Mon, 8 Nov 2004 14:50:25 +0100
Harald Welte <laforge@netfilter.org> wrote:
> Dave: would the two changes below be acceptable for you?
>
> > 1) export inet_confirm_addr
This one I think is OK.
> > 2) change inet_ifa_match to use ifa_local instead of ifa_address.
> > Since ifa_local != ifa_address on ppp interfaces, inet_ifa_match
> > could not be used to verify ppp interface addresses without
> > this change.
This one on the other hand is a serious semantic change
and needs more careful thought. ifa_address is used for
a reason, and people expecting that are going to break
if we change things this way.
A study of at least the net/ipv4/devinet.c shows that this
ifa_address vs. ifa_local distinction is definitely on
purpose. I really don't think we can make this suggested
change therefore.
next prev parent reply other threads:[~2004-11-11 22:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 18:18 [PATCH] MASQUERADE handling of device events Phil Oester
2004-11-08 1:06 ` Henrik Nordstrom
2004-11-08 13:50 ` Harald Welte
2004-11-11 22:58 ` David S. Miller [this message]
2004-11-08 16:05 ` Patrick McHardy
2004-11-08 16:15 ` Phil Oester
2004-11-08 16:24 ` Patrick McHardy
2004-11-08 16:34 ` Phil Oester
2004-11-08 21:55 ` Phil Oester
2004-11-09 11:04 ` Patrick McHardy
2004-11-09 16:53 ` Phil Oester
2004-11-09 17:44 ` Patrick McHardy
2004-11-21 2:58 ` Rusty Russell
2004-11-23 21:16 ` Phil Oester
2004-11-24 3:37 ` Rusty Russell
2004-11-24 9:24 ` Henrik Nordstrom
2004-11-24 15:39 ` Herve Eychenne
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=20041111145838.6bdb40ce.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=laforge@netfilter.org \
--cc=linux-net@vger.kernel.org \
--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.