Gabriel Cane(deleted)
12/23/2010 9:59 AM
post80208
|
Hello, I have communications problems in a link between two hosts in different tcp/ip networks (i'm using a router to do
this communication).
My Server is the IP 192.168.11.1 (QNX host)
and the client host is 192.168.0.1 (non qnx host - RTU)
The router have the IP address 192.168.11.252, so I added the route
#route add -net 192.168.0.0 -netmask 255.255.255.248 192.168.11.252
First, I assumed a fail in the fiber link between the router and the RTU. So I proved with a "all-day" ping to get some
information about the problem.
The result was, several lost of pings, whith the "no route to host" message.
Then, I've created a virtual interface in the router (An allways alive interface or network from the point of view of
the other networks). The result of the ping test, was the same for my virtual interface.
Therefore, I can't assume a problem in the fiber link. And, as the error message says, the problem is a lost route for
the network 192.168.0.0/29.
The same test, pinging to the router from my host, was always successfuly.
Is possible, that my QNX server losses routes for periods of about 40 seconds o less?
Internet:
Destination Gateway Flags Refs Use Mtu Interface
10.210.40/22 link#5 UC 49 0 - en3
10.210.40.10 00:a0:f4:01:00:40 UHLc 1 55732081 - en3
10.210.40.11 00:a0:f4:00:0a:1f UHLc 1 5224829 - en3
10.210.40.12 00:a0:f4:01:00:44 UHLc 1 55693107 - en3
10.210.40.14 00:a0:f4:01:00:41 UHLc 1 55730625 - en3
10.210.40.15 00:a0:f4:01:00:46 UHLc 1 55697045 - en3
10.210.40.16 00:a0:f4:01:44:96 UHLc 1 55705008 - en3
10.210.40.21 00:a0:f4:01:00:48 UHLc 1 55724202 - en3
10.210.40.23 00:a0:f4:01:00:43 UHLc 1 5236297 - en3
10.210.40.36 00:a0:f4:04:00:a4 UHLc 1 16804378 - en3
10.210.40.70 00:a0:f4:01:41:f6 UHLc 1 27221310 - en3
10.210.40.71 00:a0:f4:01:56:7b UHLc 1 27213964 - en3
10.210.40.74 00:a0:f4:01:41:f5 UHLc 1 27287201 - en3
10.210.40.75 00:a0:f4:01:56:fb UHLc 1 27224002 - en3
10.210.40.82 00:a0:f4:01:56:53 UHLc 1 27300330 - en3
10.210.40.83 00:a0:f4:01:56:fc UHLc 1 27280735 - en3
10.210.40.108 00:a0:f4:01:37:2d UHLc 1 17493316 - en3
10.210.40.118 00:a0:f4:41:6f:2e UHLc 1 33207717 - en3
10.210.40.151 00:a0:f4:01:16:74 UHLc 1 24887446 - en3
10.210.40.254 00:0e:0c:7f:c0:b5 UHLc 0 2 - en3
10.210.41.7 00:a0:f4:01:a5:f9 UHLc 1 8823528 - en3
10.210.41.8 00:a0:f4:01:91:b5 UHLc 1 5564906 - en3
10.210.41.15 00:a0:f4:01:7b:5f UHLc 1 8543950 - en3
10.210.41.16 00:a0:f4:01:7b:33 UHLc 1 5183769 - en3
10.210.41.18 00:a0:f4:04:1f:07 UHLc 1 8545354 - en3
10.210.41.19 00:a0:f4:01:a5:f7 UHLc 1 8309208 - en3
10.210.41.20 00:a0:f4:01:90:85 UHLc 1 5203971 - en3
10.210.41.22 00:a0:f4:00:15:ac UHLc 1 2405227 - en3
10.210.41.25 00:a0:f4:01:91:b7 UHLc 1 4914377 - en3
10.210.41.26 00:a0:f4:01:90:8a UHLc 1 6445966 - en3
10.210.41.27 00:a0:f4:01:90:88 UHLc 1 6446406 - en3
10.210.41.28 00:a0:f4:01:90:62 UHLc 1 209450 - en3
10.210.41.29 00:a0:f4:01:90:63 UHLc 1 210362 - en3
10.210.41.246 00:00:54:14:70:ab UHLc 1 131239584 - en3
10.210.42.5 00:a0:f4:01:97:69 UHLc 1 37821135 - en3
10.210.42.6 00:a0:f4:01:97:53 UHLc 1 41906247 - en3
10.210.42.7 00:a0:f4:01:97:56 UHLc 1 41673128 - en3
10.210.42.8 ...
View Full Message
|
|
|