IP Routing with a subnet and internet

gilee · August 29, 2008

I been reading and looking for 2 weeks now, and with the 8 hrs I tried

today after work, I believe I am stuck! I need help Everyone!

I am basically trying to get PC1 to ping www.yahoo.com through this

connection layout:

PC1(NIC1) -> HUB -> PC2(NIC2) -> PC2(NIC3) -> cable modem -> www.yahoo.com

This is the setting I had so far. I cannot even get IPv4 to work.

-- PC1 (NIC1) --

IP address: 10.1.1.11

Subnet mask: 255.255.255.0

Default gateway: 10.1.1.1

-- PC2 (NIC2) --

IP address: 10.1.1.1

Subnet Mask: 255.255.255.0

Default gateway: empty

-- PC2 (NIC3) --

IP address: 192.168.1.148

Subnet mask: 255.255.255.0

Default Gateway: 192.168.1.1

-- cable modem --

IP address: 192.168.1.1

I already did the following 2 things as well:

1) changed the IPEnableRouter register to enable in windows XP

2) I even tried to add a IP route into window XP routing Table:

route -p add 192.0.0.0 mask 255.0.0.0 10.1.1.0 metric 2

Please help. Thanks

gilee · August 29, 2008

BTW my real goal is using IPv6, but for now I just want to get the routing to work.

Also for #1 & #2, I only did those IPEnableRoute and Route Table in PC2.

Hope this clear things more. Thanks.

gilee · August 30, 2008

Anyone??

Scarecrow Man · August 31, 2008

1. Why are you using a hub? They are terrible and will cause collisions on your network. Get a switch, or even better a router.

2. It looks like PC2 is the one connected to the cable modem. Why could you not just plug the cable modem into the switch (not hub) and connect both computers to the same switch. Voila!

3. Why no router? Would makes things a lot easier :)

gilee · August 31, 2008

Hello, I kinda figure people might ask why in the world I am doing what I am trying to do here.

It is a VERY long story, but let me give you a short summary of it so you understand why.

