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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |