* Network namespace and tc?
@ 2008-02-13 23:59 Stephen Hemminger
2008-02-14 8:07 ` Denis V. Lunev
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2008-02-13 23:59 UTC (permalink / raw)
To: netdev
It looks like tc filter won't work on alternate namespaces:
/* Add/change/delete/get a filter node */
static int tc_ctl_tfilter(struct sk_buff *skb, struct nlmsghdr *n, void *arg)
{
...
if (net != &init_net)
return -EINVAL;
Haven't played with namespace virtualization yet, but what else is
not supported? Where is this documented?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Network namespace and tc?
2008-02-13 23:59 Network namespace and tc? Stephen Hemminger
@ 2008-02-14 8:07 ` Denis V. Lunev
2008-02-14 8:37 ` Daniel Lezcano
0 siblings, 1 reply; 3+ messages in thread
From: Denis V. Lunev @ 2008-02-14 8:07 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev
Hello, Stephen!
Namespaces are not fully implemented yet :) Right now we we have only
basic infrastructure in the mainstream and, currently, we can't even run
TCP in different namespace :( We hope this will be changed very soon.
These marks (net != &init_net) are used to
- mark places we need to modify
- ensure that we do not break initial namespace.
Regards,
Den
On Wed, 2008-02-13 at 15:59 -0800, Stephen Hemminger wrote:
> It looks like tc filter won't work on alternate namespaces:
> /* Add/change/delete/get a filter node */
>
> static int tc_ctl_tfilter(struct sk_buff *skb, struct nlmsghdr *n, void *arg)
> {
> ...
>
> if (net != &init_net)
> return -EINVAL;
>
>
> Haven't played with namespace virtualization yet, but what else is
> not supported? Where is this documented?
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Network namespace and tc?
2008-02-14 8:07 ` Denis V. Lunev
@ 2008-02-14 8:37 ` Daniel Lezcano
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Lezcano @ 2008-02-14 8:37 UTC (permalink / raw)
To: Denis V. Lunev; +Cc: Stephen Hemminger, netdev, Linux Containers
Denis V. Lunev wrote:
> Hello, Stephen!
>
> Namespaces are not fully implemented yet :) Right now we we have only
> basic infrastructure in the mainstream and, currently, we can't even run
> TCP in different namespace :( We hope this will be changed very soon.
>
> These marks (net != &init_net) are used to
> - mark places we need to modify
> - ensure that we do not break initial namespace.
>
> Regards,
> Den
>
> On Wed, 2008-02-13 at 15:59 -0800, Stephen Hemminger wrote:
>> It looks like tc filter won't work on alternate namespaces:
>> /* Add/change/delete/get a filter node */
>>
>> static int tc_ctl_tfilter(struct sk_buff *skb, struct nlmsghdr *n, void *arg)
>> {
>> ...
>>
>> if (net != &init_net)
>> return -EINVAL;
>>
>>
>> Haven't played with namespace virtualization yet, but what else is
>> not supported? Where is this documented?
I wrote some documentation here:
http://lxc.sourceforge.net/network.php
That talk about configuration, bench, etc ...
Your question make me feel I should add a matrix with the current state
of the network namespace, what is in, what is done but not merged yet,
what is planned and what is not planned.
Thanks for paying attention at this.
-- Daniel
Sauf indication contraire ci-dessus:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400
Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 ?
SIREN/SIRET : 552 118 465 02430
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-02-14 8:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-13 23:59 Network namespace and tc? Stephen Hemminger
2008-02-14 8:07 ` Denis V. Lunev
2008-02-14 8:37 ` Daniel Lezcano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).