originally posted at https://www.washington.edu/R870/examples/sun-network To configure a Sun system to properly exist on the UW campus network, do the following steps: o Register an IP address with your departmental network administrator, or with "netops@cac.washington.edu". o If you do not yet have an domain name for you department, you will need to register one with "domainmaster@cac.washington.edu". This will require approval by your departmental chair, so talk to them to begin the process of coming up with a good name for your department on the network. You departmental domain name will have ".washington.edu" added to it, so you should make it relatively short (e.g., 4-7 characters). o If you already have a domain name (for the sake of examples, the name "cac" is used here; substitute your own domain name wherever "cac" occurs), give this name to "domainmaster@cac.washington.edu" along with the name of your computer, IP address, CPU type (e.g., "Sun SPARC"), OS type (e.g., "SunOS"), and the name and phone number of the administrator of the system (for contact if problems occur with the network). You can find a good reference on naming computers in FYI 5, which you can get by anonymous ftp from ftp.uu.net in the directory /inet/rfc. Here is the title line for this FYI: 5 Libes, D. Choosing a name for your computer. 1990 August; 8 p. (Format: TXT=18472 bytes) (Also RFC 1178) o Edit the /etc/hosts file so it has an entry for your host with its IP address and an alias for loghost (required by syslog). Here is an example of the /etc/hosts file: 127.0.0.1 localhost loghost 128.95.257.123 myhost myhost.cac.washington.edu o If you are using SunOS 5, a file should have been created during your operating system installation called "/etc/hostname.le0" (where "le0" is the name of your Ethernet interface, so it may differ from this example). This file contains the name of your host and should match one of the entries in the /etc/hosts file you just created ("myhost", in this example). o Edit the /etc/netmasks file and add an entry for the network 128.95 with a netmask of 255.255.255.0. o Create a file called /etc/resolv.conf. Here is an example of what it should contain: domain cac.washington.edu nameserver 128.95.120.1 nameserver 128.95.112.1 nameserver 128.101.101.101 o For SunOS 5 users, you will need to copy the file /etc/nsswitch.files to have the name /etc/nsswitch.conf. Edit this file and change the entry for hosts to look like this: hosts: files dns o For SunOS 4 users, you will need to replace some libraries on the system that handle domain name system (DNS) name resolution. You can get replacement libraries by anonymous ftp from the site ftp.cac.washington.edu in the directory /pub/sun-fix. Get the file ReadMe.DNS and carefully follow the instructions there. (Note for SunOS 4.1.4 users; the 4.1.3 binaries appear to work fine for 4.1.4 systems) o Routing information can come from one of two places. i). The system, by default, uses the "routed" routing daemon. This daemon uses "router discovery" to determine the router's address and remember it. You don't need to do anything to set this up; just boot the system and it should work fine. ii). Static routes. Static routes are all that you really need on most UW subnets that only have one router out of the local network. This is sometimes preferable to running "routed", since the UW routers are "passive" and will not answer requests for updated routing table information. You can set a static route by putting the router's address in the file "/etc/defaultrouter" file (this may be SunOS 5 only). The standard for router addresses on UW networks is the same subnet address as your host, but with ".100" as the last octet. Using the example IP address as shown in step 1, you would put this entry in "/etc/defaulrouter": 128.95.257.100 o Reboot the computer. The netmask and broadcast address will be set by the system initialization files. (For SunOS 4, the command is "ifconfig le0 netmask + broadcast +" in the /etc/rc.local file. For SunOS 5, the command is "/usr/sbin/ifconfig -au netmask + broadcast +" in the /etc/init.d/inetsvc file.) You host should now be usable on the network.