Linux Container Development
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley-VXdhtT5mjnY@public.gmane.org>
To: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [PATCH 1/2] C/R: Support for IPv6 addresses on network devices
Date: Thu, 25 Mar 2010 17:28:52 -0400	[thread overview]
Message-ID: <4BABD594.1020301@hp.com> (raw)
In-Reply-To: <87aatwf74u.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>

Dan Smith wrote:
>>> +#define HTON_IPV6(dst, src) __BYTE_ORDER_COPY(htonl, dst, src)
>>> +#define NTOH_IPV6(dst, src) __BYTE_ORDER_COPY(ntohl, dst, src)
> 
> BH> Yuck, this is ugly, use ipv6_addr_copy() please.
> 
> So, I started with ipv6_addr_copy(), but that leaves the addresses in
> the host endianess within the checkpoint image, right?  Dave Miller
> had previously asked to have the IPv4 addresses htonl()'d before being
> written to the image, so I was doing the same here.

Ok, I don't remember Dave's email.

> BH> I am still worried about this.  When an interface is activated and
> BH> the IPv6 module is loaded, it's going to generate a link-local address
> BH> right away.  Then it will auto-configure an address based on information
> BH> in a received router advertisement.  Is this code going to conflict
> BH> with that?  Meaning, will you have two link-locals on this interface
> BH> once the system is running?
> 
> I have to claim IPv6 ignorance here :)

Well, what does an 'ip -6 a' show before and after a checkpoint?

-Brian

  parent reply	other threads:[~2010-03-25 21:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 19:40 C/R: Fixup IPv6 support Dan Smith
     [not found] ` <1269459625-21033-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-24 19:40   ` [PATCH 1/2] C/R: Support for IPv6 addresses on network devices Dan Smith
     [not found]     ` <1269459625-21033-2-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-25 20:36       ` Brian Haley
     [not found]         ` <4BABC967.5090908-VXdhtT5mjnY@public.gmane.org>
2010-03-25 21:01           ` Dan Smith
     [not found]             ` <87aatwf74u.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-03-25 21:28               ` Brian Haley [this message]
     [not found]                 ` <4BABD594.1020301-VXdhtT5mjnY@public.gmane.org>
2010-03-26 15:35                   ` Dan Smith
     [not found]                     ` <87634jf63u.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-03-30 15:35                       ` Brian Haley
     [not found]                         ` <4BB21A45.4050300-VXdhtT5mjnY@public.gmane.org>
2010-03-30 16:17                           ` Dan Smith
     [not found]                             ` <87zl1peqd4.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-03-30 17:05                               ` Brian Haley
     [not found]                                 ` <4BB22F73.60704-VXdhtT5mjnY@public.gmane.org>
2010-03-30 18:07                                   ` Dan Smith
     [not found]                                     ` <87r5n1el9z.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-03-30 19:56                                       ` Brian Haley
2010-03-24 19:40   ` [PATCH 2/2] C/R: Fix storing IPv6 addresses and handle the "ipv6only" socket flag Dan Smith

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=4BABD594.1020301@hp.com \
    --to=brian.haley-vxdhtt5mjny@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox