* Physical device to Kernel-netlink mapper
@ 2005-09-09 12:38 Al Boldi
2005-09-09 16:57 ` Ben Greear
0 siblings, 1 reply; 3+ messages in thread
From: Al Boldi @ 2005-09-09 12:38 UTC (permalink / raw)
To: linux-net; +Cc: linux-kernel
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.
Thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Physical device to Kernel-netlink mapper
2005-09-09 12:38 Physical device to Kernel-netlink mapper Al Boldi
@ 2005-09-09 16:57 ` Ben Greear
2005-09-10 4:00 ` Al Boldi
0 siblings, 1 reply; 3+ messages in thread
From: Ben Greear @ 2005-09-09 16:57 UTC (permalink / raw)
To: Al Boldi; +Cc: linux-net, linux-kernel
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.
I have some other types of virtual (ethernet-ish) interfaces, but I have
no idea what you are really asking....
Please explain in more detail.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Physical device to Kernel-netlink mapper
2005-09-09 16:57 ` Ben Greear
@ 2005-09-10 4:00 ` Al Boldi
0 siblings, 0 replies; 3+ messages in thread
From: Al Boldi @ 2005-09-10 4:00 UTC (permalink / raw)
To: Ben Greear; +Cc: linux-net, linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-09-10 4:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-09 12:38 Physical device to Kernel-netlink mapper Al Boldi
2005-09-09 16:57 ` Ben Greear
2005-09-10 4:00 ` Al Boldi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.