(off-list ancestor, not in this archive)
Re: network namespace and kernel bind issue · Eric W. Biederman <hidden> · 2012-10-01
Re: network namespace and kernel bind issue · Stephen Hemminger <hidden> · 2012-10-01
Re: network namespace and kernel bind issue · Eric W. Biederman <hidden> · 2012-10-01
Re: network namespace and kernel bind issue · Stephen Hemminger <hidden> · 2012-10-01
Re: network namespace and kernel bind issue · Eric W. Biederman <hidden> · 2012-10-02
Re: network namespace and kernel bind issue · Stephen Hemminger <hidden> · 2012-10-02
Re: network namespace and kernel bind issue · Julian Anastasov <ja@ssi.bg> · 2012-10-02
Re: network namespace and kernel bind issue · Stephen Hemminger <hidden> · 2012-10-02
[PATCH net-next] vxlan: put UDP socket in correct namespace · Stephen Hemminger <hidden> · 2012-10-02
Re: [PATCH net-next] vxlan: put UDP socket in correct namespace · Eric W. Biederman <hidden> · 2012-10-02
[PATCHv2 net-next] vxlan: put UDP socket in correct namespace · Stephen Hemminger <hidden> · 2012-10-02
Re: [PATCHv2 net-next] vxlan: put UDP socket in correct namespace · Eric W. Biederman <hidden> · 2012-10-02
Re: [PATCHv2 net-next] vxlan: put UDP socket in correct namespace · David Miller <davem@davemloft.net> · 2012-10-02

Re: network namespace and kernel bind issue

From: Stephen Hemminger <hidden>
Date: 2012-10-02 00:48:44

The problem was vxlan wasn't doing sk_change_net on the created socket.

I'm testing that fix.

The long term fix is to change sock_create_kern() to take a 'struct net'
argument. This would avoid the trap of having to change the namespace.
Also several places using __sock_create() could use it.

L2TP still looks to have several namespace related issues.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help