Re: [RFC] [patch 0/6] [Network namespace] introduction

On Fri, Jun 09, 2006 at 11:02:02PM +0200, [email protected] wrote:
> What is missing ?
> -----------------
> The routes are not yet isolated, that implies:
> 
>    - binding to another container's address is allowed
> 
>    - an outgoing packet which has an unset source address can
>      potentially get another container's address
> 
>    - an incoming packet can be routed to the wrong container if there
>      are several containers listening to the same addr:port

- renaming an interface in one "namespace" affects everyone.
-
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/

Follow-Ups:
- Re: [RFC] [patch 0/6] [Network namespace] introduction
  - From: Daniel Lezcano <[email protected]>

References:
- [RFC] [patch 0/6] [Network namespace] introduction
  - From: [email protected]

Prev by Date: Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
Next by Date: Re: Driver model ISA bus
Previous by thread: Re: [RFC] [patch 0/6] [Network namespace] introduction
Next by thread: Re: [RFC] [patch 0/6] [Network namespace] introduction
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]