Private address space doesn’t exist in IPv6 (at least not like the private address space in IPv4). The idea is precisely that we don’t need that, otherwise we will create IPv6 NAT, which will work all the work done for moving to IPv6.
I will not use either 6to4 (2002) addresses, otherwise, you will not be able to reach hosts that use those addresses outside of your network.
I will suggest instead, specially for a lab network, to use link-local addresses or not sure if this is correct, but may be also the reserved prefix, which will not be routed outside your network. See: http://www.apps.ietf.org/rfc/rfc3849.html
Regards,
Jordi
De: Ronald Heitmann <[EMAIL PROTECTED]>
Responder a: <[EMAIL PROTECTED]>
Fecha: Fri, 09 Sep 2005 08:43:38 +0200
CC: "[email protected]" <[email protected]>
Asunto: Re: how to add default gateway on Linux host
hi,
all fine.
I'd like to mention, that site-local addresses _have_ allready been deprecated in September 2004 (RFC 3879) so they are not part of the ipv6-standard anymore.
ULI would be an solution in future, maybe 6to4-address space would be an idea today.
Regards,
//Ronald
Mark Smith wrote:
On Thu, 8 Sep 2005 14:09:57 -0700 (PDT)
Susan Zheng <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote:
Hi,
I'm a beginner for IPv6 need to set up a small private IPv6 network.
The lab setup plan is like below:
Use 1 windows 2003 server which has two IPv6 interfaces configured as
default routers(it has two NIC cards) connected to net1 and net2.
My linux host 1 is on net1 and linux host 2 is on net 2. Both are IPv6 enablled. The goal is to let the two hosts on different subnet to ping each other by their site-scope address.
Note:
The two hosts can ping each other in IPv4 addresses, but can't reach each
other by IPv6 addresses.
Any advices about what need to do are very much appreciated!
Well, you could configure a static default on both Linux boxes, pointing
to the IPv6 link local address of the corresponding interface they're
attached to on the Win 2003 server.
Alternatively, and generally a better idea, as this is how IPv6 was
designed to be used, run a Router Advertising service on the Windows
2003 box, which can both inform the Linux hosts of their IPv6 site-local
prefixes and subnets (the first 64 bits of the address), and their
default router address. That makes the Linux host configuration
plug-and-play.
I don't know what service will perform this router advertisement do this
under Windows 2003 server unfortunately as I don't use it.
btw, don't get too fixed on the idea of deploying site-local addresses,
I'm pretty sure they've recently been deprecated, to be replaced with
Unique Local Addresses or ULAs. ULAs have similar routing properties to
site-locals (e.g. they aren't supposed to be routed across the
Internet), however they've added a unique part to the address allowing
sites or organisations to be joined together with a very low
probability of subnet number collisions. This site joining includes via
a VPN. There are a number of other advantages to ULAs over site-locals.
HTH,
Mark.
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
************************************
The IPv6 Portal: http://www.ipv6tf.org
Barcelona 2005 Global IPv6 Summit
Information available at:
http://www.ipv6-es.com
This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
