Before someone reinvents the wheel, did anyone actually bother following
the discussion that happened here on netdev:
http://marc.theaimsgroup.com/?t=101751064400001&r=1&w=2
If Stefan Rompf hasnt disapeared or is buried in work somewhere,
all pieces are already in place. thats what the device netcarrier state
is for.
cheers,
jamal
On Thu, 20 Jun 2002, James Morris wrote:
> On Wed, 19 Jun 2002, Andi Kleen wrote:
>
> > On Wed, Jun 19, 2002 at 05:44:05PM -0400, Chris Friesen wrote:
> > > Andi Kleen wrote:
> > >
> > > > I would suggest sending a netlink message from the driver. That's
> > > > really
> > > > what netlink was designed for.
> > >
> > > Can you point me to a driver that's done this cleanly as an example to
> > > follow?
> >
> > Not exactly a driver, but you can e.g. look at the ip_queue netfilter
> > module.
> >
>
> It's not a very clean example at this stage, unfortunately, as it contains
> some fairly ugly logic for maintaining unicast sessions.
>
> If you don't specifically need unicast Netlink (which I don't think you
> do), try also looking at the tcpdiag & ctnetlink code.
>
>
> - James
> --
> James Morris
> <jmorris@xxxxxxxxxxxxxxxx>
>
>
|