This is a setup I am trying to do for my Thesis for master Degree, and I have to setup the network in this form so I can continue further into my project and complete my degree. So in a big picture, I am setting up an entire local network with two computers. PC1 and PC2. They both are collected with a HUB (I pick HUB before I intentionally don't want any intelligents/smartness to it) PC1 has only 1 NIC which connects to the HUB. PC2 has 2 NIC, one to the HUB and one to the cable modem (to the internet). What I am trying to do is, on PC1, I tries to ping a website on the WWW using IPv6. So PC1 NIC1 ping PC2 NIC2 thought the hub, then the ping will get routed to PC2 NIC3 to the WWW ..on and on...

I tried over 2 weeks reading and reasearching but still no luck in this problem. So please help.

Here are the information for PC1 and PC2. I hope this will helps. They are obtained by ipconfig /all >"%USERPROFILE%"\Desktop\pc1ipcfg.txt for both PC1 and PC2.

======= PC1 (tester1) ========

Windows IP Configuration

Host Name . . . . . . . . . . . . : tester1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Ethernet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® PRO/100 VE Desktop Connection

Physical Address. . . . . . . . . : 00-02-55-7F-E7-7D

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.1.1.11

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::202:55ff:fe7f:e77d%4

Default Gateway . . . . . . . . . : 10.1.1.1

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 0A-01-01-0B

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.11%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

======= PC2 (tester2) ========

Windows IP Configuration

Host Name . . . . . . . . . . . . : tester2

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-C0-CA-19-A3-28

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.148

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::2c0:caff:fe19:a328%4

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Saturday, August 30, 2008 8:27:34 PM

Lease Expires . . . . . . . . . . : Sunday, August 31, 2008 8:27:34 PM

Ethernet adapter Local Ethernet:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® PRO/100 VE Desktop Connection

Physical Address. . . . . . . . . : 00-02-55-3F-4E-F4

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.1.1.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::202:55ff:fe3f:4ef4%5

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2

fec0:0:0:ffff::2%2

fec0:0:0:ffff::3%2

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-94

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.148%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 0A-01-01-01

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.1%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2

fec0:0:0:ffff::2%2

fec0:0:0:ffff::3%2

NetBIOS over Tcpip. . . . . . . . : Disabled

Scarecrow Man · August 31, 2008

You should work 1 PC at a time. Get each one connected and bridging its connection to other PC's.

I have a set up of:

PC1

- Connected to internet via Dial Up.

- Connected to PC2 via crossover.

- Connected to Router via straight thru.

PC2

- Connected to PC 1 via crossover.

PC3

- Connected to router via straight thru.

PC4

- Connected to router via Wireless.

All had internet, all were networked.

I used a workgroup of home and I manually entered all the ip addresses as:

PC1 - 192.168.0.1

PC2 - 192.168.0.3

PC3 - 192.168.1.102

PC4 - DHCP

Router - 192.168.0.2 (outside) / 192.168.1.1 (inside)

Could you do something like this?

gilee · September 2, 2008

Hi, I am not sure how you set it up.

But below are what I did.

Here are the results from Pinging in both PC1 (tester1) and PC2 (tester2).

The following results are obtained by typing in:

ping tester2 >"%USERPROFILE%"\Desktop\t1pingt2.txt

ping 192.168.1.148 >>"%USERPROFILE%"\Desktop\t1pingt2.txt

ping 192.168.1.1 >>"%USERPROFILE%"\Desktop\t1pingt2.txt

ping yahoo.com >>"%USERPROFILE%"\Desktop\t1pingt2.txt

=============== Pinging From Tester 1 ================

Pinging tester2 [10.1.1.1] with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.148 with 32 bytes of data:

Reply from 192.168.1.148: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.148:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:

Request timed out.

Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping request could not find host www.yahoo.com. Please check the name and try again.

=============== Pinging From Tester 2 ================

Pinging tester1 [10.1.1.11] with 32 bytes of data:

Reply from 10.1.1.11: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.11:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 10.1.1.11 with 32 bytes of data:

Reply from 10.1.1.11: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.11:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 10.1.1.1 with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging www.yahoo-ht3.akadns.net [69.147.76.15] with 32 bytes of data:

Reply from 69.147.76.15: bytes=32 time=20ms TTL=50

Reply from 69.147.76.15: bytes=32 time=18ms TTL=50

Reply from 69.147.76.15: bytes=32 time=17ms TTL=50

Ping statistics for 69.147.76.15:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 17ms, Maximum = 20ms, Average = 18ms

Let me know if you need any other information.

Thanks again, I greatly appreciated!

homecomputeraid · September 2, 2008

2) I even tried to add a IP route into window XP routing Table:
route -p add 192.0.0.0 mask 255.0.0.0 10.1.1.0 metric 2

Is this route still in the routing table for PC1 or PC2? It's wrong. The route should be 192.168.1.0 mask 255.255.255.0 next hop 192.168.1.1 if you're putting it on PC2 for the networks as you have them configured.

Are all PC's running Windows XP?

What's the Teredo Tunneling Pseudo Interface? Does your Internet Service Provider (ISP) require authentication to use the Internet?

Please do a route print from each PC at the command prompt and paste the results here.

gilee · September 3, 2008

Do you mean I should do route -p add 192.168.1.0 mask 255.255.255.0 192.168.1.1 metric 2.

It is still no good.

gilee · September 3, 2008

Hi guys,

I just thought of using another point of view (different angle) in attacking my problem.

How about I do it this way.

Same configuration of having 2 computers. PC1 (with 1 NIC) & PC2 (with 2 NICs)

Same configuration of PC1(NIC1) <-> HUB <-> PC2 (NIC2) -- PC2 (NIC3) <-> internet

Both PC has windows XP installed with SP2 updated and both PC has Microsoft TCP/IP version 6 installed.

