Re: AF_UNIX sockets crossing namespace based boundaries

2019-01-17 Thread Eric W. Biederman
Andrew Lunn writes: > On Wed, Jan 02, 2019 at 10:22:36AM -0500, Donald Sharp wrote: >> I am only creating a network namespace, but I don't think this changes >> my core question. >> >> Suppose I am running FRR/zebra in the default namespace and I startup >> a BGP instance in namespace one. BGP

Re: AF_UNIX sockets crossing namespace based boundaries

2019-01-02 Thread Andrew Lunn
On Wed, Jan 02, 2019 at 10:22:36AM -0500, Donald Sharp wrote: > I am only creating a network namespace, but I don't think this changes > my core question. > > Suppose I am running FRR/zebra in the default namespace and I startup > a BGP instance in namespace one. BGP will connect to the default >

Re: AF_UNIX sockets crossing namespace based boundaries

2019-01-02 Thread Donald Sharp
I am only creating a network namespace, but I don't think this changes my core question. Suppose I am running FRR/zebra in the default namespace and I startup a BGP instance in namespace one. BGP will connect to the default namespaces zebra instance. Now suppose I am running FRR/zebra in the defa

Re: AF_UNIX sockets crossing namespace based boundaries

2019-01-02 Thread Andrew Lunn
On Tue, Jan 01, 2019 at 07:46:07PM -0500, Donald Sharp wrote: > I have created multiple namespaces: > > sharpd@robot /v/l/frr> ip netns list > two (id: 2) > one (id: 1) > EVA (id: 0) > > And am running a process in namespace two that creates a named socket > `/var/log/frr/run/zserv.api`: Hi Dona

AF_UNIX sockets crossing namespace based boundaries

2019-01-01 Thread Donald Sharp
I have created multiple namespaces: sharpd@robot /v/l/frr> ip netns list two (id: 2) one (id: 1) EVA (id: 0) And am running a process in namespace two that creates a named socket `/var/log/frr/run/zserv.api`: sharpd@robot ~/frr> sudo ip netns exec two /usr/lib/frr/zebra -N two --daemon -A 127.0.