To delete a route from just the routing table (not the ODM), route delete -net 199.221.80 -netmask 255.255.252.0 10.225.48.1 To delete it from both places (what smitty does), chdev -l inet0 -a delroute=net,-netmask,255.255.252.0,199.221.80,10.225.48.1 To see persistent routes (ie, they're in the ODM), odmget -q 'name=inet0 AND attribute=route' CuAt To add perisistent static routes, it's easiest to go through smitty Communications Applications and Services TCP/IP Further Configuration Static Routes Add a Static Route For network routes (the most common type), leave Destination TYPE = net and fill in DESTINATION Address = 163.231.10.0 Default GATEWAY Address = 10.225.48.1 Network MASK = 255.255.255.224 for example, in the case of EDC machines to get to rhino. ------------------------------------------------------------------------------- The "/nn" number in the new netstat -rn command, e.g. netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2 (Internet): default 9.1.24.250 UG 7 6674 en0 - - 9.1.24/21 9.1.30.30 U 254 876932 en0 - - 10/8 9.1.24.253 UG 0 0 en0 - - 32/8 9.1.24.253 UG 0 0 en0 - - 127/8 127.0.0.1 U 0 203 lo0 - - ... is the number of significant bits on the left, that this Destination uses. For the example above, 127/8 says 127.0.0.0 through 127.255.255.255, that is, the 127 is the first 8 bits. Contrast that with the 9.1.24/21, which says the 9.1.24 is the first 21 bits (e.g. netmask = 255.255.248.0), so the Destination refers to 9.1.24.0 through 9.1.31.255. ------------------------------------------------------------------------------- Normally, a change to your /etc/hosts file is ignored in preference to going to your DNS server(s), so if you want your system to check your local /etc/hosts file first, export NSORDER="local,bind" You can also specify this in a system's /etc/netsvc.conf file, e.g. echo hosts = local,nis,bind > /etc/netsvc.conf ------------------------------------------------------------------------------- There are two types of ethernet connections. Around Almaden, We have versus We Don't Have versus We Also Don't Have ------------ ------------- ------------------ Twisted Pair Thick Thin 10 Base T 10 Base 5 10 Base 2 en0 et0 RJ-11 15-Pin BNC (aka coax) dix ??? ---- I'm not sure what this is ---- BNC You can connect a Twisted Pair, 10 Base T wire to a Thick, 15-pin connector with a transceiver, which is common practice at Almaden. With a different transceiver, you could connect a Thin, 10 Base 2 wire to a Thick, 15-pin connector, but you (probably) won't see this setup at Almaden. The point is, transceivers are connection adapters. Separate from the connection, is the protocol one chooses to run over your physical wire. The protocol could be either Standard or IEEE 802.3. At Almaden, we use the Standard protocol. ------------------------------------------------------------------------------- Notes from the TCP/IP Networking class I took 4/24/95. /etc/inittab has a line to call /etc/rc.tcpip. /etc/rc.tcpip has lines to start the tcp/ip daemons, - syslogd. Error and event logging. - sendmail. To send mail (duh). - portmap. To return port numbers per /etc/services. - inetd. To control other tcp/ip deamons per /etc/inetd.conf.----\ | Commented out but you can uncomment if you wish are | - lpd. Line printer daemon. | - Either routed or gated. gated is better. | - named. Name Server. | - timed. ?? | - rwhod. "A time waster" ?? | - snmpd. Simple Network management Protocol. | | /etc/inetd.conf are the services that inetd controls. Some are <-------/ commented out and is best handled by smit to uncomment (because smit then "imports" the changes to the ODM via inetimp and refreshes inetd via refresh -s inetd). The interesting services are - ftpd - telnetd These daemons are only started when needed. - rshd One instance is started up for every session. - rlogind - rexecd -------------------------------------------------------------------------------- The 7 (sometimes only 5) layers of the Internet Protocol Architecture are Application: Sends and receives data to/from socket buffers. Examples are ftp & rlogin. +---------------------------------+ | Data | +---------------------------------+ Presentation: Data Retrieval Layer. External Data Representation (XDR) protocol transforms data to a generic format before transmitting and allowing machines with different architectures to exchange information. Oftentimes left out of the 7 protocols. Session: Remote Procedure Call (RPC) Library. Oftentimes left out, too. Transport: Responsible for breaking up data from socket buffers into smaller, more-manageable pieces. Determines socket (ip_address, port #) to use. An application chooses which it wants to use. Examples are - TCP: Has a built-in mechanism to insure correctness of data transport (as far as correct order and completeness). ftp uses TCP. Passes "segments" to Internet layer. Statefull. +------------+-------+ | TCP Header | Piece | This is a segment. +------------+-------+ - UDP: Has no such mechanism. tftp uses UDP. So does NFS, but NFS does the data integrity assurances itself. Passes "messages" to Internet layer (same as TCP segments, just different word). Stateless. +------------+-------+ | UDP Header | Piece | This is a message. +------------+-------+ Internet: Handles logical addressing & routing. ARP is also at this layer, but sometimes ARP is its own layer. Knows about subnet masks. +-----------+------------+-------+ | IP Header | TCP Header | Piece | This is a datagram. +-----------+------------+-------+ Network Interface: Knows about hardware addresses. +-----------+-----------+------------+-------+------------+ This is a | NI Header | IP Header | TCP Header | Piece | NI Trailer | packet. +-----------+-----------+------------+-------+------------+ Physical: Wiring & electrical. Examples are - IEEE 802.3 Ethernet. (et) - Standard Ethernet Xerox Version 2. (en) Most common. - Token Ring, aka IEEE 802.5. (tr) Uses MSAU's. - Fiber Distributed Data Interface (FDDI). - X.25. - SLIP, aka RS-232 or asynch. "Poor man's ethernet." --------------------------------------------------------------------------------- From the TCP/IP Networking Student Notebook, page 1-41. See also the AIX 4.1 Migration Student Notebook, page 4-49. gateway - Software at the application layer that connects two different types of network protocols together, for example, SNA & token ring. router - Software at the Internet layer that connects two networks of the same type together. Not a daemon. Bridge - Hardware at the network interface layer that connects two networks, forming a bigger logical network. Repeater - Hardware at the physical layer that propogates electrical signals. -------------------------------------------------------------------------------- | ARPANET | Berkeley --------------------+--------------+------------ File Transfer | ftp & tftp | rcp | | Remote Commands | rexec | rsh | | Remote Login | telnet/tn | rlogin | | Authorization File | ~/.netrc | /etc/hosts.equiv for above commands | | or ~/.rhosts | | Miscellaneous | finger | who | | talk | setclock | ruptime -------------------------------------------------------------------------------- Host Name Resolution: /---------------\ /-----------------------\ / Is DNS running? \ /--------------\ | We are a DNS client. | | I.E. does | Yes / Is \ No | /etc/resolv.conf has | | /etc/resolv.conf |----->| /etc/resolv.conf |---->| our domain name and | \ exist? / \ empty? / | the I.P. address of | \---------------/ \--------------/ | our nameserver in it. | No | | Yes. \-----------------------/ | \|/ | | /---------------------\ \|/ | | We're a nameserver. | /---------------\ | | Use the named | / Check \ Found | | daemon running |--->| nameserver |--\ | | on our machine. | \ for resolution. / | | \---------------------/ \---------------/ | | Not Found | | |<---------------------------------------------------/ | | \|/ | /----------------\ \|/ | Name is resolved | /----------------\ /---------\ \----------------/ / Is NIS running? \ Yes / Check \ /|\ | I.E. is |-------->| NIS server | Found | \ ypbind running? / | for |-----------------------/ \----------------/ \ resolution / | No | \----------/ | | Not | Note that /etc/hosts | | Found | is not used in an | \|/ | NIS environment. | /-----------\ \|/ | | Is it in | No /--------\ | | /etc/hosts? |-------------->| Failed | | \-----------/ \--------/ | Yes | | \-----------------------------------------------------------/ If /etc/resolv.conf exist and is empty, then we are a name server. Go to our named daemon for name resolution. (There is a difference between a primary and secondary server differentiated in the /etc/named.boot file.) The ARCworld standard platform sets up each machine as a primary name server, i.e. /etc/resolv.conf exists and is empty, and /etc/named.boot has domain almaden.ibm.com cache . /etc/named.ca primary 0.0.127.in-addr.arpa /etc/named.local The /etc/named.ca file is what points to the "real" nameservers at 129.33.xx.254, at least for the initial load of named's cache. See the AIX/6000 Network Services, NFS, NIS, DNS Student Notebook starting on page 5-19 for more detail on these files and how to set everything up. If /etc/resolv.conf exists and is not empty, then we are a client and the /etc/resolv.conf file contains the default domain name and the server name. For example, when I initially defined a nameserver on pulp, smit created a /etc/resolv.conf with this in it nameserver 129.33.12.254 domain almaden.ibm.com -------------------------------------------------------------------------------- To check the networking options, no or to just check on option, no -o ipforwarding to change an option, no -o ipforwarding=1 -------------------------------------------------------------------------------- A tftp server uses /etc/tftpaccess.ctl to define what is available via tftp, e.g. allow:/local/lib/afs --------------------------------------------------------------------------------