Am 26.05.2015 um 16:36 schrieb Alexander Holler:
Am 26.05.2015 um 14:10 schrieb Nicolas Dichtel:
I don't understand why dumping in another netns is a problem.
It isn't. I just wondered how you (or someone else) is using
NETLINK_LISTEN_ALL_NSID, assuming it already serves a purpose. ;)
Maybe
Am 26.05.2015 um 14:10 schrieb Nicolas Dichtel:
Le 26/05/2015 12:53, Alexander Holler a écrit :
Am 25.05.2015 um 15:09 schrieb Nicolas Dichtel:
[snip]
Hmm, sounds like we're talking in different rooms about the same thing
in regard
to the dump. ;)
I just wanted to explain why I think this se
Le 26/05/2015 12:53, Alexander Holler a écrit :
Am 25.05.2015 um 15:09 schrieb Nicolas Dichtel:
[snip]
Hmm, sounds like we're talking in different rooms about the same thing in regard
to the dump. ;)
I just wanted to explain why I think this series misses the (extended) dump
which includes al
Am 25.05.2015 um 15:09 schrieb Nicolas Dichtel:
Le 25/05/2015 12:55, Alexander Holler a écrit :
Am 25.05.2015 um 09:45 schrieb Nicolas Dichtel:
Le 22/05/2015 22:50, Alexander Holler a écrit :
First I think if NETLINK_LISTEN_ALL_NSID is enabled, a dump
of the interfaces through RTM_GETLINK to
Le 25/05/2015 12:55, Alexander Holler a écrit :
Am 25.05.2015 um 09:45 schrieb Nicolas Dichtel:
Le 22/05/2015 22:50, Alexander Holler a écrit :
First I think if NETLINK_LISTEN_ALL_NSID is enabled, a dump
of the interfaces through RTM_GETLINK together with NLM_F_DUMP and
NLM_F_REQUEST should r
Am 25.05.2015 um 09:45 schrieb Nicolas Dichtel:
Le 22/05/2015 22:50, Alexander Holler a écrit :
First I think if NETLINK_LISTEN_ALL_NSID is enabled, a dump
of the interfaces through RTM_GETLINK together with NLM_F_DUMP and
NLM_F_REQUEST should return all interfaces of all reachable namespaces.
Le 22/05/2015 22:50, Alexander Holler a écrit :
Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
So I am dense. I have read through the patches and I don't see where
you tag packets from other network namespaces with a network namespace
id.
Me too,
I've recently written a little tool calle
Am 22.05.2015 um 23:29 schrieb Cong Wang:
On Fri, May 22, 2015 at 2:12 PM, Alexander Holler wrote:
Bridge doesn't have an underlying link, so no LINK_NETNSID. LINK_NETNSID
is only added when its underlying link is in a different netns.
I'm using "link" similiar as interface. Maybe I've no i
Am 22.05.2015 um 23:19 schrieb Eric W. Biederman:
Alexander Holler writes:
Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
So I am dense. I have read through the patches and I don't see where
you tag packets from other network namespaces with a network namespace
id.
Me too,
You need t
On Fri, May 22, 2015 at 2:12 PM, Alexander Holler wrote:
>>
>> Bridge doesn't have an underlying link, so no LINK_NETNSID. LINK_NETNSID
>> is only added when its underlying link is in a different netns.
>
>
> I'm using "link" similiar as interface. Maybe I've no idea what the
> attribute LINK:NETS
Alexander Holler writes:
> Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
>>
>> So I am dense. I have read through the patches and I don't see where
>> you tag packets from other network namespaces with a network namespace
>> id.
>
> Me too,
You need to use recvmsg, and then parse out the NE
Am 22.05.2015 um 23:04 schrieb Cong Wang:
On Fri, May 22, 2015 at 1:50 PM, Alexander Holler wrote:
Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
So I am dense. I have read through the patches and I don't see where
you tag packets from other network namespaces with a network namespace
id
On Fri, May 22, 2015 at 1:50 PM, Alexander Holler wrote:
> Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
>>
>>
>> So I am dense. I have read through the patches and I don't see where
>> you tag packets from other network namespaces with a network namespace
>> id.
>
>
> Me too,
>
> I've recent
Am 08.05.2015 um 14:02 schrieb Eric W. Biederman:
So I am dense. I have read through the patches and I don't see where
you tag packets from other network namespaces with a network namespace
id.
Me too,
I've recently written a little tool called snetmanmon (source is
available at github) to m
From: Nicolas Dichtel
Date: Thu, 7 May 2015 11:02:46 +0200
> This idea was informally discussed in Ottawa / netdev0.1. The goal is to
> ease the use/scalability of netns, from a userland point of view.
> Today, users need to open one netlink socket per family and per netns.
> Thus, when the numb
15 matches
Mail list logo
