Problems when adding an entry to the network routing table.

Hello,

when I add a new entry to the network routing table my system hang up if
the specified gateway is not online (e.g. the gateway computer is
shutdown at the moment).
After I have execute the following command:
route ADD 192.168.105.0 MASK 255.255.255.0 192.168.105.10 METRIC 1 IF 3
the system doesn't work successfully anymore till I have reboot the hole
system. The system cannot be accessed through telnet, FTP or each other
protocol, but it responds successfully to all ping requests.

With the PB 5.0 I discovered that something in the AFD component seems
to block but I cannot find the cause. Maybe that something in the TCP/IP
stack is corrupted to but I don't know why. I don't think that the
problem is in the network driver because the device responds
successfully to ping requests.

Have someone else seen this problem before ? Is there a solution
available for this curiosity ? I' using Windows CE 5.0 with all actual QFEs.

Thanks in advance for any help.

Regards,
Ruediger Fichter

Remi
Fri Feb 02 08:35:59 CST 2007

Hi,

> METRIC 1

Are you sure of your METRICS parameter?
IMHO, 1 "hop" is a really short path for IP packets that have to cross
gateways; etc.

Remi

R
Fri Feb 02 09:15:31 CST 2007

Remi de Gravelaine schrieb:
> Hi,
>
>> METRIC 1
>
> Are you sure of your METRICS parameter?
> IMHO, 1 "hop" is a really short path for IP packets that have to cross
> gateways; etc.
>
> Remi
>
>
Yes I'm sure of the METRIC parameter. The traffic, which I want to
transfer is for the connected network and have not to cross gateways.
But my problem is independent of the METRIC parameter.

Ruediger

Remi
Fri Feb 02 10:04:02 CST 2007

So, if the problem happens when the gateway is off, it may be because
'someone' tries to access this gateway when you make the ROUTE ADD. Did you
try to catch the Ethernet traffic at this moment?

Remi

R
Mon Feb 05 06:06:35 CST 2007

Remi de Gravelaine schrieb:
> So, if the problem happens when the gateway is off, it may be because
> 'someone' tries to access this gateway when you make the ROUTE ADD. Did you
> try to catch the Ethernet traffic at this moment?
>
> Remi
>
>
I have catch the traffic on the ethernet. The device sends ARP requests
to solve the IP address of the specified gateway which is not available.
It seems that this block each request to the upper protocol layers
(telnet, ftp, ...).
I have done further investigation and find out that the problem only
exists if the destination network, the gateway which is not available
and the interface are in the same network. E.g. if the destination is
specified to 192.168.105.0, the interface has the IP 192.168.105.121 and
the gateway the IP 192.168.105.12 (which is currently not available)
then the problem occurs.
I'm not sure if this an illegal route entry which I want to declare or
if this is a bug. My expectation is it, that this don't block all traffic.

Regards,
Ruediger

Remi
Mon Feb 05 09:27:12 CST 2007

Hi Ruediger,

> I have done further investigation and find out that the problem only
> exists if the destination network, the gateway which is not available and
> the interface are in the same network. E.g. if the destination is
> specified to 192.168.105.0, the interface has the IP 192.168.105.121 and
> the gateway the IP 192.168.105.12 (which is currently not available) then
> the problem occurs.

If not illegal (?), this is quite a special route entry.
Maybe the bad behaviour of the whole stack comes from this as usually, when
gateways are not available, things go faster.
It would be interesting to have MS opinion on this point.

Remi