[Planetlab-devel] IPv6 support for MyPLC
maoke
mk at cernet.edu.cn
Wed Nov 8 04:12:26 EST 2006
hi jim, rick, marc and all,
pity that i'm late to join this discussion due to time-difference! :P i
understand that jim was talking about the prefix (first 64 bit) for an
interface, and therefore the remained problem was selecting prefixes
(/64) for each vserver. right?
recall to the problem of distinguish vservers on a same node, we can
apply either different prefixes or different interface ids.
the former approach might be quite straightforward, without need of
assigning different mac address for the vservers. the concerns to be
faced will be: (1) one planetlab node might need several prefixes, then
should they aggregated in a single block (e.g. a /56 one) or not? to the
concern of routing, the answer is "yes"; (2) we probably cannot expect
dhcpv6 working in this scenario, because there is not a way to identify
which vserver is asking for an address. (3) there should be a mechanism
implemented in the root context in order that one vserver can send or
receive packets only over its corresponding address. addresses not
belongs to it must be not "visible" in a certain vserver's context.
personally i prefer the latter approach, i.e. making every vserver has
its own virtual (logical) interface and corresponding eui-64 MAC
address. it should be noticed that even the host root context can
determine which vserver is responsible for a packet according to its
prefix, dhcpv6 interaction also needs the client vserver has unique MAC
address as well as link-local IPv6 address, in order that the server can
distinguish the vservers on a same host node. different interface ids
give us a freedom in selecting the way of address auto-configuration -
dhcpv6-based or in the stateless way.
Marc has mentioned a method to substitute FF:FE in the eui-64 format
with the sliver id. i think this is a good idea. on the other hand, if
we can get a special company id (first 24 bits in MAC address) for
vserver like xen or vmware, why don't we do this? ;-)
best,
maoke
Bound, Jim wrote:
>
> For IPv6 for a link it can support multiple prefixes per link. So lets
> say on PLL vserver is its own link. There could be multple prefixes for
> one NIC all using the same EUI for IPv6. Depending on the PLL prefix
> you select will identify what each link vserver uses. Thus I think
> stateless autoconfig can work just need good router that handles the
> node discovery in front of PLL vserver node. All the choices marc
> listed for DNS are a decision to be made. Just so you know years ago we
> moved all the IPv6 node discovery ICMPv6 packets up to user space and
> then from there did DynDNS (yours truly wrote that code :--)).
>
> But PLL is using Linux right not UNIX variant?
>
> Bottom line this is very doable but it will take some tinkering with the
> interface to the vserver incantations and sounds like some code changes?
>
> /jim
>
>
>> -----Original Message-----
>> From: McGeer, Patrick C
>> Sent: Tuesday, November 07, 2006 7:35 PM
>> To: Bound, Jim; 'Marc E. Fiuczynski'; 'devel at lists.planet-lab.org'
>> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
>>
>> 1. Yes, there are multiple (often, >= 20) vservers/machine.
>> 2. I'll let Marc describe how IP config is done. Or can we
>> get enough info just by logging into an arbitrary PL node and
>> running ifconfig?
>>
>> -----Original Message-----
>> From: Bound, Jim
>> Sent: Tuesday, November 07, 2006 4:31 PM
>> To: McGeer, Patrick C; 'Marc E. Fiuczynski';
>> 'devel at lists.planet-lab.org'
>> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
>>
>> Rick,
>>
>> OK yes v6 makes that much better.
>>
>> So are there multiple vservers per machine?
>>
>> If you have a paper that explains how IP config is done I can
>> go read that too? If answer is yes to the above next questions :--)
>>
>> thx
>> /jim
>>
>>
>>> -----Original Message-----
>>> From: McGeer, Patrick C
>>> Sent: Tuesday, November 07, 2006 7:26 PM
>>> To: Bound, Jim; Marc E. Fiuczynski; devel at lists.planet-lab.org
>>> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
>>>
>>> Jim,
>>> One of the problems that PlanetLab has is that we only have one v4
>>> address per machine (gee, think more address bits would solve this
>>> problem?). So the ugly choices are to share the port space (which
>>> we're doing), or do some hideous on-box NAT thing.
>>>
>>> The cool thing about v6 (well, one cool thing about v6) is
>>>
>> that we can
>>
>>> give each sliver (aka, each virtual machine) its own v6
>>>
>> address. So
>>
>>> we haven't faced this issue in v4 because
>>> v4 is too limited to give us the possibility.
>>>
>>> -- Rick
>>>
>>> -----Original Message-----
>>> From: devel-bounces at planet-lab.org
>>> [mailto:devel-bounces at planet-lab.org] On Behalf Of Bound, Jim
>>> Sent: Tuesday, November 07, 2006 3:35 PM
>>> To: Marc E. Fiuczynski; devel at lists.planet-lab.org
>>> Subject: RE: [Planetlab-devel] IPv6 support for MyPLC
>>>
>>> How does it work with IPv4 today?
>>>
>>> I don't how the vserver configures its IP address and if it uses an
>>> IPv6 implementation it must know node discovery thus
>>>
>> stateless could
>>
>>> work.
>>>
>>> DHCPv6 assumes their is a DHCPv6 client on the vserver?
>>>
>>> /jim
>>>
>>>
>>>> -----Original Message-----
>>>> From: devel-bounces at planet-lab.org
>>>> [mailto:devel-bounces at planet-lab.org] On Behalf Of Marc E.
>>>>
>>> Fiuczynski
>>>
>>>> Sent: Tuesday, November 07, 2006 5:59 PM
>>>> To: devel at lists.planet-lab.org
>>>> Subject: [Planetlab-devel] IPv6 support for MyPLC
>>>>
>>>> [This thread was on started on a separate mailing list.
>>>>
>>> I've shut down
>>>
>>>> that mailing list and would like to continue on the devel mailing
>>>> list.]
>>>>
>>>> We are still plugging along on the required kernel fixes to
>>>>
>>> support a
>>>
>>>> unique
>>>> IPv6 address per sliver (i.e., a vserver or virtual machine) on
>>>> PlanetLab.
>>>> While this seems to be making happy progress, there are at
>>>>
>>> least two
>>>
>>>> issues that we need to resolve for which it would be great to get
>>>> feedback /
>>>> thoughts:
>>>>
>>>> 1) What IPv6 address should be assigned to a sliver (static or
>>>> autoconf'd)?
>>>>
>>>> and
>>>>
>>>> 2) How to get the IPv6 addresses assigned to slivers into DNS?
>>>>
>>>> Marc
>>>>
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at lists.planet-lab.org
>>>> https://lists.planet-lab.org/mailman/listinfo/devel
>>>>
>>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at lists.planet-lab.org
>>> https://lists.planet-lab.org/mailman/listinfo/devel
>>>
>>>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel
>
>
>
More information about the Devel
mailing list