Dan Smith wrote: > BH> Ok, I don't remember Dave's email. > > https://lists.linux-foundation.org/pipermail/containers/2010-February/023135.html > > However, now that I've gone in and done some looking and replacing my > print statements with %pI6, I think it may actually be kept in memory > in network byte order, which means I don't need to switch it. Does > that sound right? :) Yes, it sounds right to me. > BH> Well, what does an 'ip -6 a' show before and after a checkpoint? > > Yeah, I end up with an extra address. I think ignoring the > link-local ones sounds like a good plan, for now at least. Can I ask what the addresses were? Did you move from VM to VM so the underlying NIC MAC address changed? Again, I don't know your typical user for C/R. For example, with IPv4 you save all the addresses, but if one of them was configured via DHCP, you could have an address conflict when you restore it, since there's no way to know if it's been handed-out to another system in the meantime. Or does a typical C/R user only have static addresses? With IPv6 it gets worse because the link-local will get created automatically, and if you're in a VM it will probably be somewhat random. Then when you move to another VM you'll get another virtual NIC with a different MAC address. Since the global address is going to be based off the same lower 64-bits, you'll wind-up with a second global in most situations (since you're restoring the original address). It almost seems as though you only want to C/R manually configured IPv6 addresses (those marked IFA_F_PERMANENT) since those are going to be static to that "system", and in that case the admin has probably disabled the address auto-configuration process. I guess you'll find out as people use it and complain, then you can add knobs to control the behavior, or simply document the restrictions. -Brian _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
