lkml.org 
[lkml]   [2005]   [Sep]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Physical device to Kernel-netlink mapper
Date
Ben Greear wrote:
> Al Boldi wrote:
> > Is there a virtual device that would allow to connect the communication
> > paths from the physical devs into the kernel netlink subsystem in a way
> > that would be more flexible than what is currently avaible?
> >
> > Something like this:
> >
> > Kernel-netlink
> > |
> > virtual dev
> > |
> > --> mapper/conf <--
> > |
> > physical dev(s)
> >
> > tun/tap,bridge,bond... are devs that incorporate this idea, but don't
> > allow for a flexible configuration.
>
> Please explain in more detail.

Consider the bridge:
1. Creates a virtual dev
2. Adds physical devs
3. Connects devs to each other in a fixed way

What is needed is a generalized module that allows step 3 to be completely
flexible.

Thanks!

--
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-09-10 09:02    [W:0.030 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site