From: Steve Wise <[EMAIL PROTECTED]>
Date: Wed, 26 Jul 2006 11:15:43 -0500
> Dave, what do you think about removing the user-space stuff for the
> first round of integration? IE: Just add netevents and kernel hooks to
> generate them.
Sure.
-
To unsubscribe from this list: send the line "unsubs
On Wed, 2006-07-26 at 13:39 +1000, Herbert Xu wrote:
> On Tue, Jul 25, 2006 at 10:05:40AM -0500, Steve Wise wrote:
> >
> > But they really are seeing a delete followed by an add. That's what the
> > kernel is doing.
>
> Actually that's the other thing I don't really like. The user-space
> monit
On Tue, Jul 25, 2006 at 10:05:40AM -0500, Steve Wise wrote:
>
> But they really are seeing a delete followed by an add. That's what the
> kernel is doing.
Actually that's the other thing I don't really like. The user-space
monitor may perceive that a route was actually deleted and replaced
by a
On Tue, 2006-07-25 at 17:39 +1000, Herbert Xu wrote:
> Steve Wise <[EMAIL PROTECTED]> wrote:
> >
> > Routing redirect events are broadcast as a pair of rtmsgs, RTM_DELROUTE
> > and RTM_NEWROUTE.
>
> This may confuse existing rtnetlink users since you're generating an
> RTM_DELROUTE message that's
Steve Wise <[EMAIL PROTECTED]> wrote:
>
> Routing redirect events are broadcast as a pair of rtmsgs, RTM_DELROUTE
> and RTM_NEWROUTE.
This may confuse existing rtnetlink users since you're generating an
RTM_DELROUTE message that's identical to one triggered by something
like 'ip route del'.
As y
This patch adds netevent and netlink calls for neighbour change, route
add/del, pmtu change, and routing redirect events.
Netlink Details:
Neighbour change events are broadcast as a new ndmsg type RTM_NEIGHUPD.
Path mtu change events are broadcast as a new rtmsg type RTM_ROUTEUPD.
Routing redi
