From: David Miller <davem@davemloft.net>
To: kadlec@blackhole.kfki.hu
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] Introduce notification events for routing changes
Date: Wed, 28 Nov 2012 17:59:29 -0500 (EST) [thread overview]
Message-ID: <20121128.175929.618012822860698468.davem@davemloft.net> (raw)
In-Reply-To: <1354048045-17846-2-git-send-email-kadlec@blackhole.kfki.hu>
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Date: Tue, 27 Nov 2012 21:27:25 +0100
> The netfilter MASQUERADE target does not handle the case when the routing
> changes and the source address of existing connections become invalid.
> The problem can be solved if routing modifications create events to which
> the MASQUERADE target can subscribe and then delete the affected
> connections.
>
> The patch adds the required event support for IPv4/IPv6.
>
> Signed-off-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
What part of the information are you actually interested in?
Because just saying that a route is added or removed using fib_info X
doesn't tell you a whole lot.
fib_info only encapsulates the information that can be shared heaving
with many ipv4 routes. It doesn't include the TOS or other aspects
stored in the fib_alias part. I can only guess that you did not
use fib_alias in order to avoid having to export that structure to
the callers, as it is currently private to net/ipv4/
The notifier doesn't seem to distinguish between adds or removes
either, making it less useful in another way.
I would suggest passing a super-structure that gives the event type:
struct route_changed_info {
enum {
add,
remove,
} event_type;
void *data;
};
or something like that.
Can you also show us exactly how this will be used? Otherwise we
have to guess.
next prev parent reply other threads:[~2012-11-28 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 20:27 [PATCH 0/1] Introduce notification events for routing changes Jozsef Kadlecsik
2012-11-27 20:27 ` [PATCH 1/1] " Jozsef Kadlecsik
2012-11-27 20:32 ` Chris Wilson
2012-11-28 22:59 ` David Miller [this message]
2012-11-28 23:34 ` Jozsef Kadlecsik
2012-11-29 9:05 ` Jozsef Kadlecsik
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=20121128.175929.618012822860698468.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).