All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <groeck-gvzKVTG1yJJBDgjK7y7TUQ@public.gmane.org>
To: Elwin Stelzer Eliazer <stelzere-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: Using 127.n.x.x/16 for namespace to host
Date: Mon, 6 Jul 2009 17:28:42 -0700	[thread overview]
Message-ID: <20090707002842.GA20703@redback.com> (raw)
In-Reply-To: <638f07d70907061546h5e017064t57ee22f45fa746b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Look for ipv4_is_loopback().

Another option might be to use link local addresses.

Guenter

On Mon, Jul 06, 2009 at 03:46:20PM -0700, Elwin Stelzer Eliazer wrote:
> Hi,
> 
> I am using an internal bridge for internal socket communication between the
> host and various containers' applications.
> This is purely an internal bridge and no external traffic is expected in
> this.
> I can use a regular private ip address subnet for this, for example a
> 192.168.x.x/16 for this, and things are working.
> But since the applications at the container and host handle external traffic
> as well, we are forced to exclude this internal subnet for external use.
> Using a 127.n.x.x/16 subnet is preferred, since that is not expected to be
> used externally.
> But this is requiring kernel code change, since 127.0.0.1/8 is programmed
> for loopback interface 'lo' in host.
> Towards this tried changing:
>      IFF_LOOPBACK 0x10 // in in.h, changed from 0x8 to 0x10
>      ifa->ifa_prefixlen = 16; // in devinet.c, changed from 8 to 16
> And still do not see them connected.
> 
> Any suggestions on this will be appreciated.
> 
> regards,
> Elwin.
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers

  parent reply	other threads:[~2009-07-07  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 22:46 Using 127.n.x.x/16 for namespace to host Elwin Stelzer Eliazer
     [not found] ` <638f07d70907061546h5e017064t57ee22f45fa746b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-07  0:28   ` Guenter Roeck [this message]
     [not found]     ` <20090707002842.GA20703-gvzKVTG1yJJBDgjK7y7TUQ@public.gmane.org>
2009-07-07  9:09       ` Elwin Stelzer Eliazer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090707002842.GA20703@redback.com \
    --to=groeck-gvzkvtg1yjjbdgjk7y7tuq@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=stelzere-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.