Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

route command on windows

Nov 24, 2015 3:24AM PST

my current setup
PC
whose eth1 is 10.3.255.102 connected to remote device having 10.3.255.101
its wifi has 192.168.7.23 connected to netgear router having 192.168.7.1
NETGEAR router
has extreme switch connected to its lan port with ip 192.168.7.11
EXTREME switch
has server with ip 10.0.0.2 connected to one of its untagged ports
to its trunk port is connected a network of devices with ip in range 10.0.0.x

Here is route print of PC

[code]
===========================================================================
Interface List
20...10 0d 7f bd 2d b5 ......NETGEAR WNA1000M N150 Wireless USB Micro Adapter
13...6c 3b e5 22 a9 19 ......Realtek PCIe GBE Family Controller
22...0a 00 27 00 00 00 ......VirtualBox Host-Only Ethernet Adapter
1...........................Software Loopback Interface 1
41...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
11...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
12...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
23...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.7.1 192.168.7.23 2
10.3.255.0 255.255.255.0 10.3.255.101 10.3.255.102 21
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.7.0 255.255.255.0 On-link 192.168.7.23 257
192.168.7.23 255.255.255.255 On-link 192.168.7.23 257
192.168.7.255 255.255.255.255 On-link 192.168.7.23 257
192.168.56.0 255.255.255.0 On-link 192.168.56.1 266
192.168.56.1 255.255.255.255 On-link 192.168.56.1 266
192.168.56.255 255.255.255.255 On-link 192.168.56.1 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.3.255.102 276
224.0.0.0 240.0.0.0 On-link 192.168.56.1 266
224.0.0.0 240.0.0.0 On-link 192.168.7.23 257
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.3.255.102 276
255.255.255.255 255.255.255.255 On-link 192.168.56.1 266
255.255.255.255 255.255.255.255 On-link 192.168.7.23 257
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
13 276 fe80::/64 On-link
22 266 fe80::/64 On-link
20 281 fe80::/64 On-link
13 276 fe80::6058:bc3a:8f8c:1b79/128
On-link
22 266 fe80::8436:48fa:c8fc:89f4/128
On-link
20 281 fe80::c8b3:6368:dbd1:54e7/128
On-link
1 306 ff00::/8 On-link
13 276 ff00::/8 On-link
22 266 ff00::/8 On-link
20 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
[/code]
From PC
traceroute to 10.0.0.2 works but not to 10.0.0.x devices
Here is log

[code]
C:\Windows\system32>tracert 10.0.0.2

Tracing route to 10.0.0.2 over a maximum of 30 hops

1 4 ms 1 ms <1 ms 192.168.7.1
2 4 ms 1 ms 2 ms 10.0.0.2

Trace complete.
[/code]

[code]

Tracing route to 10.0.0.38 over a maximum of 30 hops

1 1 ms 4 ms 1 ms 192.168.7.11
2 2 ms * * 192.168.7.11
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

[/code]

How can I systematically find the cause of problem ?

Discussion is locked

- Collapse -
Answer
I'd change my 10. address.
Nov 24, 2015 7:24AM PST

I've yet to use 255 in an IP address for many reasons. Try 0 to 254.
"whose eth1 is 10.3.255.102" is where I go "Hmmm."

- Collapse -
Answer
problem prevails
Nov 26, 2015 8:24PM PST

Sorry , for my late reply .

the thing is :
the port with ip 10.3.255.102 is connected to system having ip 10.3.255.101.
We have a embedded software running on system that communicates to 10.3.255.102 .
So , it cannot be changed .

- Collapse -
Still see a 255 in the address.
Nov 26, 2015 9:33PM PST

So back to those that created this mess.

- Collapse -
problem is why 10.0.0.2 gets pinged while 10.0.0.8 does not
Nov 26, 2015 9:57PM PST

when i send a ping packet for 10.0.0.x it first goes to 192.168.7.1 via 192.168.7.23 interface of my pc because any ip not beginning with 10.3.255 should not got to 10.3.255.102 interface .

Ping packet will go from netgear to switch interface having ip 192.168.7.11
here is switch arp table

* X460-24t.2 # show iparp
VR Destination Mac Age Static VLAN VID Port
VR-Default 10.0.0.2 14:cc:20:05:94:b0 0 NO vlan2001 2001 10
VR-Default 10.0.0.8 00:24:88:00:73:25 0 NO vlan2001 2001 22

I have noticed that I can ping 10.0.0.8 from server with ip 10.0.0.2.
This absolves switch or device with ip 10.0.0.8 from any wrong doing .

Can you tell me why traceroutes result are different ?
Why did 10.0.0.8 go to 192.168.7.11 instead of 192.168.7.1 as in 10.0.0.2 ping ?

- Collapse -
change in results
Nov 26, 2015 10:02PM PST

hi ,
there is no way here to edit posts .

Did traceroute again today

C:\Users\ravinder>tracert 10.0.0.2

Tracing route to 10.0.0.2 over a maximum of 30 hops

1 9 ms 196 ms 2 ms 192.168.7.11
2 3 ms 2 ms 1 ms 10.0.0.2

Trace complete.

C:\Users\ravinder>tracert 10.0.0.8

Tracing route to 10.0.0.8 over a maximum of 30 hops

1 2 ms 1 ms 4 ms 192.168.7.11
2 3 ms * * 192.168.7.11
3 1054 ms * * 10.0.0.8
4 * * * Request timed out.
5 * 16 ms 15 ms 10.0.0.8

Trace complete.

C:\Users\ravinder>ping -t 10.0.0.8

Pinging 10.0.0.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.8: bytes=32 time=15ms TTL=63
Request timed out.
Request timed out.
Reply from 10.0.0.8: bytes=32 time=17ms TTL=63
Request timed out.
Request timed out.

This means ping happens sometimes .
Can you suggest way to debug paths ?

- Collapse -
I've seen that for example
Nov 26, 2015 11:02PM PST

On video DVRs. Turned out the PING was not always going to get a reply since the device was busy sometimes. There was nothing wrong with the route.

-> I think you need on site support.