IP Routing with a subnet and internet

Sorry. I was so immersed in IP land I've overlooked one vital thing you need to get this to work. You need to bridge the two network connections on PC2.

Basically, you highlight your two network connection in "Network Connections" and right click on them. Then select "Bridge Connections ".

There are a couple of guides here:

http://www.microsoft.com/windowsxp/using/networking/expert/crawford_02april22.mspx

http://www.homenethelp.com/web/howto/windows-xp-bridge-setup.asp

http://www.windowsnetworking.com/articles_tutorials/wxpbrdge.html

They tend to concentrate on bridge a wired network to a wireless network, but the process is the same.

 

Bridge is successful, but still no IPv6 pinging

Hi reggie,
Thanks for pointing out the bridging for both connections.
Now I bridged the two NIC on PC2 and I set the IP address to 192.168.1.12
Gateway as 192.168.1.1.
And for PC1, the IP address is 192.168.1.11 with gateway as 192.168.1.1

With no other route added to any route table, from PC1, I can ping any IPv4 internet address or 192.168.1.x address fine.

But my main goal is trying to PING a IPv6 address from PC1 through PC2 to the internet. Sadly, this is still not successful!
On both PC1 and PC2, I already have IPv6 installed.
From PC1, I can ping PC2's bridged IPv6 address.
From PC2, I can ping PC1's NIC IPv6 address as well.

The problem is, from PC1 and PC2, I am not able to ping any IPv6 address on the internet. like ipv6.google.com or www.ist-ipv6.org..... none of these works.
I tried the following (from both PC1 and PC2):
1) ping -6 www.ist-ipv6.org
Pinging www.ist-ipv6.org [2a01:48:1:0:2e0:81ff:fe05:4658] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Ping statistics for 2a01:48:1:0:2e0:81ff:fe05:4658:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

2) ping6 www.ist-ipv6.org
Pinging www.ist-ipv6.org [2a01:48:1:0:2e0:81ff:fe05:4658]
from fe80::2:55ff:fe3f:4ef4%4 with 32 bytes of data:
Reply from fe80::2:55ff:fe3f:4ef4%4: Destination address unreachable.
Reply from fe80::2:55ff:fe3f:4ef4%4: Destination address unreachable.
Reply from fe80::2:55ff:fe3f:4ef4%4: Destination address unreachable.
Reply from fe80::2:55ff:fe3f:4ef4%4: Destination address unreachable.
Ping statistics for 2a01:48:1:0:2e0:81ff:fe05:4658:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

3) ping www.ist-ipv6.org (this works, but since using ping, it treats it as IPv4)
Pinging www.ist-ipv6.org [213.172.48.141] with 32 bytes of data:
Reply from 213.172.48.141: bytes=32 time=138ms TTL=42
Reply from 213.172.48.141: bytes=32 time=146ms TTL=42
Reply from 213.172.48.141: bytes=32 time=147ms TTL=42
Reply from 213.172.48.141: bytes=32 time=134ms TTL=42
Ping statistics for 213.172.48.141:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 147ms, Average = 141ms

ipv6.google.com or www.ist-ipv6.org should be a valid IPv6 address because I can sucessfully ping it from this website tool: http://www.berkom.blazing.de/tools/ping.cgi

Any idea guys?
Thanks again for the help so far!
Greatly appreciated!

 

OK - glad you've got it working.

I don't use IPv6. Rumours of the death of IPv4 are greatly exaggerated and have been all the time I've been a network engineer. So sorry, I'll be no help to you from here on.

 

Cannot even Ping IPv6 web address

Thanks for all your help Reggie!
Greatly appreciated.

I still cannot ping IPv6 web address thou... not even through the PC1 to PC2 to internet..
Even any computers I have, work computer, laptop, or the setup I had before.. from PC1 or PC2... I cannot even just ping an IPv6 web address...
like PING ipv6.google.com.. .

From online search, everyone said, it is as simple as PING -6 IPv6_address
or PING6 IPv6_address

But I keep getting destination address unreachable, or some problem...

Anyone have any thoughts into this problem?
Thanks again Reggie.

 

You are welcome.

I'm glad to see you've opened a new thread dedicated to the IPv6 problem. That's probably a wise move.

 

Great job Reggie!

I learned a few things myself from you in this thread.

gilee the problem is tho IP6 is coming, it is not widely used now.

I myself have not used it so get to be an Expert in IP6 and hopefully your job market will be better by the time you graduate.

Mike