Problem
With previous versions of OpenServer the "routed" daemon would start
by default. With later versions of OpenServer this does not happen. Cause
If you don't specify a default route, you get neither the default
route set nor does routed start up. Solution
Routing will occur once a value is defined in the GATEWAY= entry of /etc/default/tcp, or the start up of routed is automated by giving the value "/etc/routed" to the ROUTER_DAEMON entry in /etc/default/tcp.
The extract from /etc/default/tcp reads as follows:
# The ROUTER_DAEMON keyword can be used to start your choice of router daemon.
# For example, to use routed, set ROUTER_DAEMON=/etc/routed. You can also
# pass argument to the daemon, using the ROUTER_DAEMON_ARGS keyword. Note
# that is you set ROUTER_DAEMON, it must point to an executable file, which
# is executed by /etc/tcp. Usually, if you set a default GATEWAY, you do not
# set a routing daemon.Also run the commands:inconfig -v ipforwarding
inconfig -v ipsendredirectsThese should be set to "0" if your server is not acting as a router.
For OpenServer 5.0.5:The routed daemon can be disabled by changing the following in the file /etc/tcp
FROM:if [ -x /etc/routed -a ! -f /etc/gated.conf ]; then
routed &
echo "routed \c"
fiTO:# Turn of "routed" by ... on ...
#
#if [ -x /etc/routed -a ! -f /etc/gated.conf ]; then
# routed &
# echo "routed \c"
#fiWhen the server re-boots there will be no "routed" daemon running.
Note: if you modify your network configuration within "netconfig" then this file will be re-configured and your changes removed.
To add a default gateway:Create a file as defined in TA107569, "How do I add a default
route statement so it's included at boot-up in OpenServer 5.0?"To add DNS client (resolve) capabilities:Create a file called:/etc/resolv.conf containing a sample such as:domain <Fully Qualified Domain Name (FQDN)> hostresorder local bind nis nameserver xxx.xxx.xxx.xxx nameserver yyy.yyy.yyy.yyy search FQDN
Where "domain" refers to the domain the server is in.
"hostresorder" refers to the name resolution path. In this case, names are resolved locally in /etc/hosts first, then by the DNS nameserver(s) and then by any NIS configuration.
"nameserver" refers to the name(s) of the server(s) to resolve
names from. In the case of one nameserver being down you may
wish to configure a secondary."search" refers to the search list for host-name lookup. The search list is normally determined from the local domain name. By default, it begins with the local domain name, then successive parent domains that have at least two components in their names.
For example: search subnet1.company.com company.comNOTE: Should you experience problems pinging servers after configuring
DNS as above then the nameserver defined may be incorrect.Tools to test functionality are :ping -n <IP_address> which does not use name resolution
traceroute -n <IP_address>If these tools work, then the problem is name resolution. If not, then there is likely to be a name resolution problem.
NOTE: For OpenServer 5.0.7, 6.0.0, the default route can be set when you add
a network card at Initial System Load (ISL).Post installation this can be done in "scoadmin client manager".
See also
TA107569, "How do I add a default route statement so it's included at boot-up in OpenServer 5.0?"
TA107690, "Routes are mysteriously showing up in my routing tables."
TA107706, "Can I run the IRD protocol with RIP or OSPF, that is, with routed or gated?"
TA110909, "'routed' adds duplicate entries into the routing table for a subnetted class C netmask."
TA109261, "UnixWare 7 gethostbyname and gethostbyaddr search order (hostresorder)."
resolver(SSF)
ping(ADMN)
inconfig(ADMN)