From: ccie2be (ccie2be@nyc.rr.com)
Date: Tue Feb 15 2005 - 10:04:34 GMT-3
Thanks, Alexei,
So the bottom line is this:
Even when stateless autoconfiguration is used, before 2 hosts on the same
local-link can communicate, DHCP and DNS must be up and running and properly
configured, true?
The Neighbor Solicitation message and response are essentially a different
way of doing what ARP did in ipv4.
Am I correct?
Some of this ipv6 documentation is so detailed that it's hard to see the
forest from the trees.
Thanks again. Tim
----- Original Message -----
From: "asadovnikov" <asadovnikov@comcast.net>
To: "'kinwai'" <kinwai@singnet.com.sg>; "'ccie2be'" <ccie2be@nyc.rr.com>
Cc: <ccielab@groupstudy.com>
Sent: Monday, February 14, 2005 10:30 PM
Subject: RE: ipv6 neighbor solicitation
> And here is how to configure it:
>
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5187/products_conf
> iguration_guide_chapter09186a00801d65f5.html#wp1126687
>
> The example shows router configured as both DHCP server and the actual
IPv6
> router, but certainly the server can be remote. The command "ipv6 nd
>
other-config-flag"(http://www.cisco.com/univercd/cc/td/doc/product/software/
> ios123/123cgcr/ipv6_r/ipv6_07g.htm#wp1921566) is the key here as it tells
> the host to go to DHCP server for more information after the IPv6 address
is
> obtained via stateless configuration. So the DNS info can be pulled from
> the DHCP server.
>
> Best Regards,
> Alexei
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> kinwai
> Sent: Monday, February 14, 2005 12:17 PM
> To: ccie2be
> Cc: ccielab@groupstudy.com
> Subject: Re: ipv6 neighbor solicitation
>
> According to rfc3736
>
> To obtain configuration parameters through stateless DHCP, a node uses the
> DHCP Information-request message. DHCP servers respond to the node's
> message with a Reply message that carries configuration parameters for the
> node. The Reply message from the server can carry configuration
> information, such as a list of DNS recursive name servers [3] and SIP
> servers [5].
>
> http://www.tahi.org/conformance/ct-profile-host/dd/DDDHCPv6.html
>
> this should be how the process looks like =)
>
> --- ccie2be <ccie2be@nyc.rr.com> wrote:
>
> > Hi Kinwai,
> >
> > Thanks for getting back to me but you didn't clear up my problem.
> >
> > Please see in-line comments.
> > ----- Original Message -----
> > From: "kinwai" <kinwai@singnet.com.sg>
> > To: "ccie2be" <ccie2be@nyc.rr.com>
> > Cc: "Group Study" <ccielab@groupstudy.com>
> > Sent: Monday, February 14, 2005 11:51 AM
> > Subject:
>
> Re: ipv6 neighbor solicitation
> >
> >
> > > R1 will send a NS(ICMPv6 Type 135) to R2
> > > Source address of himself... destination will be a
> > (Solicitied-note
> > mulitcast) which will copy the last 24 bits of the destination R2(or
> > a
> > host?)
> > >
> > > When you want to send to R2 or any other host, you will know the
> > destination ipv6 address in the first place.
> > ******************
> > How does host1 (or any sender) find out the ipv6 destination address
> > of host
> > 2 in the first place? I assume it's via DNS, but if so, how does
> > host1 find
> > out the iv6 address of the DNS server if autoconfig is being used?
> >
> > Thanks, Tim
> >
> > ********************
> > >
> > > Source mac address as usual. Destination mac will be a standard
> > mac
> > address of 33:33:FF:01:00:0B.
> > >
> > > All the routers will listen to it and respond by default.
> > >
> > > sh ipv6 interface output
> > > -----
> > > GigabitEthernet0/1 is up, line protocol is up
> > > IPv6 is enabled, link-local address is FE80::201:FF:FE01:1
> > > Description: ***
> > > Global unicast address(es):
> > > 2001:1::1, subnet is 2001:1::/64
> > > Joined group address(es):
> > > FF02::1 (interface-local, link local level)
> > > FF02::2 (link-local, link local level )
> > > FF02::1:FF00:1 (solicated-node muliticast also,auto enable)
> > > FF02::1:FF01:1 (this is the one!!)
> > > ------
> > >
> > >
> > > --- ccie2be <ccie2be@nyc.rr.com> wrote:
> > >
> > > > Hi guys,
> > > >
> > > > I'm trying to understand the NS process used in ipv6 but so far,
> > I
> > > > haven't
> > > > found a complete explanation.
> > > >
> > > > In particular, I know that when an ipv6 host wants to
> > communicate
> > > > with another
> > > > ipv6 on the same local-link but doesn't have the address of
> > that
> > > > other host,
> > > > it sends a Neighbor Solicitation message to that other host.
> > For
> > > > this
> > > > message, it creates the destination ipv6 address by
> > concatenating
> > > > the last 24
> > > > bits of the neighbor's ipv6 to a 104 bit multicast address.
> > > >
> > > > What I don't understand is from where would the host find it's
> > > > neighbor's ipv6
> > > > address? I assume for this it uses DNS, but how does it get
> > the
> > > > ipv6 address
> > > > of the DNS server assuming it's using stateless
> > autoconfiguration?
> > > >
> > > > If someone can explain this process, I would be greatly
> > > > appreciative.
> > > >
> > > > TIA, Tim
> > > >
> > > >
> > _______________________________________________________________________
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:20 GMT-3