Technical article 107576

Routing problems using ODT 3.0 syntax for route(ADMN) metrics on OpenServer 5

OpenServer 5.0.0

Written · Last revised

Problem

The functionality provided by the route(ADMN) command has been increased significantly for OpenServer 5.0.0 products, and as a consequence the syntax for specifying the metric for a route has also changed.

Use of the ODT 3.0.0 (TCP/IP 1.2.1) syntax to add a route with
a metric of 9 or less is supported for backward compatibility.
The route(ADMN) command confirms that obsolete syntax has been
assumed and the route behaves as expected.  For example:
# route add default host.domain.dom 5
old usage of trailing digit, assuming route via gateway
add net default: gateway host.domain.dom
However, a metric of 10 or greater is interpreted as a netmask,
which causes routing to behave in an unexpected manner.  The
route(ADMN) command does not warn that the syntax used is obsolete.
# route add default host.domain.dom 15
add net default: gateway host.domain.dom

Only those hosts which match using the netmask thus applied will route as expected; other hosts will fail with the error:

No route to host

The ping(ADMN) command may be used to demonstrate this behavior; the ping(ADMN) command will give output similar to:

$ ping 150.127.5.17
PING 150.126.5.17 (150.126.5.17): 56 data bytes
ping: sendto: No route to host
ping: wrote 150.126.5.17 64 chars, ret=-1
<DEL>

Solution

Use the OpenServer 5.0.0 (TCP/IP 1.2.1) route(ADMN) syntax, For example:

route add -hopcount 16 default gateway

From the Xinuos technical article database, record 107576. Reproduced with permission. The original is at www.sco.com/ta/107576, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.