On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
Also, I might not want to allow the user to open a
random random raw socket, but only one on a specific downstream
port of a macvlan interface, so I can filter out the data from
that respective MAC address in an external switch.
On Thu, Sep 17, 2009 at 01:30:00PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
Also, I might not want to allow the user to open a
random random raw socket, but only one on a specific downstream
port of a macvlan interface, so I can filter out the
On Thursday 17 September 2009, Michael S. Tsirkin wrote:
On Thu, Sep 17, 2009 at 01:30:00PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
Also, I might not want to allow the user to open a
random random raw socket, but only one on a specific
On Thu, Sep 17, 2009 at 02:14:06PM +0200, Arnd Bergmann wrote:
On Thursday 17 September 2009, Michael S. Tsirkin wrote:
On Thu, Sep 17, 2009 at 01:30:00PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
Also, I might not want to allow the user to
On Thursday 17 September 2009, Michael S. Tsirkin wrote:
Well, we could have a char device with an ioctl that gives you back a socket,
or maybe even have it give you back a socket when you open it.
Will that make you happy?
Well, that would put is in the exact same spot as the tun/tap driver
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
vhost-net driver projects
I still think that list should include
- UDP multicast socket support
- TCP socket support
- raw packet socket support for qemu (from Or Gerlitz)
if we have those, plus the tap support that is already on
your
On Wed, Sep 16, 2009 at 04:52:40PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
vhost-net driver projects
I still think that list should include
Yea, why not. Go wild.
- UDP multicast socket support
- TCP socket support
Switch to UDP unicast
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
On Wed, Sep 16, 2009 at 04:52:40PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
vhost-net driver projects
I still think that list should include
Yea, why not. Go wild.
- UDP
On Wed, Sep 16, 2009 at 05:08:46PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
On Wed, Sep 16, 2009 at 04:52:40PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
vhost-net driver projects
I still think
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
No, I think this is less important, because the bridge code
also doesn't do this.
True, but the reason might be that it is much harder in bridge (you have
to snoop multicast registrations). With macvlan you know which
multicasts
On Wed, Sep 16, 2009 at 05:27:25PM +0200, Arnd Bergmann wrote:
On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
No, I think this is less important, because the bridge code
also doesn't do this.
True, but the reason might be that it is much harder in bridge (you have
to
On 09/16/2009 06:27 PM, Arnd Bergmann wrote:
That scenario is probably not so relevant for KVM, unless you
consider the guest taking over the qemu host process a valid
security threat.
It is. We address it by using SCM_RIGHTS for all sensitive operations
and selinuxing qemu as tightly as
12 matches
Mail list logo
