[lxc-devel] Communication between single network namespace

Eric Brower ebrower at gmail.com
Thu Mar 10 05:29:29 UTC 2011


I've not worked with very recent kernels, but my recollection is that
a new network namespace (CLONE_NEWNET) is created with no network
devices (and, therefore, routing table entries) aside from the
loopback device, which is initially down.  Your code snippet is not
very helpful, but I'm guessing the error message is correct-- the
unshare'd process does not inherit the system's (parent namespace's)
devices or routing table.  Network device addition must be performed
from the parent namespace (refer to the 'ip' man page, and look for
'netns'), and device configuration/routing must still be configured
from within the clone'd process.

My suggestion to you is spawn a shell within your unshare'd process,
and poke around a bit to understand the environment you have created.

E

On Wed, Mar 9, 2011 at 8:52 PM, Maheswara Reddy  C - ERS, HCL Tech
<maheswarareddyc at hcl.com> wrote:
> Hi,
>
> I am implementing client/server programming in a single network namespace using AF_INET, but client connet() failing with error Network unreachable.
> Shall we use AF_INET or AF_UNIX, could some one explain.
>
>
> Int main()
> {
>
> if (unshare(CLONE_NEWNET)) {
>        perror("unshare");
>        return 1;
>         }
>
>   pthread_create(&thread1,NULL ,&server,(void*)valPtr);  // AF_INET   server socket
>   pthread_create(&thread2,NULL ,&client,(void*)valPtr);    // AF_INET client
>
>
> }
>
>
>
> Thanks
> Mahesh
>
> ::DISCLAIMER::
> -----------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
> It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
> this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
> this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
> received this email in error please delete it and notify the sender immediately. Before opening any mail and
> attachments please check them for viruses and defect.
>
> -----------------------------------------------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Lxc-devel mailing list
> Lxc-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-devel
>



-- 
E




More information about the lxc-devel mailing list