Thank you for your info!
My current IPv6 set up situation is like described as below:
The two linux hosts can ping their default gateway's site-local addresses,
i.e. each site-local address connect to the other net.
For example:
---------------
host1 from net1 can ping the other net's --> net2 side-local address through it's own net1's link-local address (gateway). And host2 from net2 can ping the other net --> net1 side-local address through it's own net2's link-local address (gateway).
Problem:
----------
host1 from net1 cannot ping host2 from net2 via their site-local addresses.
Note: The router (Win2003 server) is configured via netsh which has routing enabled, forward enabled and interface published.
On Linux hosts, I've added a static route to the other net site-local address via its own net's router link-local address. And, a default route ::/0 via its own net's router link-local address.
Not sure if the above configuration still have some problem or something else needs to be done to make it work --> The two hosts from differrent subnet can reach each other?
Thank you very much for the help!
Susan
Mark Smith <[EMAIL PROTECTED]> wrote:
On Thu, 8 Sep 2005 14:09:57 -0700 (PDT)
Susan Zheng <[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 box es, 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 t he 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]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