Now I set PC1 NIC1 to "Obtain an IP address automatically" from Internet Protocol (TCP/IP) Properties

I set PC2 NIC2 to "Obtain an IP address automatically" also

Then I set PC2 NIC3 to Internet Connection Sharing Enabled.

Now when I tries to PING from tester1(PC1) to tester2(PC2), it works fine and so does other PING like (from tester1)

PING tester2 (successful)

PING 192.168.1.1 (successful)

PING 192.168.1.148 (successful)

PING www.yahoo.com (successful)

But the reason I chose not to use Internet Connection Sharing features and go for manual IP routing because I cannot get IPv6 to work.

I am trying to capture IPv6 packets (echo) using wireshark on PC1 when I ping www.yahoo.com.

But instead the wireshark on PC1 (tester1) only capture IPv4 packets, so this is clearly show that PC1 used IPv4 to send the PING to PC2 and route to www.yahoo.com for PING.

Can anyone help for providing what setting I can do to PING in IPv6?

Thank you very much!

homecomputeraid · September 3, 2008

See if the following helps:

http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

Q. How do I ping?

A. Windows Vista, Windows Server 2008, Windows XP with SP1 or later, and Windows Server 2003 include an IPv6-enabled version of the Ping.exe tool. When you ping a link-local address with the Ping.exe tools, you must include a zone identifier (ID), which specifies the interface over which the ICMPv6 Echo Request messages are sent. For link-local addresses, the zone ID is typically equal to the interface index, as displayed in the output of the netsh interface ipv6 show interface or command.
For site-local addresses, the zone ID is equal to the site number, as displayed in the output of the netsh interface ipv6 show interface level=verbose command. If multiple sites are not being used, a zone ID for site-local addresses is not required.
The zone ID is not needed when the destination is a global address.
For example, to send ICMPv6 Echo Request messages to the link-local address fe80::260:97ff:fe02:6ea5 using zone ID 4 (the interface index of an installed Ethernet adapter), use the following command:

ping fe80::260:97ff:fe02:6ea5%4

Try manually pinging by IPV6 Address.

gilee · September 4, 2008

Thanks for the link! =)

I basically spent my past don't know how long times looking and reading online.

I am able to PING and get IPv6 replies from PING ECHO... but only from PC1 to PC2.

I am unable to get IPv6 replies from PING ECHO when I tries to ping from PC1 to the outside world.

See if the following helps:
http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

Q. How do I ping?

A. Windows Vista, Windows Server 2008, Windows XP with SP1 or later, and Windows Server 2003 include an IPv6-enabled version of the Ping.exe tool. When you ping a link-local address with the Ping.exe tools, you must include a zone identifier (ID), which specifies the interface over which the ICMPv6 Echo Request messages are sent. For link-local addresses, the zone ID is typically equal to the interface index, as displayed in the output of the netsh interface ipv6 show interface or command.
For site-local addresses, the zone ID is equal to the site number, as displayed in the output of the netsh interface ipv6 show interface level=verbose command. If multiple sites are not being used, a zone ID for site-local addresses is not required.
The zone ID is not needed when the destination is a global address.
For example, to send ICMPv6 Echo Request messages to the link-local address fe80::260:97ff:fe02:6ea5 using zone ID 4 (the interface index of an installed Ethernet adapter), use the following command:
ping fe80::260:97ff:fe02:6ea5%4
Try manually pinging by IPV6 Address.

homecomputeraid · September 5, 2008

You're reaching the limits of my IP V6 knowledge. If you're pinging a site across the Internet, does it have both IP V6 and IP V4 addresses? IP Version 4 is still ubiquitous. There are probably many instances where a device between you and the device you're pinging does not do IP V6. Does it then revert to IP V4?

Sorry I don't know the answers to those questions. If everything works up to where you hand off to the Internet, the problem may be in traversing the Internet to get to the IP V6 site.

Sign In

IP Routing with a subnet and internet

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information