On Tue, May 21, 2019 at 5:28 PM Nicolas Dichtel
wrote:
>
> Le 21/05/2019 à 07:53, Tonghao Zhang a écrit :
> [snip]
> > The problem is that we create one vxlan netdevice(e.g dstport 4789 and
> > external), and move it to
> > one net-namespace, and then we hope create one again(dstport 4789 and
> >
Le 21/05/2019 à 07:53, Tonghao Zhang a écrit :
[snip]
> The problem is that we create one vxlan netdevice(e.g dstport 4789 and
> external), and move it to
> one net-namespace, and then we hope create one again(dstport 4789 and
> external) and move it to other net-namespace, but we can't create it.
On Tue, May 21, 2019 at 7:53 AM David Miller wrote:
>
> From: xiangxia.m@gmail.com
> Date: Fri, 17 May 2019 19:42:23 -0700
>
> > From: Tonghao Zhang
> >
> > Don't allow to remove the vxlan device to other namesapce,
> > because we maintain the data of vxlan net device on original
> > net-name
From: xiangxia.m@gmail.com
Date: Fri, 17 May 2019 19:42:23 -0700
> From: Tonghao Zhang
>
> Don't allow to remove the vxlan device to other namesapce,
> because we maintain the data of vxlan net device on original
> net-namespace.
>
> $ ip netns add ns100
> $ ip link add vxlan100 typ
From: Tonghao Zhang
Don't allow to remove the vxlan device to other namesapce,
because we maintain the data of vxlan net device on original
net-namespace.
$ ip netns add ns100
$ ip link add vxlan100 type vxlan dstport 4789 external
$ ip link set dev vxlan100 netns ns100
$ ip netn
